If you're adding a two-way inbox to your product, you have two paths: use a conversation API you assemble yourself, or use a messaging platform that already threads replies per contact and per customer. The second gets you to a working inbox sooner.
We make Ready, so we favor the second. We haven't re-read Twilio's current Conversations docs, so check them for features and pricing.
What a two-way texting layer has to do
- Thread messages by contact and by number.
- Deliver inbound replies to the right customer's inbox.
- Handle STOP and START correctly and block later sends.
- Keep delivery status in sync.
- Respect the recipient's local calling and texting rules.
Our two-way SMS API post covers the mechanics, and receive SMS API inbound webhooks shows the webhook side.
Build vs buy for the inbox
| Piece | Build yourself | Platform provides |
|---|---|---|
| Threading | Your database design | Included |
| Per-customer isolation | Your tenancy model | Sub-accounts |
| Opt-out handling | Your code | Built in |
| Inbox UI | Your front end | Ready's app, or your own |
How Ready does it
Each customer has a sub-account with its own numbers. Replies land in an Inbox in the app, and they come to your system by webhook. Inbound replies are billed the per-segment rate plus the lower received carrier fee. The request shapes are in the Ready docs.
Ready doesn't send a text from Slack and doesn't log every text to your CRM on its own, so if you need those, plan the work.
Frequently asked questions
Can I build my own inbox UI on Ready? Yes, you can receive replies by webhook and show them in your own UI.
Does a conversation API handle compliance? Usually the API handles transport, and compliance such as opt-outs is left to you. Check the docs of the one you choose.
The practical takeaway
An inbox is mostly plumbing. If your product's value is elsewhere, buy the plumbing.