Use this reference to understand sender and destination approval statuses. A sender's overall status is separate from the approval status for each destination country. After you submit a destination, check both statuses: the destination can move to Pending while the sender still shows Draft.
# In this article
# RCS sender statuses
| Status | Description | Next steps |
|---|---|---|
| Draft | Sender was created and isn't syncing. This status appears before you submit your first destination, while you prepare and test, and can continue after you submit. After submission, the sender can stay in Draft for up to one week while external review starts and the destination is Pending. | Before submission: add test numbers, record launch video, and prepare for registration. After: check destination status on the sender detail page. Only edit a sender after you submit if Iterable or a reviewer asks you to. |
| Syncing | Iterable is registering the sender with the provider. | Wait for syncing to complete, then refresh the page. |
| Failed | Sender didn't register with the provider because of an internal error. | Contact your Iterable CSM. |
| Pending | A destination has been submitted and is in initial review. | Monitor the sender detail page. Make sure the brand contact monitors verification email and responds promptly. |
| Update required | Initial review identified issues with the sender profile. | Review the flagged sender fields, make the requested updates, and resubmit. |
| Partially approved | Some carriers have approved the sender, while others are still in progress or need changes. | Check destination statuses, respond to requested changes, and resubmit as needed. You can create templates, campaigns, and journeys, and send to audiences supported by approved carriers. |
| Approved | Sender is fully approved across its target carriers. | Sender is ready to use. Each destination country requires separate approval. |
| Resubmission required | A previously approved sender requires resubmission because of a change or compliance issue. | Review the reason in Iterable, update required sender details, and resubmit. Sender is unavailable for templates and journeys until it returns to a launched state. |
# RCS destination statuses
| Status | Description | Next steps |
|---|---|---|
| Draft | Destination form has been started but not submitted. | Complete remaining fields, save your work, and submit when ready. |
| Submitted | Destination form has been submitted for review. | Monitor the sender detail page for Google and carriers to begin application review. |
| Pending | Destination form is under review by Google and carriers. | Monitor the sender detail page. Make sure the brand contact checks email and responds to requests. |
| Approved | All carriers in this destination have approved the sender. | Proceed with launch steps once the overall sender is ready to use. |
| Rejected | All carriers in this destination have rejected the sender. | Open the destination, review the rejection reason, update the requested fields, and resubmit. |
| Partially approved | Some carriers approved the sender for this destination and others rejected it. | Check destination details, identify requested changes, and resubmit to resolve remaining rejections. |
# Revision reasons
Revision requests are a normal part of registration. A request does not permanently block your launch.
| Reason type | What to review |
|---|---|
| Sender description | State the types of messages users will receive. Use a factual description instead of a tagline, slogan, or promotional call to action. |
| Launch video | Include opt-in, HELP, opt-out, and message examples that match the campaign description. For a Multi-use sender, include both promotional and transactional examples. Confirm that the video URL is accessible. If test number actions are no longer available, contact your Iterable customer success manager. |
| Campaign description or message examples | Add specific details and make sure examples match the launch video. Do not treat opt-in, HELP, or STOP as a use case. |
| Opt-in confirmation | Include program name, customer-care contact, frequency, Message and data rates may apply, and STOP instructions. |
| Call to action | Confirm the screenshot or URL shows frequency, terms, privacy, HELP, STOP, and data-rate language. |
| Brand or contact details | Confirm that website, support contact, and legal information are current and clear. |
| Consent documentation | Confirm that your opt-in URL is accessible and that the opt-in flow is clear. |
# Resubmitting updates
For instructions on correcting and resubmitting sender- and destination-level issues, see RCS Registration: Managing Approvals.