Two-way conversations
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
Every reply is an event, not a ticket in a queue
- Inbound replies threaded to the outbound message that triggered them
- Keyword rules evaluated at the gateway, so STOP and HELP never depend on your uptime
- Auto-responses per market and per language, defined once and reused
- Long codes and short codes both supported, with the same inbound payload shape
- Full conversation history queryable by player reference
- Optional forwarding into your existing support desk through the connectors
Build order
- 1Enable inboundTurn on inbound for a sender. Nothing else in your integration changes.
- 2Set keyword rulesDefine STOP, HELP and any campaign keywords, per market and language.
- 3Handle the eventmessage.inbound arrives on the same subscription, carrying the parent message id.
- 4Route itForward to your support desk, or answer through the API with a threaded reply.
Put two-way conversations to work
Sandbox keys cost nothing and mirror the live gateway, rejections included, so your ops team can watch a message land on a handset before anything is signed.