Phishing test ideas for Nigerian offices (6 safe ones)
Get a free phishing test for up to 25 of your staff We run a safe, fictional phishing test and show you who clicked and what to fix. It takes a short form. Request the free test → Phishing test ideas built for a US or European office often miss the fraud your Nigerian staff actually meet. Here are six built around local life. All use fictional names, companies and domains. None uses a real brand or a live harmful link.
What makes a good phishing test for staff?
A good test looks like something your staff could really receive, teaches one habit, and is fair. Pick one scenario, one habit, one lesson.
Use the real-life pattern, not a real brand. CISA lists the signs to teach: urgent or emotional language, requests for personal or financial information, untrusted shortened links, and incorrect addresses that imitate real ones. Build each test around one or two of these.
1. Fake POS “wrong transfer, please refund” alert
Scenario: A text claims a customer sent money to the wrong account by POS and urgently asks for a refund, with fake transaction details.
What it teaches: Verify any reversal request through official bank channels. Never act on an unsolicited alert alone. See fake transfer alerts and POS fraud.
2. Vendor bank-detail change email
Scenario: An email that looks like it is from a known vendor says their bank account changed “due to an internal audit” ahead of this month’s invoice.
What it teaches: Any change to payment details needs a call to a number already on file, and a second person to approve. Never reply to the email that asks. See business email compromise.
3. WhatsApp family-emergency message
Scenario: A message from an unknown number says a relative is in trouble and asks for money or an OTP now.
What it teaches: Urgency plus a request for money or a code from a number you do not know is a scam pattern, however personal it feels. Read more on WhatsApp scams at work.
4. Fake regulator call
Scenario: A caller says they are from a regulator, claims a compliance problem and demands payment or account access to “fix” it.
What it teaches: Regulators do not settle compliance issues by an unexpected call that demands payment. Staff should pass it up the line, not handle it on the spot.
5. Fake recruitment or loan-app message
Scenario: A message offers a very generous job or loan and asks for a form with personal and banking details.
What it teaches: An offer that is too good, plus a request for sensitive data up front, is a common data-harvesting trick. See BVN and OTP scams at work.
6. QR code poster in the break room
Scenario: A poster offers a prize or a survey, and the QR code leads to a fake login page.
What it teaches: Treat a QR code like a link. Check where it goes before you type a password. See text and QR code scams.
How do you run one phishing test, step by step?
Tell staff the program exists, send to a small group first, teach right after a click, then count and repeat.
- Tell staff the program exists. A short note from leadership is enough. Do not name the date.
- Pick one scenario from the list above.
- Send it to a small group first to check the message works and the landing page is safe.
- Teach in the moment. When someone clicks, show a short page that names the red flag they missed.
- Count clicks and reports. The report rate matters as much as the click rate.
- Repeat next month with a different scenario.
How do you keep a phishing test fair?
Keep it safe and kind. A few simple rules:
- Never use a real bank, a real regulator logo or a live harmful link. Point only to your own landing page.
- Do not test on staff who are in the middle of a hard week, such as month-end payroll.
- Do not shame people or share names in front of the team.
- Give finance staff their own scenarios, since they approve payments.
- Thank people who report, even for a false alarm.
What should you measure?
Measure the report rate, the click rate and how long people take to report. If more people report and fewer click over the months, your training is working. Our full guide has the measurement table.
Running these end to end
Every simulation should point only to your own tracking and landing page, and end with a specific teachable moment when someone clicks, replies or calls back. See our full phishing simulation program for how we run these, rotated through a 12-month calendar so no employee sees the same test twice in a year. Note that every simulation is delivered by email today, so the WhatsApp, call and QR ideas above run as email scenarios written around those patterns.
Not sure where your team stands? Get a free phishing risk test or book a free demo.
Questions people ask
What is a phishing simulation?
A safe, fake phishing message sent to your own staff to see who clicks, and to teach them right after.
What is a good phishing test for staff?
One that copies a real message your staff might get, such as a vendor bank-detail change, with a fictional sender and a safe landing page.
How often should we run one?
Many teams run one a month or one a quarter. Pick a rhythm you can keep. See our guide on how often to train.
Is it legal to test staff?
Tell staff the program exists, keep it fair, and avoid real brands or harmful content. Ask your legal adviser about your setup.
Should we punish people who click?
No. Teach them in the moment. Fear makes people hide mistakes, and you want them to report.