Verification is the step where RCS programmes stall, and it is two separate tracks. Google sender verification creates and approves the RBM agent, the verified identity that puts your name, logo and checkmark on every message. 10DLC registration is the US carrier requirement for application-to-person traffic on local numbers, filed with The Campaign Registry, and it governs the SMS and MMS fallback every RCS programme needs. Both ask for the same evidence, the legal entity, EIN, website, use case, sample messages and opt-in proof, and both reject mismatches between them. A provider that files both, from one set of documents, removes the most common cause of a launch slipping from weeks to months. The table below records what each provider documents about who does the work, checked in September 2026.
What "handles it for you" has to mean
Four things, and most providers do fewer than four:
- Preparing the submission. Collecting the brand assets, writing the use-case description and consent story in the form reviewers accept, and making the RCS agent and the 10DLC brand agree on every field.
- Filing it. Submitting the RBM agent to Google, the brand and campaigns to The Campaign Registry, and the vetting request to Aegis, under the provider's own account and relationships rather than yours.
- Working the queue. Answering reviewer questions, fixing rejections and chasing carrier activation, which is where the calendar time actually goes.
- Owning the fees. Passing the carrier, registry and vetting charges through at cost, itemised, rather than marking them up or leaving them unpublished.
The scorecard
| Provider | Google RBM sender verification | 10DLC brand and campaign registration | Aegis vetting and carrier activation | Time to first verified send | Fees documented |
|---|---|---|---|---|---|
| SimplyRCS | Filed for you, in-house | Filed for you | Filed for you | 2 to 4 weeks, stated target | $250 agent install, $200/yr Aegis, $500 T-Mobile activation, registry fees listed, all at cost |
| Sinch | Registered through the Sinch dashboard or provisioning API; Sinch submits to Google | Assisted through the account | Assisted | Sinch's own estimate: 6 to 12 weeks | Up to $500 activation, about $75 per profile change |
| Infobip | Handled during enterprise onboarding | Assisted | Assisted | Enterprise onboarding runway | Inside the quote |
| Twilio | You create the sender and complete the compliance registration in the Twilio Console; Twilio reviews it, then submits it to Google, Aegis and the carriers | You register the brand and campaigns yourself | Passed through: one-time carrier onboarding fee per sender and an annual Aegis fee, amounts not published | Twilio's guidance: allow 4 to 6 weeks | Partly: fees named, amounts not |
| Vonage | Self-serve through the Messages API and dashboard | You | You | Not stated | Not published |
| Bird | Self-serve | You | You | Not stated | Plan tiers |
| Telnyx | Self-serve | You | Passed through | Not stated | Rates published, verification fees not |
| Plivo | Self-serve, verified sender supported | You | You | Not stated | Rates published |
| AWS End User Messaging | You, through the AWS console | You | Passed through: $500 agent setup, $200/yr brand vetting, $200/month agent maintenance | Not stated | Published |
| Bandwidth | Contracted, phased onboarding | Contracted | Contracted | Contract | Fee structure published, rates by contract |
"Self-serve" is not a criticism. For an engineering-led team with a compliance function, filing through a console with good documentation is a reasonable path, and Twilio's review of the application catches errors before Google or a carrier sees them. It is the wrong path for a marketing or operations team without that function, because the forms are the easy part and the queue is the hard part.
Why the two tracks belong with one provider
The Google agent and the 10DLC brand are reviewed by different parties against the same facts, and the most common rejection on either is a mismatch with the other: a legal name that differs by a suffix, an EIN that does not match the registered address, a use case described one way to Google and another way to the registry. When one provider prepares both from one document set, that class of error disappears. When you file them yourself on two portals, or through two vendors, you are the only party who sees both, and reconciling them is your job.
There is a second reason. The verified RCS agent and the 10DLC campaigns are tied to the provider that filed them, which is why moving from Twilio without losing your numbers involves re-filing both. A provider that filed them in the first place can re-file them, in parallel with your old provider, until cutover.
What SimplyRCS files, and what it costs
SimplyRCS prepares and files your Google RBM sender verification, your 10DLC brand and campaign registrations, your Aegis vetting request and your carrier activations in-house, from one set of documents, and works the reviewer queue until the sender is live. The stated target for a first verified US send is two to four weeks. The charges behind the filing are published on the pricing page and passed through at cost on their own invoice lines: $250 one-time agent install, $200 a year Aegis sender review, $500 one-time T-Mobile activation, and The Campaign Registry schedule of $4.50 brand registration, $15 campaign vetting and $1.50 to $10 a month per campaign. Changing a sender profile you already paid to create costs nothing. Before any of that, a free sender ID test puts a verified message from your brand on your own phone. How to get RCS verified walks through the review itself step by step, and what is 10DLC covers the registry track.
Questions to ask any provider
Who prepares the submission, and from what documents? Who files the RBM agent to Google, under whose account? Who registers the 10DLC brand and campaigns? Who answers reviewer questions and chases carrier activation? What is the target time to a first verified send, and is it stated anywhere? And what are the one-time, annual and per-change fees, in writing, and are they passed through at cost? A provider that answers all six in the affirmative and in writing handles it for you. One that answers "our console has a form for that" does not, and that is fine, as long as you have the team to work the form.
- SimplyRCS files Google RBM sender verification, 10DLC brand and campaign registration, Aegis vetting and carrier activation in-house, targeting a first verified US send in 2 to 4 weeks.
- Sinch and Infobip submit the RCS agent to Google on your behalf as part of onboarding; Sinch's own first-send estimate is 6 to 12 weeks.
- Twilio, Vonage, Bird, Telnyx, Plivo and AWS are self-serve; at Twilio the sender you file in the console passes Twilio's review before submission, and Twilio's guidance allows 4 to 6 weeks.
- Google sender verification and 10DLC registration ask for the same evidence, and a mismatch between the two is the most common rejection on either.
- Verified agents and 10DLC campaigns are tied to the provider that filed them; a new provider re-files both when you move.
- SimplyRCS publishes the filing fees at cost: $250 install, $200/yr Aegis, $500 T-Mobile activation, TCR fees from $4.50, $0 to change a profile.