NEW ZEALAND (NZ)

Country Summary

Country nameNew Zealand
ISO codeNZ
RegionOceania
Mobile country code530
Dialing code+64
Major carriersVodafone, Telecom NZ, 2degrees

Guidelines

Two-way SMS supported No
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 into a random short code for all SMS traffic to New Zealand. Sending gambling-related content is strictly prohibited in New Zealand. Unsolicited Communication—All commercial electronic messages sent to an electronic address in Australia are beholden to the SPAM Act (2003). It is a partner’s responsibility to be familiar with this legislation and ensure compliance; you can find the key rules relating to this requirement being at https://www.acma.gov.au/theACMA/spam­industryobligations and below: - Permission (consent)—Messages can only be sent with the permission of the person who owns the account for the address (usually the recipient). - Identification—Messages must contain the name and contact details of the person or business that authorized the message (sender identification). - Unsubscribe—Messages must contain a low (or no-cost) way for the recipient to stop receiving messages (to ‘opt out’ or unsubscribe).

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, particular 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

PreregisteredAlphanumericLong CodeShort Code
Operator network capabilityNot RequiredNot SupportedNot SupportedSupported
Twilio supportedNot RequiredNot SupportedSupportedNot Supported
Sender ID preserved --- --- No ---
Provisioning time--------
UCS-2 support --------
Use case restrictions ----Numeric sender IDs would be overwritten to generic shortcode to ensure delivery--
Best practices ----You may use a global SMS-capable number to reach mobile phones in New Zealand; however, the sender ID will be overwritten to a short code.--
Preregistered
Operator network capabilityNot Required
Twilio supportedNot Required
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices --
Alphanumeric
Operator network capabilityNot Supported
Twilio supportedNot Supported
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices --
Long Code
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning time--
UCS-2 support --
Use case restrictions Numeric sender IDs would be overwritten to generic shortcode to ensure delivery
Best practices You may use a global SMS-capable number to reach mobile phones in New Zealand; however, the sender ID will be overwritten to a short code.
Short Code
Operator network capabilitySupported
Twilio supportedNot Supported
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions --
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.