Your business identifies who is responsible for the messaging.Your Agent defines how that business communicates with customers using RCS.
1. Choose your RCS Type
Choose the RCS Type that best represents how you intend to use your Agent.Transactional
For notifications and updates relating to an existing customer relationship, service or transaction.Examples: Order confirmations, delivery updates, account notifications and service messages.
Promotional
For marketing, sales and promotional messaging.Examples: Special offers, discounts, product promotions and marketing campaigns.
OTP
For authentication and verification messaging.Examples: One-time passwords, login verification, password resets and transaction verification.
Multi-use
For an Agent that needs to send both Transactional and Promotional messages.Examples: Order updates, customer service messages and promotional offers from the same Agent.
2. Add your Agent details
Agent name
Enter the customer-facing name customers should recognise when they receive your messages. The Agent name does not need to be the legal name of the business. For example: Business: Example Communications Ltd Agent: Example ConnectDescription
Add a short description of the Agent, service or business. This appears as part of the customer-facing Agent profile, so keep it concise and recognisable.Use the Business Info Preview in Kero to see how your Agent may appear to customers.
3. Describe your use case
We’ll ask you three questions about how your Agent will communicate with customers.What actions trigger messages to users?
Tell us what causes your business to send an RCS message.For example: placing an order, making a payment, requesting an OTP or opting in to receive an offer.
What types of interactions will the Agent have with users?
Describe the messages and conversations customers can expect.For example: order confirmations, delivery updates, authentication codes, customer service or promotions.
How do you ensure consent?
Explain how customers agree to receive your messages, including where consent is collected and how customers can opt out where applicable.
4. Save or submit your Agent
You don’t need to complete your Agent in one session.Save Draft
Save your work if you want to review your use case, check your consent process or return to the configuration later.Status: Draft
Submit
When you’re satisfied that your Agent information is complete, submit it to Kero for review.Status: In Review
Submitting an Agent does not launch it or make it available for live customer messaging.Kero must review your submission before your Agent can proceed to testing and external verification.
5. Review, test and launch
After submission, your Agent progresses through Kero review, Agent creation, testing and external verification before launch.1
Kero reviews your Agent
A Kero Customer Success Specialist reviews your RCS Type, Agent identity, use case and consent information.Status: In ReviewKero is responsible for reviewing your submission and preparing your RCS Agent.
2
Make changes if required
If Kero needs additional information or changes, we’ll explain what needs updating.You may be asked to correct your Agent information or provide supporting details before the process can continue.
3
Your Agent is created
Once Kero has completed its review and created your Agent within the RCS ecosystem, it moves to the next stage.Status: Ready for VerificationYour Agent has been created, but it has not yet been externally verified or launched.
4
Complete final testing and verification preparation
Test your Agent on supported RCS-enabled test devices.Check its branding, message content and interactive features, and complete any outstanding verification requirements with Kero.Status: Ready for VerificationLearn how to add an RCS test device →
5
External verification and approval
Once final testing and verification preparations are complete, a Kero Customer Success Specialist submits your Agent for external verification through the relevant RCS provider.Status: VerifyingYour responsibility: Monitor your email and respond to verification requests from Google Support and the relevant mobile network operators.These requests confirm that your business authorised Kero to create an RCS Agent on its behalf.Kero’s responsibility: Coordinate external verification, follow up on outstanding requirements and manage the approval process.Learn more about RCS Agent verification and launch →
6
Your Agent is launched
Once the required approvals and launch steps are complete, your Agent can be made available for live messaging on the applicable networks.Status: LaunchedYou can now begin sending live RCS messages using your Agent, subject to the supported market and network availability.
Your RCS Agent status journey:Draft → In Review → Ready for Verification → Verifying → Launched
What’s next?
Once your Agent reaches Ready for Verification, you can complete final testing on registered RCS test devices and prepare for external verification.Testing your Agent does not mean it has been approved for live customer messaging. Your Agent must reach Launched before you can send live RCS messages.