# Creating an Automated TXT Out

Automated TXT Outs let you send TXT messages to contacts based on dates or lifecycle events — without having to manually send each time. Common uses include:

* Sending a birthday TXT
* Following up with a contact a set number of days after a purchase
* Notifying a contact before their subscription expires
* Sending a welcome TXT when a contact joins, with follow-ups one and two weeks later

***

### Creating an Automated TXT Out

When you create an Automated TXT Out you are taken to the Automated TXT Out Dashboard. From here you can step through the wizard:

1. **Content and Preview**
2. **Filter**
3. **Dedupe**
4. **Recurrence**
5. **Activate**

An Automated TXT Out will not run until it has been activated. Once activated, the dashboard updates to include reporting and a history of runs. To make changes, deactivate it first.

Use **Run Now** to trigger the Automated TXT Out immediately outside of its schedule.

***

### Content and Preview

Content and Preview works the same way as for a standard TXT Out. Write your message, add merge fields, and include a STOP opt-out instruction if required. Use the preview function to check merge fields against database contacts.

See TXT Message Guidelines for guidance on when a STOP message is required.

***

### Filter

The filter for an Automated TXT Out works similarly to a standard TXT Out filter, with the addition of a **When Filter**.

#### When Filter

The When Filter lets you target contacts based on date fields using relative operators, for example:

* *5 days after Purchase Date*
* *2 days before the anniversary of Birthdate*

**Anniversary options** ignore the year part of a date. This means the Automated TXT Out will send each year on the correct day and month, regardless of the year in the database.

The Filter and the When Filter work together as an **AND** condition — both must be true for a contact to be included.

*Example: Filter — City = Auckland, When Filter — 2 days before the anniversary of Birthdate. This will only send to contacts in Auckland, two days before their birthday.*

Use the preview function to test your filter logic by selecting a date and clicking **Refresh**.

#### Automatically excluded contacts

As with standard TXT Outs, contacts flagged as **GNA** or who have **opted out** are automatically excluded. Contacts are marked GNA when three consecutive TXT messages to their mobile number fail to deliver.

***

### Dedupe

The Dedupe screen removes duplicate contacts from each run of the Automated TXT Out. Duplicates are calculated at the time the Automated TXT Out runs, not when it is set up.

Select the field or fields that indicate a duplicate. To prevent duplicates in your database, set Unique Fields under **Database > Edit Database Fields**.

***

### Recurrence

Set how often the Automated TXT Out should run — for example, daily, weekly, or monthly.

***

### Activate

Once you are satisfied with your setup, activate the Automated TXT Out. The dashboard will update to show reporting and a run history.

To make changes after activation, deactivate the Automated TXT Out first, then edit and reactivate.

***

### TXT Out Projections

Once your Automated TXT Out is active, the **TXT Out Projections** section shows how many messages are expected to be sent on future dates. Click on a date to see the projected send count for that day.

Projections are estimates based on current data. The actual number sent may differ if your database changes before that date.


---

# 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/channels/txt/creating-an-automated-txt-out.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.