NEW ZEALAND (NZ)
|Country name||New Zealand|
Short codes are ideal for high-throughput programmatic messaging.
Short codes are approved for specific use cases, so if you are experiencing carrier filtering on long codes you may be a good candidate for short codes.
Some of the most common use-cases for short codes in New Zealand are:
Short codes can only message users on carriers within the countries in which they are provisioned.
Although Twilio can provision short codes in multiple countries, if your customers are not located in New Zealand, you should not obtain a New Zealand Short Code.
Short codes require express consent from end users before any SMS can be sent; if you cannot obtain consent you should not use a short code.
Twilio and/or the carriers will not support certain types of campaigns, including:
Please note that if you order FTEU (Free to End User) Short Code the owner pays extra to send messages for which end users do not pay.
Minimum term commit for New Zealand Short Code is 3 months.
The notice period before returning the Short Code is 1 month (provided minimum term commit has been fulfilled).
Refer to this article for detailed explanation on New Zealand Short Code Best Practices.
To apply for New Zealand Short Code please fill in the following Order Form:
The following details are included in the order form:
2 - 4 weeks, once you submit all required information and documentation.
Please expect delays on any applications submitted from December through mid January, as the wireless carriers have an annual provisioning freeze during this time.
Click to see SMS pricing, including for short codes.
To apply for New Zealand Short Code please follow these steps:
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.