> For the complete documentation index, see [llms.txt](https://docs.mercuri.cx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mercuri.cx/communication-channels/sms-integration/post-tfn-submission-finalize-your-sms-number-setup.md).

# Post-TFN Submission:Finalize Your SMS Number Setup

After submitting the TFN form, follow the steps below to complete and activate your SMS number setup.

#### 1. Setting Up the SMS Opt-in Form

Having an SMS opt-in form is crucial for collecting customer consent before sending any messages. This ensures compliance with SMS regulations and builds trust with your customers.

*For detailed instructions,* [*click here.*](/features/sms-opt-in-form/how-to-add-an-sms-opt-in-form-to-your-wix-business-website.md)

**2. Updating Your Privacy Policy**

If you already have a Privacy Policy page, please add the following section:\
\&#xNAN;*SMS and Phone Number Privacy*\
`If you provide your phone number, it will be used strictly for order updates, customer service, or other service-related communication.`\
`We do not sell, share, rent, or disclose your phone number to third parties for marketing purposes. You can opt out of receiving texts at any time by replying STOP.`\
\
**3. Adding SMS to Terms & Conditions**

Make sure your Terms & Conditions page contains a Communications (SMS) section with the following text:\
\&#xNAN;***`Communications (SMS)`***\
`By providing your contact details, you consent to receive messages about your bookings, classes, promotions, and updates through email or SMS. Message and data rates may apply.`\
`You can opt out of marketing communications anytime by following the provided unsubscribe links or replying STOP (for SMS).`


---

# 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.mercuri.cx/communication-channels/sms-integration/post-tfn-submission-finalize-your-sms-number-setup.md?ask=<question>&goal=<endgoal>
```

`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.