New Zealand's mobile market is small — 5 million people, three carriers (Spark, One NZ / Vodafone, 2degrees) — and the carriers do not offer commercial A2P routes to some of the biggest US-based SMS platforms. If your all-in-one growth platform's native SMS is powered by one of those, you'll find SMS just... doesn't send in NZ.
The three routes that work
Every viable NZ SMS gateway settles onto one of the local carrier partnerships. The three we've tested and shipped to clients:
- ClickSend — Aussie-owned, direct routes through Spark and One NZ. Simple pricing (~NZ$0.075/segment as of Sept 2026), decent delivery reports, native two-way inbound.
- Sinch — global tier-1 provider; slightly cheaper at volume but two-way inbound requires a dedicated NZ virtual number.
- Message Media — Aussie-owned; strongest UI for non-technical operators; ~NZ$0.085/segment but bundled reply-management makes the delta worth it for smaller teams.
Making two-way conversations feel native
The hard part isn't sending — it's making inbound SMS replies show up in your CRM as if they were sent through it natively. There are two patterns we use:
Pattern A — webhook back into a Conversation record
Every provider above posts inbound SMS to a webhook. Route that webhook into your workflow builder (native webhook trigger, or via Zapier / Make.com for stacks that don't do it natively), then create or update a Conversation record on the matching contact. Your team sees a normal thread in the same inbox they'd see LC Phone / native SMS in.
Pattern B — number-forwarding + manual reply
For low-volume clients we sometimes buy a NZ virtual number from the SMS gateway and forward inbound SMS to a shared email inbox. Team replies from a canned response link that fires the outbound message via API. Cheap, works, doesn't scale past ~50 threads/day.
Common gotchas
- Sender ID display — NZ allows alphanumeric sender IDs (up to 11 chars) but only for one-way traffic. If you send from 'OmniPipes' the recipient can't reply. Always ship two-way conversations from a numeric shortcode or a dedicated long-code virtual number.
- Segment length — GSM-7 gives you 160 chars per segment, UCS-2 (any emoji or non-Latin char) drops that to 70. Multi-segment SMS is billed per segment, so an emoji-heavy 200-char message becomes THREE segments not one.
- Compliance — the Unsolicited Electronic Messages Act 2007 (UEM Act) requires clear consent + sender identification + an unsubscribe mechanism. Same as CASL / Spam Act / TCPA in spirit. Any SMS platform serving NZ should give you the tools; you still have to use them.