STRAX Reach · Messaging apps
RCS business messages through Twilio
RCS shows your logo, a verified badge and tappable buttons inside the default Android messaging app. Reach sends through a Twilio Messaging Service and falls back to SMS for handsets without RCS.
- Verified brand sender
- SMS fallback
- Rich cards and chips
A richer text message that still reaches everyone
Reach sends from a Twilio Messaging Service whose sender pool holds your approved RCS agent and an SMS number. Twilio tries RCS first and delivers by SMS when the handset or network cannot receive it, or you can choose RCS only per environment.
Rich cards, suggestion chips and carousels come from templates you build in Twilio's Content Template Builder. Your systems queue the template id with its variables, and the client sees a card with buttons such as Pay now or Talk to us.
Replies arrive on the Messaging Service webhook, signed by Twilio with your auth token. A tapped suggestion is filed as its label, and the client's number stays the same identity whether the reply came over RCS or the SMS fallback.
Where it helps
Payment requests with a button
Send a monthly premium or account payment request as a card with a pay button and a second button to reach an agent.
Verified sender against phishing
Clients see your verified brand name and logo, which makes spoofed payment messages easier to spot.
Delivery of card and statement notices
Tell a client that a replacement card is at the branch, with a chip to book a collection time.
What you need
-
An approved RCS sender
Registered with Twilio, which handles the brand and carrier verification.
-
A Twilio Messaging Service
With the RCS sender and an SMS number in its pool, plus a public address for the incoming webhook.
-
Your Twilio keys
Account SID, the Messaging Service SID and the auth token, kept in the STRAX credential vault.
-
Reach Core
Keeps RCS, SMS and every other channel on one client timeline.
Good to know
RCS reach depends on the handset, the mobile network and the sender approval in each country. Keep SMS fallback switched on until you have measured how many of your clients receive RCS.
Questions
What do clients without RCS receive?
With fallback on, Twilio sends the text as an ordinary SMS from the number in the Messaging Service.
How do we build a card?
Create a card or carousel template in Twilio's Content Template Builder and queue it from your systems by its template id with the variables filled in.
Are replies to a fallback SMS recorded too?
Yes, both arrive on the same webhook and land on the client's record under the same number.
How long does sender approval take?
Brand verification runs through Twilio and the carriers and usually takes a few weeks. Start it before you build the flows.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add RCS via Twilio to Reach
Tell us which channels your clients use and we will plan the rollout with your team.
Premium Requires STRAX Reach - Core, which is licensed.
About this listing
| Version | 1.0.0 |
| Author | STRAX |
| Category | Communication |
| Published | 2026-09-24 |
What's inside
| Credential | 1 |
| Global variable | 1 |
| Workflow | 2 |
What happens on install
After the import, and only with your consent, the installer runs:
- Reach - Register Channel : Registers the RCS via Twilio channel with Reach Core, disabled until its credentials are entered
Free listing
Install it from Feature Marketplace inside STRAX
It builds on STRAX Reach - Core, a premium package. Ask us for a quote to license it first.
Open Feature Marketplace
In your STRAX installation, open Feature Marketplace from the navigation.
Find "STRAX Reach - RCS Twilio"
Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.
Install
Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.
RCS, Android and Twilio are trademarks of their owners, named here only to identify the service this package connects to.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.


