How to Register an RCS Agent
Everything you'll need to gather before we submit your RCS agent for approval — brand assets, opt-in details, use case info, and US-specific requirements.
RCS gives your customers a branded, verified messaging experience right in their native texting app. Instead of seeing a phone number, they see your company name, logo, and colors — with read receipts, rich media, and no per-segment billing surprises. Where RCS isn't available, messages fall back to SMS automatically. Nothing changes in your Avochato inbox.
To get started, you'll register an RCS agent — a branded business profile that represents your company on RCS. Think of it as your business identity, rather than just a number. This page covers everything we'll need from you to submit that registration.
Before you start
Plan for 4–6 weeks from submission to launch, longer if you're registering in multiple countries. Your submission goes through two reviews: one by Google (required for all countries) and, if you're messaging US recipients, a second review by US carriers.
Once submitted, your profile is locked and can't be edited — double-check everything before sending it our way.
If you want more than one RCS sender for the same brand (e.g., one for marketing and one for support), each needs a distinct display name. Carriers typically reject duplicates.
For a full overview of how RCS works alongside SMS in Avochato, see RCS Agent Overview.
What we need from you
Gather everything below before submitting to help@avochato.com. We'll build your sender’s brand profile, run a test message to a device you choose, and submit for review once you've confirmed the preview.
Brand profile
These details appear on the contact card your customers see.
- Display name — the brand name customers will see
- Description — up to 100 characters; no HTML, code, or special escape characters
- Logo — 224 × 224 px, max 50 KB, JPEG/JPG/PNG, hosted at a public URL
- Banner — 1140 × 448 px, max 200 KB, JPEG/JPG/PNG, hosted at a public URL
- Accent color — HEX code that meets a 4.5:1 contrast ratio against white
- Contact details — at least one phone number (E.164 format) or email; website optional
- Privacy policy URL — public, live link
- Terms of service URL — public, live link
Banner and accent color only display on Android, but you still need to provide them for review. File sizes and dimensions are enforced exactly — assets that are slightly off get rejected.
Opt-in and opt-out
Carriers verify you have explicit consent from every contact you message.
- Opt-in description — how people sign up (e.g., "checkbox at checkout")
- Opt-in screenshot or page URL — publicly accessible, showing the actual opt-in experience
- Opt-out confirmation message — the exact text sent when someone replies STOP
- Reviewer access instructions — a short note explaining how a reviewer can test your sender
Use case
- Use case description — what this sender does and how customers interact with it
- Triggers — what causes a message to be sent (reminder, confirmation, reply, etc.)
- Use case video URL — publicly hosted (YouTube, Vimeo, or similar) showing real messages and the full STOP opt-out flow
Videos are strongly preferred over screenshots — they move faster through review.
Authorized representative
Someone at your company with authority to confirm brand details. Reviewers may contact them directly.
- Full name
- Work email
- Job title
- Company website
Additional details for US messaging
The US review is separate from Google's and has additional submission and annual fees charged by brand-verification companies. Those aren't Avochato fees — they're passed through.
- Legal business name exactly as it appears on your IRS CP 575 letter (or local tax authority document for non-US entities)
- Company type — government, nonprofit, private corporation, public corporation, or sole proprietorship
- Business registration number — EIN for US companies, FTIN for non-US
- Stock exchange and symbol, if publicly traded
- Industry
- Brand contact phone number (E.164)
- Legal business address
- Monthly website traffic (integer)
- Existing short code traffic, if any, plus estimated monthly volume
- Expected monthly RCS volume
- Campaign description — what you'll send and what the customer experience looks like
- Message flow and opt-in steps
- Sample HELP reply
- Sample STOP reply
- Message service type — one category that best describes your use case (account notification, appointment reminder, two-factor authentication, promotional marketing, etc.)
You'll also need to acknowledge that your privacy policy doesn't share messaging consent with third parties, your terms of service meet carrier requirements, and your campaign complies with the CTIA short code handbook guidelines.
Country coverage
Registration is currently available for 19 countries, including the US, UK, Ireland, and most of Western Europe, plus Mexico. A single sender can be approved for multiple countries in one registration.
After you submit
Approval happens one carrier at a time. As soon as any single carrier in a country approves your sender, you can start sending there — you don't have to wait for full coverage.