How RCS Sender Applications Are Reviewed
When you submit an RCS (Rich Communication Services) sender for approval, the registration goes through a review process to ensure that your business, messaging use case, and sender information meet the applicable compliance and carrier requirements. The review generally involves two main stages:
Internal Review
After an RCS sender is submitted, an RCS onboarding specialist on our team reviews the application to ensure that all required information has been provided and that the submission complies with applicable messaging policies. Here's what internal reviewers check:
Reviewers verify that the sender represents a legitimate business. They check:
- Legal business name and registration details
- Official business website and contact information
- Authorized representative details
- Consistency between the brand name, website, and sender identity
- Supporting business verification or attestation documents, where required
Reviewers make sure the sender profile accurately represents the business. This includes:
- Sender display name
- Business description
- Brand logo and banner
- Business website
- Privacy Policy and Terms of Service URLs
All branding details should consistently represent the same business, and the required URLs must be accessible.
One of the most important parts of the review is verifying how customers consent to receive RCS messages. Reviewers check:
- How customers provide consent
- Whether the opt-in form is live and accessible
- Whether the consent checkbox is unchecked by default, where applicable
- Whether the consent language clearly identifies the business
- Whether the types of messages customers will receive are explained
- Whether customers can unsubscribe by replying STOP
- Whether HELP and opt-out responses meet applicable requirements
- Whether the Privacy Policy and Terms of Service are available
Reviewers may test the opt-in process. The consent flow should be functional and accessible during the review.
Reviewers verify that the intended messaging activity complies with applicable policies. They examine:
- Purpose of the messaging campaign
- Types of messages being sent, such as promotional, transactional, or informational
- Events that trigger messages
- Sample messages
- Expected message frequency
- Whether sample messages match the submitted use case
Depending on the country, additional documentation may be required. Examples include:
- Business registration documents
- Brand verification or attestation letters
- Authorization documents
- Screenshots of consent forms
- Demonstration videos showing the opt-in and messaging experience
If any information is missing or incorrect, our team may request corrections before proceeding with the registration.
Carrier Review
Once the application passes the internal review, it is submitted to the applicable carriers and verification providers. Carriers perform their own checks to confirm that the sender meets their requirements. Here's what carrier reviewers check:
Carriers verify that the business is legitimate and authorized to use the submitted sender identity. This may include:
- Validating the legal business information
- Confirming that the sender name matches the business brand
- Reviewing business registration documents
- Verifying brand ownership or authorization
For US carrier registration, Aegis, a third-party verification provider, may perform additional verification of the business and its authorized representative. Make sure the representative uses a company-branded email address and responds promptly to any verification email.
Carriers review whether the intended messaging activity is permitted under their policies. They may check:
- Campaign description
- Intended audience
- Promotional or transactional messaging purpose
- Message triggers
- Sample messages
- Expected message frequency
The submitted information must accurately represent how the business intends to use RCS messaging.
Carriers may independently test the opt-in flow to verify that customers have explicitly consented to receive messages. They check:
- Whether the opt-in process is functional
- Whether the consent language clearly identifies the business
- Whether the message purpose is explained
- Whether the required disclosures are present
- Whether STOP and HELP instructions are supported
- Whether Privacy Policy and Terms of Service links are accessible
For US carriers, applicable CTIA messaging guidelines are also considered during compliance review.
Some carriers may request information about anticipated messaging traffic. This can include:
- Estimated monthly RCS message volume
- Existing SMS messaging volume
- Expected message frequency
- Existing messaging campaigns
- Business website traffic information
Depending on the country or carrier, additional verification may be necessary. Examples include:
- Agent Verification Forms
- Brand verification emails
- Additional business documents
- Authorization or attestation letters
- Demonstration videos
- Additional campaign information
Carriers may request further clarification before approving the sender.
What Happens If Reviewers Find an Issue?
If our team or the carriers identify missing information or compliance concerns, the application may require corrections before approval. Common issues include:
| Issue | Required Action |
|---|---|
| Incorrect business information | Update the legal business details to match official records. |
| Sender name does not match the brand | Ensure consistent branding across the registration and website. |
| Opt-in form is not accessible | Provide a working opt-in form. |
| Consent language is incomplete | Include the required brand identification, message purpose, and opt-out disclosures. |
| Privacy Policy or Terms of Service links are broken | Provide valid, accessible links. |
| Messaging use case is unclear | Submit a detailed use case and representative sample messages. |
| Brand verification is incomplete | Complete the verification process or provide the required documentation. |
| Additional carrier documents are missing | Submit the requested documents. |
Once the required corrections are completed, the application can continue through the review process.
How Long Does the Review Take?
RCS registration timelines depend on the destination country, carrier, and completeness of the submitted application.
For US RCS onboarding, plan for approximately 4–6 weeks or longer for the overall process.
The review may take longer if:
- Business information needs correction.
- The opt-in flow fails verification.
- Additional documentation is requested.
- Brand verification remains incomplete.
- Carriers request clarification.
- Carrier network freezes or major holidays affect processing.
Submitting accurate and complete information can help reduce avoidable delays, but approval timelines are not guaranteed.
Checklist Before Submitting an RCS Sender
Before submitting your RCS registration, ensure the following requirements are met:
Important Things to Remember
- Our team reviews the application before submitting it for applicable carrier approval.
- Passing the internal review does not guarantee carrier approval.
- Carriers may request additional information or documentation.
- A live and compliant opt-in process is essential.
- Approval requirements vary depending on the destination country and carrier.
- Google RCS approval does not automatically guarantee approval for every carrier or country.
Once the sender receives the required approvals and is activated, it can be used for RCS messaging on supported networks.