> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/channels/txt.md). # TXT UbiQuity TXT is a fully featured TXT messaging channel built into the UbiQuity platform. You can send one-off TXT Outs to your database contacts, set up automated TXT Outs triggered by date-based conditions, or build multi-step inbound TXT programmes that respond to messages your contacts send in. Because TXT is managed alongside your other channels in UbiQuity, you can segment your audience using the same database contacts and filters you use for email and push notifications. You can also combine channels — for example, sending a TXT when an email bounces. UbiQuity TXT uses dedicated shortcodes registered with all carriers in New Zealand. The UbiQuity team will work with you to get your shortcode set up before you can start sending. *** ### What you can do with TXT * Send one-off TXT Outs to contacts in your UbiQuity database * Set up automated TXT Outs that trigger based on dates or contact data * Build inbound TXT programmes with multi-step workflows and conditional logic * Capture data via TXT — including email addresses and survey responses * Track link clicks within TXT messages * Manage opt-outs automatically using the STOP process *** ### Supported regions UbiQuity TXT supports New Zealand mobile numbers via shortcodes registered with all NZ carriers. If you need to send to international numbers, an international long code is required — contact UbiQuity to arrange this. *** ### TXT and the law TXT messaging in New Zealand is governed by the Unsolicited Electronic Messages Act 2007, administered by the Department of Internal Affairs. You are responsible for ensuring your TXT communications comply with all applicable legislation. See TXT Message Guidelines for a summary of key requirements. *** ### Using the TXT API If you prefer to integrate programmatically, the UbiQuity API supports sending and receiving TXT messages. Once your account is set up for TXT, contact UbiQuity to register your endpoint. Inbound messages will be passed through to your endpoint, and you can send messages via the API. See the UbiQuity API documentation for details. *** ### In this section * TXT Message Guidelines — Compliance requirements for TXT messaging in New Zealand * TXT Concepts — Shortcodes, keywords, programmes, and the STOP process * TXT Programmes — Set up and build inbound TXT programmes * Sending a TXT Out — Create and send a one-off TXT Out to your database * Automated TXT Outs — Schedule TXT Outs based on dates or contact data * View Messages — View message history and understand delivery statuses --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ubiquity.co.nz/documentation/channels/txt.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.