Built for the handset, not the spreadsheet
A message is not a row in a report. These are the features that decide whether the person holding the phone reads it, replies to it, and taps the link inside it.
- SMS, RCS
- Channels
- automatic
- Fallback
- 24 months
- Click data
RCS messaging
Rich cards where the handset supports them
Send a branded card with an image, a headline and buttons where RCS is available, and fall back to plain SMS everywhere else. One payload, one receipt, no branching in your code.
- automatic
- Fallback
- 6
- Card types
- included
- Verified sender
Two-way conversations
Every reply is an event, not a ticket in a queue
Inbound messages arrive on the same webhook as everything else, threaded to the original send. Route them to your own support tooling instead of asking agents to watch another screen.
- by message id
- Threading
- unlimited
- Keyword rules
- included
- Inbound cost
Link tracking
Know which message moved the number
Every link is rewritten on your own branded domain, shortened to protect the segment count, and attributed back to the exact message, template and player it came from.
- yours
- Domain
- per message
- Attribution
- 24 months
- Click data
Give the handset something worth opening
Every module runs against sandbox keys first, with simulated networks and forced failure codes, so you can prove the integration before a single real message is billed.