> ## Documentation Index
> Fetch the complete documentation index at: https://docs.goeva.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Your business page and SMS consent

> Tell contacts what texts they will receive and how they confirm they want them.

Your public page identifies your business, shows its privacy policy and terms, and explains your texts. A2P registration uses that same page.

## What you will get

Confirmed consent from each person who wants texts from your business.

## How it works

**1. Create and publish your page**

In **Permission** during SMS registration, select **Create my page**. Eva prepares a draft from your account details. Edit your business name and contact details, policies, message frequency, and `STOP` and `HELP` instructions. Use **Preview** to check it and **Publish** to put it online; draft changes do not appear publicly until you publish.

**2. Share the published link**

The person enters their phone and checks the consent box themselves. This request does not yet enable promotional texts.

**3. Wait for their reply**

If your number can text them, they receive a confirmation text. They must reply `YES`, `SI` or `SÍ` to the same number within 72 hours to activate consent. If they previously sent `STOP`, another confirmation is not sent until messaging is enabled again.

Before submitting A2P registration, publish the version you want Twilio to review. While registration is in review, you can edit the draft, but Eva does not let you publish changes to SMS permission or policies until review ends.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.