A2P SMS, OTP, and sender ID rules in New Zealand.
BroadNet delivers A2P SMS and OTP in New Zealand over direct connections to Spark NZ, One NZ, and 2degrees; sender IDs need no formal pre-registration with DIA. Direct termination into Spark NZ, Vodafone NZ (One NZ), and 2degrees with privacy-aligned operations.
From-rates by channel in New Zealand
- SMSfrom$0.0460per SMSIndicative list rate, reviewed September 24, 2026Volume pricing available
- OTPRequest a quote Channel list rate from $0.0120 per verification (all markets)
- WhatsAppRequest a quote Channel list rate from $0.0135 per template message (all markets)
- RCSRequest a quote Channel list rate from $0.0080 per session (all markets)
- VoiceRequest a quote Channel list rate from $0.0150 per minute (all markets)
Indicative list prices in USD, excluding taxes and sender-ID registration fees. Final per-operator pricing is confirmed in your quote.
The New Zealand A2P market at a glance.
New Zealand is served by 3 licensed mobile networks (Spark NZ, One NZ, and 2degrees) covering a subscriber base of 6M. Department of Internal Affairs (DIA) regulates A2P messaging and sender-ID registration. No sender-ID registry has been published for New Zealand; alphanumeric sender IDs should identify the business, and operator requirements are confirmed during onboarding. Unsolicited Electronic Messages Act 2007 + Privacy Act 2020 enforced. OPC supervises.
Technical facts for New Zealand
Network codes, message lengths and sender-ID rules in one table. Segment lengths are the GSM standard values (3GPP TS 23.038).
| Mobile country code (MCC) | 530 |
|---|---|
| Dialling code | +64 |
| Operators (MCC-MNC) |
|
| SMS length, GSM-7 (Latin alphabet) | 160 characters in a single SMS; 153 per part when concatenated |
| SMS length, UCS-2 (Arabic, Cyrillic and other scripts) | 70 characters in a single SMS; 67 per part when concatenated |
| Regulator | DIA (Department of Internal Affairs) |
| Sender-ID rules | No sender-ID registry has been published for New Zealand; alphanumeric sender IDs should identify the business, and operator requirements are confirmed during onboarding. |
| Sender-ID lead time | Free-form |
Channels live in New Zealand.
One contract, one contact model. Fall back between SMS, WhatsApp, and Voice with shared opt-in evidence and a single audit trail.
SMS
Operator-direct A2P with alphanumeric sender support on transactional traffic.
OTP
Sub-3-second median across the three major networks.
WhatsApp Business API live; modest penetration relative to SMS.
RCS
RCS Business Messaging available via Google MaaP on enabled carriers.
Voice
Voice OTP / TTS available as SMS fallback.
How do I register a sender ID in New Zealand?
Filed end-to-end by BroadNet's compliance team — KYC pack, operator approval, and renewal cycles handled on your behalf.
DIA · Spark NZ and One NZ
- Format
- Alphanumeric (where supported) or numeric long-code / short-code
- Pre-registration
- No published sender-ID registry; operator requirements confirmed during onboarding
- KYC documents
- Confirmed during onboarding
- Renewal cycle
- Confirmed during onboarding
- Common rejection causes
- Sender-ID rules are set by the operators; BroadNet confirms current requirements during onboarding.
What OTP delivery looks like in New Zealand.
Latency profile, peak-hour behaviour, recommended fallback chain, and the fraud signals our firewall watches in-market.
Typical latency window
Median 2.9 s with a 95th-percentile inside 8 seconds across operator-direct binds. Two-shot delivery confirmed by DLR.
Peak-hour behaviour
Operator throughput holds steady through local business peaks; throttling kicks in only during outlier mass-send events. BroadNet load-shapes per-MNO to avoid firewall blocks.
Fallback chain
Recommended fallback: Voice OTP after 30s no-delivery. WhatsApp available as an additional channel.
Fraud signals we watch
Watch for SIM-swap fraud on banking flows and for marketing senders that drift outside the registered traffic class.
What you can — and can't — send.
Opt-in, opt-out, quiet hours, content restrictions, and the penalty regime for the New Zealand market.
Opt-in
Spam Act / equivalent requires inferred or express consent, with the source of consent logged and reviewable.
Opt-out
STOP keyword and clearly stated unsubscribe required on every marketing send. Honoured within 5 business days at most.
Quiet hours
We have not found a regulator-published time-of-day window for promotional SMS in this market. Agree sending hours with the operator and schedule promotional sends for the recipient's local daytime; transactional traffic runs 24/7.
Content restrictions
Misleading-sender provisions apply; sender-ID brand must match the registered identity. Gambling and adult content require licence evidence.
Regulator penalties
DIA can issue infringement notices and pursue civil penalties — typically scaled per breach and per recipient.
Termination,
network by network.
The route status column shows how each operator is reached — a direct BroadNet bind or a labelled partner route. No grey-route exposure. Route grades are indicative planning guides, not live measurements.
| Operator | MCC-MNC | Route status | Grade | A2P rate (typ.) |
|---|---|---|---|---|
| Spark NZ | 530-05 | Direct | A+ | USD 0.0506 |
| One NZ (Vodafone NZ) | 530-01 | Direct | A+ | USD 0.0483 |
| 2degrees | 530-24 | Direct | A | USD 0.046 |
Rates shown are typical pay-as-you-go for transactional traffic. Promotional traffic is priced separately, and volume tiers reduce both. See the rate-card section below for the full ladder.
| Tier | Transactional | Promotional | Notes |
|---|---|---|---|
| Pay-as-you-go | USD 0.0460 | USD 0.055 | List rate up to 100K messages/month |
| Growth · 100K+ | USD 0.0405 | USD 0.0488 | Auto-tier discount |
| Volume · 1M+ | USD 0.0340 | USD 0.0410 | Includes quarterly route review |
| Enterprise | Custom | Custom | Direct operator pricing + signed SLA |
No published sender-ID registry; operator requirements confirmed during onboarding.
Open the New Zealand rate cardCompliant
by default.
Every send is pre-screened against Department of Internal Affairs (DIA) rules, the operator firewalls, and the local privacy framework. Where registration is required, BroadNet files the paperwork on your behalf.
Unsolicited Electronic Messages Act 2007 + Privacy Act 2020 enforced. OPC supervises.
Full regulatory deep-diveNo published registry
Alphanumeric sender IDs should identify the business; operator requirements are confirmed during onboarding.
Privacy Act 2020
Enforced by OPC.
Unsolicited E-Messages Act
Opt-out and sender identification required; enforced by the Department of Internal Affairs (DIA).
Programmes that work well in New Zealand.
Where the BroadNet operator-direct footprint, the local regulator regime, and consumer messaging habits line up.
- 01
Banking and fintech OTP and AML-aligned transaction alerts.
- 02
E-commerce and click-and-collect notifications.
- 03
Government and public-sector citizen messaging.
- 04
Healthcare appointment reminders aligned with national privacy law.
- 05
Travel, airline, and itinerary-update messaging.
What we run for New Zealand senders.
The operator relationships, the compliance workflow, the routing position — all on a single contract and a single account team.
Operator-direct binds with Spark NZ, One NZ, and 2degrees — no aggregator hops, no grey-route exposure.
Sender-ID requirements confirmed during onboarding.
Live in 5–15 business days from test-access request to production, with a dedicated solution engineer through go-live.
Typical delivery rate 99.5% and typical OTP delivery time 2.9 s across the country.
Spam-Act-aligned opt-in and audit-trail handling included.
Local-number presence and alphanumeric sender support across all three networks.
Buyer questions about New Zealand.
The questions BroadNet's sales engineers field every week from teams shipping into this market.
What's the typical sender-ID approval time with DIA in New Zealand?
Typical lead time: Free-form. BroadNet confirms the current sender-ID requirements and documents during onboarding.
Are BroadNet's routes to New Zealand operator-direct?
Yes — every operator on the public coverage table is a direct A2P bind. No aggregator hops, no grey-route exposure. Route grades are indicative planning guides, not live measurements.
Can I send marketing SMS in New Zealand without prior consent?
No. Verifiable opt-in is required across every market BroadNet supports, with the consent source, timestamp, and channel logged. Transactional OTP and account-level alerts are exempt from marketing-consent rules.
Which channels do you support for New Zealand — SMS only, or also WhatsApp and Voice?
SMS, OTP, WhatsApp Business, and Voice OTP are all supported. RCS Business Messaging is available where the local operator has launched it. All channels run on the same contract and contact model.
Can I be billed in a currency other than USD?
Yes — billing is available in USD / NZD. Volume tiers apply automatically from 100K messages a month.
Does New Zealand require local-presence numbers?
Not for OTP or transactional alerts — alphanumeric sender IDs work on all major networks. Marketing traffic from local senders typically uses a local-number identity to clear Spam-Act-style scrutiny.
What happens if a route to New Zealand degrades?
BroadNet runs continuous DLR monitoring on every operator. If a route flaps, traffic is automatically re-shaped to the next-best operator on the same destination, and your account manager is notified with a remediation note within the hour.
Do you sign an SLA for traffic to New Zealand?
Yes — traffic to this market runs under BroadNet's standard SLA: 99.99% monthly platform uptime, with service credits on enterprise contracts. Support response targets and the credit schedule are published on our Support & SLA page.
A ready-to-adapt template for New Zealand.
In the local script alongside English. Copy, swap the brand, and we'll register it as part of your sender-ID onboarding.
- Mobile subscribers
- 6M
- Sender ID lead
- Free-form
- Time-to-launch
- Live in 5–15 business days from test-access request to production
- Billed in
- USD / NZD
Your verification code is 619204.
No sender-ID registry has been published for New Zealand; alphanumeric sender IDs should identify the business, and operator requirements are confirmed during onboarding.
Continue across the region.
See how enterprises put these operator-direct routes to work in banking and finance messaging and e-commerce and retail messaging, or weigh the options on the messaging platform comparison hub.
More on New Zealand
Request current route availability for New Zealand.
Live in 5–15 business days from test-access request to production. Sender ID filed with DIA on your behalf. Billed in USD from day one.
$ curl -X POST https://api.broadnet.me/sms/sendSms·mno = +64