# Channels

### Overview

UbiQuity supports three outbound channels for communicating with your contacts: Email, TXT, and Push. Each channel has different strengths depending on your message type, audience, and engagement goals.

<table><thead><tr><th width="211.67578125">Channel</th><th>Best for</th></tr></thead><tbody><tr><td>Email</td><td>Rich content, newsletters, and detailed communications</td></tr><tr><td>TXT</td><td>Short, time-sensitive messages with high open rates</td></tr><tr><td>Push</td><td>Real-time alerts and re-engagement for app or web users</td></tr></tbody></table>

***

### [Email](/documentation/channels/email.md)

Email is the most versatile channel in UbiQuity. It supports rich content including images, layouts, and personalisation, making it well suited for newsletters, promotional campaigns, transactional messages, and anything that benefits from a designed template.

Common use cases include:

* Promotional and marketing campaigns
* Newsletters and regular updates
* Transactional or triggered communications

:point\_right: See [Email](/documentation/channels/email.md) for full details on setting up and sending email campaigns.

***

### [TXT](/documentation/channels/txt.md)

TXT allows you to send short text messages directly to a contact's mobile number. Because TXT is delivered to the device itself, it tends to achieve high open rates and is particularly effective for time-sensitive or high-priority communications.

Common use cases include:

* Appointment reminders and confirmations
* Urgent alerts or time-limited offers
* Follow-ups to email campaigns

:point\_right: See [TXT](/documentation/channels/txt.md) for full details on sending TXT messages.

***

### [Push](/documentation/channels/push.md)

Push notifications allow you to send real-time messages to users who have opted in through a mobile app. They are useful for re-engaging users and delivering timely, contextual updates without relying on email or SMS.

Common use cases include:

* Real-time alerts and updates
* Re-engagement campaigns for lapsed users
* Time-sensitive announcements

:point\_right: See [Push](/documentation/channels/push.md) for full details on setting up and sending push notifications.

***

### Choosing the right channel

If you're unsure which channel to use, consider:

* **How much content do you need to include?** Email supports rich layouts; SMS and Push are better for brief messages.
* **How urgent is the message?** SMS and Push are better suited to time-sensitive communications.
* **Where is your audience?** Push requires users to have opted in via an app or browser, while SMS requires a valid mobile number.

In many cases, channels work best in combination - for example, sending an email campaign followed by an SMS reminder to non-openers.


---

# Agent Instructions: 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:

```
GET https://docs.ubiquity.co.nz/documentation/basics/channels.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.