Yes. Phishing simulation templates can be fully localised for New Zealand scams, and 2026 is exactly the year to do it — Kiwi staff ignore generic templates that smell American, while the scams that actually hit NZ inboxes (IRD tax refunds, NZ Post delivery fees, bank card suspensions) are specific to this country. Localisation is not translation. It is swapping the sender, the pretext, the currency and the references so the email looks like it was written in Wellington, not Ohio.
TL;DR
- Templates localise on four axes: sender domain, pretext, currency and cultural references.
- NZ-specific pretexts (IRD, NZ Post, ANZ/ASB/BNZ/Westpac) land harder with NZ staff than generic corporate templates.
- Localisation works best when paired with reporting and trend tracking so you can measure which pretexts actually fool people.
- Generic templates still have a place — many real phishing emails are deliberately plain English with no local flavour.
Why NZ staff ignore generic phishing templates
A phishing simulation only trains people if the email is plausible. NZ staff see an email about an 'overdue invoice from your accounts department' written in American idiom and they delete it without opening — the lesson never lands. Run the same staff through an email that looks like an NZ Post delivery-fee notice, and click rates jump.
CertNZ, New Zealand's national cyber security agency, reported 7,003 cyber security incidents in 2021 (an increase of 33% year-on-year), with phishing and scams the top two incident categories — the threat is local, and it targets NZ consumers and staff with local-looking pretexts.
- Pretext: NZ Post parcel fee, IRD tax refund, MyMSD payment update, ANZ/ASB/BNZ/Westpac card suspension
- Sender domain: .co.nz and .govt.nz lookalikes, not .com
- Currency: NZD, not USD
- Language register: NZ English spelling and NZ-specific service names
A template that nails all four is indistinguishable from the real scam email a staff member saw last week — which is exactly what makes the training stick.
How localisation actually works
Phishing simulation platforms support localisation at three levels, and Cyber Aware's phishing simulation module supports all three:
- Template library selection. Pre-built templates exist per region — an NZ library carries local sender names and pretexts, an Australian one carries ATO and Australia Post pretexts. You pick the library; you do not write the email yourself.
- Sender spoofing. The display name and reply-to address change per campaign — a local sender domain (staff@nzpost-parcel.co.nz) reads as legitimate in a way staff@company-accounts.com does not.
- Custom content. For organisations that already know which local pretext hit them (a real BEC attempt, a genuine scam invoice), the same pretext is rebuilt as a simulation. Nothing beats staff seeing their own scam, defused.
The practical limit: localisation changes the pretext and sender, not the underlying social-engineering mechanism. Every template still trains the same skill — pause before clicking, check the sender domain, hover the link. Localisation makes that skill worth practising; it does not change what the skill is.
NZ-specific pretexts worth simulating
These are the pretexts NZ businesses most often see in the wild, all usable as simulation templates:
- IRD / Inland Revenue: 'Your tax refund of $2,340 is ready — confirm your bank details'
- NZ Post: 'Your parcel is held at customs — pay $3.99 delivery fee'
- Bank card suspension: ANZ/ASB/BNZ/Westpac 'unusual activity — verify your identity'
- Microsoft 365 password expiry: the pretext every NZ office sees weekly, with the O365 login page clone
- Shared drive / SharePoint: 'Your document has been shared — sign in to view'
- Invoice fraud (BEC): supplier bank-details-change email, the pretext behind most business email compromise losses
The last two matter because they target businesses, not consumers — a staff member's personal scam sense does not transfer automatically to a supplier email that looks like it came from a company they actually deal with.
Generic templates still earn their place
Two caveats:
- A lot of real phishing is generic. M365 password-expiry emails, shared-document notifications and LinkedIn-view notifications are world-English with no local flavour. Training staff only on localised pretexts under-trains them for these.
- Over-fitting to last month's scam trains recognition of one pretext, not the general skill. A mixed campaign — some localised, some plain — covers both.
The right structure for most NZ organisations: a localised campaign every second month, a generic one in between, and reporting that shows which template family produces the highest click rate in your organisation. That last number is the one that matters — it tells you where your own staff are weak, not where staff are weak in general.
What to measure after a localised campaign
A simulation without measurement is theatre. After each localised campaign, track:
- Click rate per template family — tells you which pretext fools the most staff.
- Report rate — how many staff forwarded it to IT or used the 'Report phishing' button. This is the metric that actually reduces real-world risk.
- Repeat clickers — the handful of names that click every campaign, who need one-on-one follow-up rather than another generic email.
Cyber Aware's human risk reporting surfaces all three automatically, so the campaign produces a conversation with the client rather than a single number in an email.
FAQ
Can phishing simulation templates be localised for New Zealand scams in 2026? Yes. Template sender, pretext, currency and language can all be set per campaign, so an NZ campaign can use IRD, NZ Post or NZ bank pretexts indistinguishable from the real scam emails NZ staff receive.
Which NZ pretexts get the highest click rates? Bank card suspension and parcel-fee emails typically produce the highest click rates in NZ campaigns, followed by M365 password-expiry notifications. The exact ranking varies by organisation — which is why per-template reporting matters more than any benchmark.
Do I need to write the templates myself? No. Platforms carry a pre-built NZ template library. Custom content is only worth writing when a specific scam already hit your organisation and you want staff to see it defused.
Is localising templates legally safe? Yes, provided the simulation does not impersonate a real organisation in a way that causes harm — established simulation platforms use lookalike domains that are clearly not the real organisation's domain, and staff are told the exercise is a simulation after they click.
How often should we run localised vs generic campaigns? Alternate them. A localised campaign every second month and a generic one in between trains both the local threat landscape and the general skill, without over-fitting staff to one pretext.
One last thing
The NZ scams that actually cost businesses money in 2026 are not exotic. They are supplier bank-detail-change emails and M365 credential-harvest pages, dressed in whatever local skin the attacker thinks will work. Localising your simulation templates to match is cheap insurance against a very local problem.