Use this reference to prepare answers and supporting materials for destination approval. Before you submit, review Best Practices for RCS Compliance for more information on RCS program requirements.
IMPORTANT
The destination approval form does not autosave. Draft and review your answers before you complete the form in Iterable.
# In this article
# US destination approval form fields
The fields listed below reflect the US destination approval form. Requirements and field order can vary by country, provider, and traffic origin.
# Routing and identification
| Field | Description | Guidance |
|---|---|---|
| Country | The country you are submitting for. | See supported countries. |
| Traffic origin | Whether you are sending locally or internationally. | Select Local when your traffic stays in the destination country. Select International when you send to recipients in another country. |
| Email address | The email address that receives status notifications from the provider during review. | Use a monitored distribution list or shared inbox, not an individual's personal email. |
# Brand and partner details
| Field | Description | Guidance |
|---|---|---|
| Brand website | The brand's website. | Use a live, publicly accessible URL. |
| RCS partner name | The company that is your RCS sending partner. | This is a static value for all Iterable senders. Enter Iterable. |
| RCS partner contact person name | The contact person at your RCS partner. | This is a static value for all Iterable senders. Enter Iterable. |
| RCS partner contact person email | The email address for your RCS partner. | This is a static value for all Iterable senders. Enter rcs-support@iterable.com. |
| Brand name | The public name of your brand, as it appears on your website, app, or listings. | It can differ from your legal company name, but it must be legally associated with it. |
# Company information
| Field | Description | Guidance |
|---|---|---|
| Company name | Your company's legal name. | Use the full legal company name. |
| Company address | The registered address of the sending company. | Use the legal registered street address. |
| Company city | The city of the registered address. | Use the city from your legal registered address. |
| Country | The country where the sending company is registered. | Enter the country where your company is legally registered. This can differ from the destination country where you plan to send. |
| Company ZIP code | The ZIP or postal code of the registered address. | Use the ZIP or postal code from your legal registered address. |
| Company website | The company's website. | Use your primary company website, not a campaign microsite. |
| Tax code | The tax identifier issued when the business registered. | For US companies, use your EIN and make sure it matches your legal company name and address. |
| Industry | The company's primary business activity. | Use the category that best matches your registered activity. |
| Brand type | The legal form of the brand's company. | Select Public, Private, Government, Non-Profit, or Sole Proprietor. |
| Stock exchange | The primary home-country stock exchange abbreviation. | Required for public companies only. Otherwise, enter N/A. |
| Stock symbol | The primary stock symbol associated with the exchange. | Required for public companies only. Otherwise, enter N/A. |
| Company phone number | The company's official business phone number. | Use a main number that reaches your company directly. |
| Company region | The state, province, or region of the registered address. | Use the state or region from your legal registered address. |
# Campaign details
| Field | Description | Guidance |
|---|---|---|
| Estimated monthly volume | The estimated number of messages you plan to send monthly. | Enter a realistic estimate for planned production usage. Maximum: 2,000,000. |
| Campaign description | A plain-language description of your campaign and how you will use the sender. | Describe message types, triggers, timing, audience, and the expected user flow. Include UI elements you use, such as suggested replies, buttons, or calendar actions, and any AI or natural-language handling. For a Multi-use sender, describe both promotional and transactional programs. Don't treat opt-in, HELP, or STOP messages as a use case. |
| Campaign message example | Examples of the messages you plan to send for each sender use case. | Every example must appear in your launch video. Include exact links for URLs in message text or suggested actions. For a Multi-use sender, include at least one promotional example and one transactional example, such as an order update. Opt-in confirmation and HELP or STOP replies are required, but they don't replace a use-case example. |
| Sender launch video URL | A link to the video recording of your sender use cases. | The video must show opt-in, the confirmation message, HELP, STOP, and each campaign example. The URL must be publicly accessible without sign-in. See RCS Registration: Creating a launch video. |
# Compliance messaging
| Field | Description | Guidance |
|---|---|---|
| HELP response message | The response a user receives after sending the HELP keyword. | Match your live HELP response. Include the program name and additional contact information, such as a phone number or email address. |
| Opt-in response message | The confirmation message a user receives after opting in. | Send a single confirmation. Include your brand or program name, customer-care contact information, message frequency (for example, Max 4 msgs/mo), Message and data rates may apply, and opt-out instructions such as Reply STOP to opt out. Missing frequency is a common rejection reason. |
| Opt-out response message | The confirmation a user receives after sending an opt-out keyword. | State that the user is unsubscribed and will not receive further messages unless they opt in again. |
| Opt-in details | How, where, and when users consent to receive RCS messages. | Name the method (web form, keyword, QR code, or deep link) and describe the call to action. Click-to-chat is not a valid opt-in. One opt-in covers one program. If the sender is Multi-use, identify each use case at the call to action. Include supported opt-in keywords, such as START or YES. See Call to action and opt-in. |
| Opt-out details | How users stop receiving RCS messages. | Include supported opt-out keywords, such as STOP or UNSUBSCRIBE. After the sender is launched, a journey must identify the reply, update the RCS subscription, and send the confirmation. |
| Web opt-in URL or call-to-action screenshot URL | A public link to the website or screenshot where the user opts in. | Use a current representation of your opt-in flow. The screenshot or page must show product description, frequency, terms or a terms link, privacy policy or a privacy link, STOP, HELP, and Message and data rates may apply. Don't hide these disclosures in unrelated terms. |
# Brand contact
The brand contact monitors and responds to third-party verification requests during review. Use a person who can respond promptly to requests from Aegis Mobile and Google. For details, see RCS Registration: Managing approvals.
| Field | Description | Guidance |
|---|---|---|
| Brand contact person | The person responsible for third-party brand verification. | Use a real individual, not a shared alias. |
| Brand contact email | The email address for the brand contact. | Use a direct company email address, not a customer-facing support inbox. |
| Brand contact person role | The brand contact's job role. | Use the person's actual job title. |
| Brand contact mobile number | The brand contact's mobile number. | Use a direct mobile number, not a customer-facing support line. |
# Example approved sender application
Use this Iterable promotional sender example to see the level of detail reviewers expect. Treat it as a format reference, not copy-and-paste content for your brand. Your answers must describe your own program, assets, and compliance flows.
# Example sender and brand details
These values correspond to the fields you complete when you create an RCS sender.
| Field | Example value |
|---|---|
| Sender name | Iterable |
| Hosting region | North America |
| Billing category | Non-conversational |
| Use case | Promotional |
| Display name | Iterable |
| Description | Sends marketing offers, product release updates, and event alerts to opted-in Iterable users. |
| Accent color | #006E8B |
| Phone | +16506831194 |
support@iterable.com |
|
| Website | https://iterable.com |
| Background banner | https://library.iterable.com/1733/6139/7b07aa180f83492faa0ca621e424afca-banner.jpg |
| Logo | https://library.iterable.com/1733/6139/f8a1d5c2ad7f418296a07979a0e5104b-logo.png |
| Privacy policy URL | https://iterable.com/legal/privacy-policy/ |
| Terms and conditions URL | https://iterable.com/terms/ |
# Example US destination approval answers
These values correspond to the US destination approval form fields earlier in this article.
# Routing and identification
| Field | Example value |
|---|---|
| Country | United States |
| Traffic origin | Local |
| Email address | support@iterable.com |
# Brand and partner details
| Field | Example value |
|---|---|
| Brand website | https://iterable.com/ |
| RCS partner name | Iterable |
| RCS partner contact person name | Iterable |
| RCS partner contact person email | rcs-support@iterable.com |
| Brand name | Iterable |
# Company information
| Field | Example value |
|---|---|
| Company name | Iterable, Inc. |
| Company address | 201 Spear Street, Suite 1050, San Francisco, CA 94105 |
| Company city | San Francisco |
| Country | United States |
| Company ZIP code | 94105 |
| Company website | https://iterable.com/ |
| Tax code | ##-###### |
| Industry | Tech |
| Brand type | Private |
| Stock exchange | N/A |
| Stock symbol | N/A |
| Company phone number | 6506831194 |
| Company region | California |
# Campaign details
| Field | Example value |
|---|---|
| Estimated monthly volume | 100000 |
| Campaign description | The Iterable RCS Agent is designed to provide real-time engagement and high-utility updates to our opted-in community of marketing professionals and partners. 1. Event & Conference Engagement: We provide registered attendees of our 'Activate' conferences with real-time schedule updates, venue maps via Rich Cards, and session reminders. Suggested Actions allow users to 'Add to Calendar' or 'View Speaker Bio' directly within the message thread. 2. Product Innovation Alerts: We notify our power users of major new feature releases and platform enhancements. |
| Campaign message example |
Promotional example Text: "Our premier marketing conference is back. Join us for a deep dive into RCS, AI, and the future of cross-channel engagement. Early bird tickets are available now! https://activate.iterable.com/register" Opt-in confirmation (required; not a registered use case) Text: "Welcome, Iterable Insider! You're set to receive the latest in marketing innovation, event invites, and product updates. Max 4 msgs/mo. Msg & data rates may apply. Reply HELP for info, STOP to opt out." HELP "Iterable Support: For assistance, email support@iterable.com or visit https://iterable.com/support. Reply STOP to unsubscribe." STOP "You have been successfully unsubscribed from Iterable RCS alerts. You will no longer receive messages." |
| Sender launch video URL | In your submission, paste a publicly accessible URL to your own recording. |
# Compliance messaging
| Field | Example value |
|---|---|
| HELP response message | Iterable Support: For assistance, email support@iterable.com or visit https://iterable.com/support. Reply STOP to unsubscribe. |
| Opt-in response message | Welcome, Iterable Insider! 🌟 You're set to receive the latest in marketing innovation, event invites, and product updates. Max 4 msgs/mo. Msg & data rates may apply. Reply HELP for info, STOP to opt out. |
| Opt-out response message | You have been successfully unsubscribed from Iterable RCS alerts. You will no longer receive messages. |
| Opt-in details | Users are presented with a dedicated opt-in prompt via an In-App Message. The prompt includes a clear call-to-action with the following mandatory disclosure: 'By checking this box, you agree to receive recurring automated marketing and RCS messages from Iterable at the number provided. Consent is not a condition of purchase. Msg & data rates may apply. View our Terms and Privacy Policy.' |
| Opt-out details | Users can revoke consent and opt out of RCS messages at any time by replying with a standard opt-out keyword. Our RCS opt-out journey identifies the reply, updates the user's RCS subscription status to unsubscribed, and sends a one-time confirmation message. Supported opt-out keywords: STOP, UNSUBSCRIBE, CANCEL, END, QUIT. |
| Web opt-in URL or call-to-action screenshot URL | https://drive.google.com/file/d/1c2MsRxpaT03UDbauEsEAxtmq7ofrT0P3/view |
# Brand contact
| Field | Example value |
|---|---|
| Brand contact person | Amy Example |
| Brand contact email | amy.example@iterable.com |
| Brand contact person role | Senior Brand Manager |
| Brand contact mobile number | ########## |