Most "business texting" tools are built to send, and replies are an afterthought. You find out when a customer answers your appointment reminder with "can we do Thursday instead?" and the reply lands in a place nobody checks, or in a personal phone that left with an employee. Two-way texting software exists so the reply gets the same attention as the send.
This guide is for small teams that want actual conversations with customers: a shared inbox, a clear owner for each thread, and the ability to send one text to one person or one campaign to two thousand from the same tool. We make Ready, so we'll say where it fits and where it doesn't. The criteria apply no matter which vendor you pick.
What "two-way" should mean in practice
Every tool claims two-way texting. The useful test is what happens after the customer hits send:
- The reply lands in a thread, not a log. You should see the whole history with that contact: the reminder you sent, their reply, your answer, last month's promo. Without that context, a reply like "yes" means nothing.
- More than one person can see and answer it. If only the person who sent the text can reply, you have a group of personal phones, not a team inbox.
- The reply stays tied to the contact record. If you use a CRM, the conversation should sit on the contact there too, not in a separate app you have to cross-check.
- Opt-outs are handled before a human sees them. A "STOP" should suppress the contact automatically across every campaign, without anyone needing to read it first.
If a tool fails any of these, it's a sending tool with a reply viewer bolted on.
Shared inbox and routing
The inbox itself
For a team of two to ten people, the shared inbox is the product. Check:
- Unread state per conversation. You need to know which threads still need an answer.
- One view across numbers. If you run several numbers (by office, by area code, by team), replies to all of them should be reachable without logging in and out.
- Desktop and phone. Most replies get written at a desk, but someone will answer from the parking lot.
Routing: ask the specific question
"Routing" covers very different things: assigning a thread to a person, round-robin distribution to reps, or routing by keyword. Ask each vendor exactly which of those they do, because a demo can make a manual "assign to" dropdown look like automatic routing.
Be honest about your volume, too. A team handling a few dozen conversations a day usually does fine with one shared inbox and a habit of claiming threads. If you're running a support desk with SLAs and escalation tiers, you probably want a help desk tool with SMS as a channel. We cover that setup in using SMS for customer support.
Where Ready fits
Ready gives you two-way messaging in an Inbox. For teams on GoHighLevel, the native integration connects over OAuth and syncs inbound and outbound messages both ways, mapped per GHL location, so each sub-account's conversations stay separate. That's the difference between native sync and a webhook relay, which tends to lose threading. We break that down in native vs webhook SMS sync in GoHighLevel. If you need rule-based assignment logic, check the docs against your exact workflow before committing.
Bulk and one-to-one sending in the same tool
Most small teams need both modes, and splitting them across two products is where things break. The campaign goes out from one tool, the replies come back to another, and nobody connects them.
What to check:
- Campaign replies land in the normal inbox. When 2,000 people get your "spots open this Saturday" text and 60 reply, those 60 should be ordinary conversations that anyone on the team can pick up.
- Opt-outs are shared. Someone who texts STOP to a campaign must be suppressed from one-to-one sends too. In Ready, an opt-out propagates across campaigns, and sends to opted-out or numbers on your Ban list are refused up front and not charged.
- Templates work in both modes. Reusable templates save time on the replies you type twenty times a day.
- Drip campaigns stop when someone replies. Check how the tool handles a contact who answers mid-drip.
For the mechanics of sending to thousands (throughput, carrier caps, batching), see our bulk SMS service guide.
Automation without pretending a bot is a person
Automation belongs on the predictable edges of a conversation: confirmations, reminders, after-hours acknowledgements. Our post on automated SMS replies and after-hours messages has templates for those.
Watch for vendors who market AI that "handles your replies." Ask whether the AI sends on its own, what it does when it's wrong, and who is liable when it promises a refund you don't offer. For the record, Ready's AI helps you write messages and runs a spam-filter check before you send. An in-app assistant answers questions and takes actions on your account. Ready no longer lets accounts create AI reply agents, but one set up earlier may still answer texts on its own until you pause its automation in Automations, and the Take over button in the Inbox thread stops it in that conversation. A person sends the reply.
Compliance: the part that decides whether texts arrive
Two-way texting doesn't exempt you from carrier rules. Customers can reply only if your texts arrive, and unregistered traffic gets filtered.
| What to look for | Why it matters | How Ready handles it |
|---|---|---|
| 10DLC registration | Unregistered business traffic is carrier-filtered | Brand and campaign registration in-app; most approvals take 2 to 7 days |
| STOP handling | Opt-outs must be honored everywhere | Automatic, and it propagates across campaigns |
| Quiet hours | Reduces TCPA exposure for texts sent at bad local times | Campaigns, drip campaigns and automations wait up to 24 hours for the window; a one-to-one or API text is held only if the window opens within 6 hours, otherwise it is refused with 409 QUIET_HOURS_BLOCK and must be resent; a one-to-one reply to someone who texted you in the last 24 hours goes out at any hour. Charged only when sent. |
| Litigator / DNC screening | Known complainers are a lawsuit risk | Scrubbing available, off by default, $0.003 per segment when switched on |
| Consent records | You need to show the contact opted in | Ready records the sender's attestation per bulk send and per API send that sets consent_attested; your store or form keeps the per-contact opt-in record |
Registration costs $25 at submit, which covers the first month. After that it's $25/mo for registration and $2 per number. There's no setup fee.
None of this makes a sender immune to TCPA claims. Compliance is ultimately yours. A good tool reduces the ways you can get it wrong.
The cost math, including the part people forget
Here is the line that surprises people in two-way texting: replies cost money. Most providers bill inbound messages, and Ready bills a reply like a sent text. A tool that gets more conversations going also generates more inbound segments.
Segments matter too. A plain-text SMS segment holds 160 characters, and longer messages split into 153-character parts. One emoji drops the limit to 70 characters (67 per part). Ready swaps curly quotes and long dashes for plain ones before sending, so those don't change the count.
Worked example (assumptions stated)
Assume a small service business sends in a month:
- 1,500 one-to-one texts, one segment each
- 1,200 customer replies, one segment each
- One campaign to 2,000 consented contacts, 200 characters of plain text = 2 segments each = 4,000 segments
Total: 1,500 + 1,200 + 4,000 = 6,700 segments.
On Ready Standard at $0.0075 per segment plus a $0.0045 carrier fee per segment:
- Rate: 6,700 × $0.0075 = $50.25
- Carrier fee: 6,700 × $0.0045, itemized separately on the bill
- Registration with one number: $25/mo for registration and $2/mo per number
That all-in figure excludes the compliance surcharge. Scrubbing and landline validation are each $0.003 extra per segment when switched on for the account, and both are off by default. Add one emoji to that campaign and it becomes 3 segments per contact: 6,000 campaign segments instead of 4,000.
Honest comparison
Raw APIs like Twilio (around $0.0083 per segment) and GoHighLevel's LeadConnector (around $0.0083 per message) charge less per text. If you have engineers to build the inbox, the opt-out logic and the registration flow yourself, that can be the right call. Compare on what's included: Ready bundles registration, compliance, the inbox, CRM, pipeline and automations. Per-seat texting apps like OpenPhone are also perfectly fine for a two-person team that mostly wants a business number on their phones. Where they get expensive is adding seats as the team grows. See current card pricing at tryready.com/pricing.
Extras worth knowing about
- Local presence. Ready can send from your number closest to the contact's area code. Every number still sits on your registered campaign. Teams turn it on because a local number looks familiar.
- Blue line (iMessage). Texts appear blue on iPhones with your business name and photo. It costs $99 a month per line plus 6 cents a segment, and replies are 6 cents a segment too. Each line can start up to 50 new conversations a day, and it needs no 10DLC registration. Replies land in the same inbox thread. Campaigns still go from regular numbers. Docs: docs.tryready.com/guides/imessage.
- Calling from the same thread. The Ready Dialer adds click-to-call from the dashboard or GoHighLevel at $0.025/min. Only answered time is billed, and missed calls show up as a Missed call card in the contact's Inbox thread.
- An API if you're building. If you run a platform that texts on behalf of your own customers, the same sending works over REST with sub-accounts per customer:
POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: <uuid>
{"to": "+12125550199", "body": "Your order #1042 has shipped.", "consent_attested": true}Full reference: docs.tryready.com/api/messages.
The short version
Pick two-way texting software by what happens to the reply:
- Does it land in a shared thread tied to the contact?
- Can the right person find and answer it?
- Is STOP enforced everywhere?
- Do you understand that replies and extra segments are billed?
Then check registration, because none of it matters if carriers filter the send.
If you want to test Ready against that list, sign up and use your first 20 free one-to-one texts before you register. You can send up to 500 texts a month before registration is required, and a card on file is needed to send. Text yourself, reply, text STOP, and see where each message lands.