Onboarding · Smerio
From a test sender to production
Published
Understand the three milestones of an RCS launch: a visual preview, messages with invited test devices, and brand and network approval.
- Preview
Check the content and the conversation.
No message sent - Test device
Send and receive with an invited tester.
Real test traffic - Launch
Complete brand and network approval.
Approved reach
A preview answers a design question
Before sending a message, sketch the exchange. What information does the customer need? What happens after a reply? What should the message say if it travels over SMS instead?
A preview helps check the content and sequence. It does not demonstrate delivery, device support or sender approval.
Start with a short exchange: a reminder, a confirmation and an acknowledgement. Every extra branch adds behavior to test.
A test device answers an integration question
For an unlaunched Google RCS agent, a recipient accepts a tester invitation before exchanging test messages. Connect a real device and exercise both directions: application to recipient, then reply or event back to your webhook.
Test-device setup and webhook configuration are the useful starting points.
| Test | Evidence to look for |
|---|---|
| Send a message | The expected content appears on the test device |
| Tap a suggested reply | The application receives the corresponding reply |
| Receive an event again | The handler avoids repeating the business action |
| Try the fallback path | The alternate message is understandable by itself |
Record what actually happened. An accepted API request and a delivered message are different outcomes.
Launch answers a reach question
Production launch introduces brand verification and approval for the networks involved. Prepare the business profile, use case, contact details and required brand information. Confirm your authority to represent the brand.
Google’s launch overview distinguishes Google-managed and carrier-managed launches. The applicable requirements depend on the networks you choose.
Approval for one network does not establish reach on every network or in every country. Check launch status and recipient capabilities for your intended audience.
Keep the milestones separate
Measure the first working preview, first real test exchange and production approval independently. This helps your team see whether the next task belongs to content design, integration work or launch preparation.
Use the same principle in your application: show the current state clearly, and do not label a sender “live” just because a preview or test succeeded.
Next: compare RCS, SMS and MMS and plan the fallback behavior.
What should we explain next? Send us your feedback.