Articles in this section

See more

RCS Registration: Managing Approvals

After you submit a destination for approval, assign a dedicated owner to monitor status changes, brand-verification emails, and revision requests.

IMPORTANT

To help prevent delays:

  • Respond quickly to verification and correction requests.
  • Don't edit the sender after you submit it unless Iterable or a reviewer asks you to make changes. Editing a sender while review is in progress can delay approval.

# In this article

# Where to monitor

Check your RCS sender's detail page in Iterable regularly for status changes. Your brand contact should also monitor their email inbox for verification messages from Google and Aegis Mobile.

For sender and destination status definitions, see RCS Registration Statuses.

# Brand verification emails

After your sender moves to Pending status, your brand contact will receive two verification emails within approximately 5 to 7 business days:

  1. Aegis Mobile — This email contains a link to verify your legal business entity. Click the link to confirm. This takes under a minute and kicks off the Google verification step.
    • Expected sender address: certify@aegismobile.com
  2. Google — This follow-up email requires a direct reply to officially authorize your sender to represent your brand. Reply promptly.
    • Expected sender address: rbm-support-noreply@google.com

Both emails must be completed for approval to proceed. Delays extend the total approval timeline. Your brand contact must use a company domain email address—personal addresses are not accepted.

NOTE

Email senders may change over time. If your brand contact cannot locate an expected message, search for aegismobile.com and google.com, check spam folders, and contact your Iterable CSM.

# Resubmit updates

Revision requests are a normal part of the registration process. Receiving one does not mean your launch is permanently blocked.

# Sender-level issues

If your sender profile is rejected (for example the sender description is too vague or reads like a tagline), you should:

  1. Review the rejection reason shown in Iterable.
  2. Select Edit on the sender to update the relevant fields.
  3. After saving your changes, select Resubmit to send the updated sender for review.

NOTE

If the requested update requires a new launch video but sender-page test number actions are unavailable, contact your Iterable customer success manager. Test number actions become unavailable when the sender reaches Partially approved.

# Destination-level issues

If a destination submission is rejected (for example, if you missed or didn't provide required disclosures in your call to action, or if you used HELP or STOP replies as your transactional use-case example instead of a separate transactional message), you should:

  1. Find the destination row in the Destinations section of your sender's detail page.
  2. Select Edit next to the rejected destination. The form reopens prefilled with your previous submission.
  3. Review the rejection reason shown in the form. The reason is provided by the carrier or Google.
  4. Update the relevant fields and select Submit to resubmit.

For a deeper review of best practices to follow and some common problems to correct before resubmitting, see Best Practices for RCS Compliance and Revision reasons.

# Next steps

While approval is in progress, continue configuring RCS message types, subscriptions, and your eligible audience. Return to Step 3 in Setting up RCS.

Related articles