Skip to main content

NEW ZEALAND (NZ)

Locale Summary

Locale nameNew Zealand
ISO codeNZ
RegionOceania
Mobile country code530
Dialing code+64

Guidelines

Two-way SMS supported Yes
Number portability availableYes
Twilio concatenated message supportYes
Message length-----
Twilio MMS supportConverted to SMS with embedded URL
Sending SMS to landline numbersYou cannot send SMS to a landline destination number: the Twilio REST API will throw a 400 response with error code 21614, the message will not appear in the logs, and the account will not be charged.
Compliance considerations

Due to local carrier restrictions, sender IDs will be overwritten with a random short code for all SMS traffic to New Zealand. Deliverability by random shortcode is on a best-effort basis. For compliance, New Zealand’s mobile operators require the content “Reply to this SMS will be charged” to be added to every message sent to New Zealand. If you are sending mission-criticial and time-sensitive messages, it is highly recommended that you contact Twilio to learn how to get dedicated shortcodes.

Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. The following are some general best practices:

  1. Get opt-in consent from each end-user before sending any communication to them, particularly for marketing or other non-essential communications.
  2. Only communicate during an end-user’s daytime hours unless it is urgent.
  3. SMS campaigns should support HELP/STOP messages, and similar messages, in the end-user’s local language.
  4. Do not contact end-users on do-not-call or do-not-disturb registries.

Phone Numbers & Sender ID

AlphanumericLong CodeShort Code
Pre-registrationDynamicDomesticInternational
Operator network capabilityNot SupportedNot SupportedNot SupportedNot SupportedSupported
Twilio supported --- --- --- SupportedSupported
Sender ID preserved --- --- --- NoYes
Provisioning timeN/AN/AN/AN/A2 - 4 weeks
UCS-2 supportN/AN/AN/ASupportedSupported
Use case restrictions

N/A

N/A

N/A

Mobile operators in New Zealand require SMS messages to be delivered through dedicated short code Sender ID only. Numeric Sender IDs will be overwritten with a random shared short code Sender ID outside Twilio’s platform, and delivery is on a best-effort basis only.

Refer to our FAQs for short code best practices.

Best practices

N/A

N/A

N/A

N/A

Refer to our FAQs for short code best practices.

Alphanumeric - Pre-registration
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Long Code - Domestic
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Long Code - International
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

Mobile operators in New Zealand require SMS messages to be delivered through dedicated short code Sender ID only. Numeric Sender IDs will be overwritten with a random shared short code Sender ID outside Twilio’s platform, and delivery is on a best-effort basis only.

Best practices

N/A

Short Code
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning time2 - 4 weeks
UCS-2 supportSupported
Use case restrictions

Refer to our FAQs for short code best practices.

Best practices

Refer to our FAQs for short code best practices.

For the benefit of all our customers, these guidelines are provided to help you comply with applicable requirements and to help ensure Twilio's platform remains compliant with global telecommunications ecosystem requirements. These guidelines represent our current understanding of common compliance requirements generally applicable to Twilio and its customers, and do not constitute legal advice. By posting these guidelines, Twilio makes no assurances regarding the legal compliance of your application built using our APIs. You are expected to understand and abide by all compliance obligations applicable to your specific application. You should check these pages regularly for updates as telecommunications ecosystem requirements continue to evolve and change, and the information below may be updated or changed without notice.