Make RCS and agentic messaging part of your customer solution.
Your agents already run support and sales for brands. Now they can do it in the customer’s messaging app, under the brand’s own verified name, with cards and buttons. Tap the phone.
Unlimited Plus
$65/mo · 5G · 50GB hotspot
Essential
$40/mo · 5G · 15GB
More to offer every brand you serve.
A new channel in your solution
Sell RCS and agentic messaging with what you already offer the brands you serve.
Your agents, in the thread
Customers ask in their messaging app. Your agent answers there, with cards to swipe and buttons to tap.
The brand, verified
Every message carries the brand’s own name and logo, verified by Google and the carriers.
The hard parts handled
We run brand verification, carrier review and SMS fallback, so you stay focused on your customer.
The work your agents already do, in one thread.
- Support
- Order status, plan changes, returns and appointments.
- Sales
- Lead follow-up, product choices, quotes and booking.
- Handoff
- When a person should take over, the thread goes to the team with its full history.
Standard tank
$1,450 installed · 10-year warranty
Tankless
$2,900 installed · 15-year warranty
Tap the phone. Fictional brand.
Start with one client.
Free platform. Sender setup waived. A Slack channel with our engineers through your first launch. You pay published carrier-rate messaging, plus AI credits if you run on our models. Your customer stays your customer.
Choose one brand you already serve. We set up a free branded test sender in days.
Your model or ours. One API either way.
No SDK to adopt and no agent framework to learn. REST and JSON, an API key, and compliance you cannot route around.
Listen. Reply. Hand off.
The whole integration, in the order you will write it.
// Everything the customer types or taps arrives here, signed.
app.post('/simplyrcs/webhook', verifySignature, (req, res) => {
const { event, data } = req.body;
if (event === 'message.received' && data.contentJson.type === 'text') {
// The customer typed something: hand it to your agent.
agent.handle({ conversationId: data.conversationId, text: data.contentJson.text });
}
if (event === 'button.clicked') {
// The customer tapped a button: your value comes straight back.
agent.handleTap(data.conversationId, data.buttonPayload); // "plan:essential"
}
res.sendStatus(200);
});Illustrative samples; field names follow the API reference. Everything the API gives you.
What partners ask us.
Who owns the customer relationship and the billing?
Your customer stays yours. We agree before launch whether messaging is invoiced to you or to the brand directly. There is no revenue share and no referral fee. The platform is free; messaging is at published carrier rates.
What is free for a partner?
The platform and API for every brand you connect, the $250 sender setup for each of those brands, a free branded test sender to build against, and Premium Support, a Slack channel with our engineers, through your first brand's launch. After that it is $250 a month per brand if you want to keep it.
Do we have to bring our own model?
No. Bring your own model and connect it through the API, or run your agent on ours, billed as AI credits alongside your messaging. Either way SimplyRCS carries the conversation, verifies the sender, enforces opt-outs and gives you the handoff to a person.
Who approves the sender, and how long does it take?
Google and the carriers verify each brand and agent; we prepare and run the submission. We target 2 to 4 weeks to first US send. A test sender for building against is available in days, not weeks.
Does this work with a voice agent?
Yes. Your voice agent captures consent to text on the call. When the call ends it starts the thread with POST /v1/messages/send, and the customer carries on the same conversation by typing or tapping. Store the conversationId from the response against the call.
How does our agent keep context across messages?
Every message belongs to a conversation with a stable conversationId, which rides on every webhook event and is accepted on every send. Use it as your agent's session key; everything the customer types or taps arrives tagged with it.
What happens when the phone cannot receive RCS?
Every send checks the device first. With fallbackToSms set, the message is delivered as SMS or MMS instead, and the webhook events are identical. Your code does not branch on channel.
Do you have an MCP server our agent can connect to?
Not today, and we would rather say so than imply it. The API documents MCP only as configuration for connecting a SimplyRCS bot to a tool server you run. External agents send, listen and hand off through the REST API with an API key, under the same platform-level compliance. It is a thin tool to write, and we will help you write it.
Bring one client. We’ll build the demo.
Thirty minutes with an engineer who knows the API: your agent, one brand, and a branded test sender you can build against this week.
Book a meeting
A quick fit check, your use case, our carrier coverage, and whether RCS is right for you.
Pick a timeTell us about your customers.
Make RCS part of your customer solution.
Free platform. Sender setup waived. A Slack channel with our engineers through your first launch.