A customer texts your business number: "Can I move my Thursday appointment?" Within ninety seconds they get two answers. One says "Sure, how about Friday at 10?" The other says "Thursday is full, but Monday works." Both came from your team, from the same number, in the same thread. The customer now trusts neither.
That is the core problem with a shared texting number. The number is shared, but each reply is written by one person, and nothing stops two people from answering at once unless you put rules in place. This guide covers how to route incoming texts, decide who owns a conversation, hand off cleanly, handle opt-outs as a team, and what a busy two-way inbox costs. It also covers what Ready provides and what you'll still need to handle through team process.
Why shared numbers break down
A shared number usually falls apart in one of four ways:
- Double replies. Two people see an unread message and both answer.
- Orphaned threads. Everyone assumes someone else has it, so nobody answers.
- Lost context. The person who picks up a thread on Tuesday has no idea what was promised on Monday.
- Compliance slips. Someone texts a contact who already opted out, often from a personal phone or a different tool.
Software helps with all four. None of them is purely a software problem, though. The teams that run shared inboxes well usually have a written ownership rule that every member follows, and the tool is set up to support that rule.
Routing: get each message to the right person
Routing decides which bucket a message lands in before a human reads it. For a team on one number, there are three common approaches.
Route by intent
Keywords and first-message content tell you a lot. "STOP" is an opt-out. "HELP" needs your help response. A confirm word such as "C" after a reminder is a confirmation (avoid YES, which also opts an opted-out contact back in). "Price," "quote" or "how much" usually belongs to sales. Anything that mentions an order number belongs to support. Automating the obvious cases keeps a person from spending time on a confirmation that needs no reply. We cover building this in detail in building a keyword routing tree for STOP, HELP and YES.
Route by shift
If support covers 8 AM to 4 PM and a second person covers 4 PM to 8 PM, the rule is simply "whoever is on shift owns new threads." This is the easiest rule to follow and the one most likely to stick on a small team.
Route by relationship
Sales teams often want a lead to keep talking to the same rep. The rule here is "whoever replied first owns the thread until it closes or is handed off."
You can also build routing yourself. The messaging API lets you read message history (GET /v1/messages, paginated with before_id), and the platform sends webhooks you can feed into your own ticketing or CRM logic. See docs.tryready.com/api/messages for the details rather than us guessing at payloads here.
Assignment rules that stop double replies
This part does most of the work. Pick one rule, write it down, and make it the first thing a new hire learns.
| Cause of the double reply | Rule that fixes it |
|---|---|
| Two people open the same unread thread | Claim before you type. Whoever claims the thread, by assigning it or posting a short note, owns it. Everyone else stays out. |
| Owner is slow, a teammate "helps" | Ownership window. The owner has a fixed window to reply, for example 15 minutes during business hours. After that, anyone can take it, but only after reassigning it. |
| Shift changes mid-conversation | Handoff note required. The outgoing person leaves a one-line summary and names the new owner. |
| A manager jumps in | Managers comment and don't reply. They tell the owner what to say instead of sending their own message. |
| Same contact texts two numbers | One contact, one thread. Merge or link duplicates so history isn't split. |
Two of these deserve more detail.
Claim before you type. The double reply happens in the gap between reading and sending. Claiming closes that gap. If your inbox has an assign or owner field, use it. If it doesn't, an internal note with your initial works, as long as everyone checks for it first.
Ownership windows handle the opposite failure, the orphaned thread. Without a time limit, "it's assigned to Sam" can mean nobody replies while Sam is at lunch. A 15-minute window is a reasonable starting point for support. Sales can often get away with something closer to 5, because a lead who isn't answered quickly usually texts a competitor next.
Notes and handoffs: keep the context in the thread
A good handoff note answers three questions in one line:
- What does the customer want? ("Reschedule Thursday 2 PM cleaning")
- What did we already offer or promise? ("Offered Fri 10 AM, waiting on reply")
- Who owns it now? ("Dana from 4 PM")
Put that context where the next person will see it: in the conversation itself or the contact record, not in a separate chat tool. If your team works in GoHighLevel, Ready's native integration syncs inbound and outbound messages two ways, mapped per GoHighLevel location and sub-account. Whoever opens the GHL conversation sees the full thread, including texts sent from Ready, and you can use GHL's own user assignment and notes there. If one number feeds more than one sub-account, read our audit of where inbound replies land when GHL sync is mapped per location before you assume everyone sees the same thread.
Some conversations shouldn't stay in text. When a thread gets long or tense, call the customer. The Ready Dialer lets the owner click to call from the dial pad in the dashboard or in GoHighLevel. It bills at $0.025/min and only for answered time, so a call nobody picks up costs nothing.
Opt-outs are a team problem
When a contact replies STOP or UNSUBSCRIBE, Ready honors it automatically, and the opt-out applies across campaigns, so that contact can't be messaged again from the account. Sends to opted-out numbers are refused before they go out, and you aren't charged for them. That protects you from the most common team mistake, which is a rep who missed the STOP replying anyway.
The platform can't stop someone from texting a customer from their personal phone. Your written rules should say three things:
- Nobody texts customers from personal devices. Ever.
- Nobody re-adds an opted-out contact to a list because "they called us later." If the customer wants texts again, they opt back in themselves.
- If you sync opt-outs into another system, pull them from
GET /v1/opt-outs, and checkGET /v1/opt-outs/:phonebefore another tool texts a number: the list holds only this account's opted-out contacts, not every number Ready blocks.
Late replies need a rule too. Ready enforces quiet hours based on the recipient's area, so a reply typed at 11 PM goes out at once only if the contact texted you in the last 24 hours. Otherwise it's held if the recipient's permitted hours begin within about 6 hours, and charged only when it sends; at 11 PM they are further away than that, so the reply is refused and nothing is queued. Tell your team which case they hit: a held reply must not be sent again in the morning, which would be its own kind of double reply, and a refused one must be.
Keep in mind that the opt-out handling and quiet-hours tools reduce risk, but compliance is still the sender's responsibility.
What a busy two-way inbox costs
On Ready, replies you receive are billed the same way as texts you send: the Standard rate of $0.0075/segment plus a $0.0045 carrier fee per segment. That changes how you should budget a shared inbox.
Worked example (assumptions stated): your team handles 250 conversations a week. Each averages 6 texts total (3 out, 3 in), and every text fits in one 160-character segment with no emoji.
- 250 × 6 = 1,500 segments a week
- 1,500 × ($0.0075 + $0.0045) per week
- The Standard-rate portion alone is 1,500 × $0.0075 = $11 a week, plus carrier fees on the same 1,500 segments
Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.
An emoji changes this math. It drops a segment to 70 characters, so a friendly 140-character reply with one 🙂 becomes 3 segments instead of 1. Ready swaps curly quotes and long dashes for plain ones before sending, so those characters won't inflate the count, but emoji will. For a full breakdown, see budgeting a two-way booking inbox when each job takes 6 texts.
On price: per-segment carriers like Twilio, and GoHighLevel's LC Phone, cost less per message than Ready Standard. If cost per text is your only criterion, take that seriously. Ready competes on what it includes: registration handled in-app (most approvals take 2 to 7 days), automatic opt-out handling, quiet hours, an Inbox and reusable templates. Against per-seat team texting tools, the comparison is different, because a 6-person team pays for usage rather than seats. We walk through that in our Heymarket alternative for team texting post.
Setting it up this week
A practical order of operations:
- Write the ownership rule. Use claim-before-you-type plus a reply window. Keep it to one paragraph.
- Automate the no-brainers. STOP, START and HELP are already handled. Add confirmation replies so people only see threads that need a human.
- Build templates for the ten replies your team types most. The AI message writer can help draft them and check them against spam filters, but a person sends every reply.
- Agree on the handoff note format and enforce it at shift change.
- Ban personal-phone texting in writing.
- Check your segment counts on your most common replies before volume grows.
For support-specific response-time targets and escalation paths, our guide to using SMS for customer support goes deeper.
The takeaway
A shared number works when exactly one person owns each conversation at any moment, and everyone can see who that is. Routing gets messages to the right bucket. Assignment rules and ownership windows prevent both double replies and dead threads. Handoff notes carry context forward. Automatic opt-out handling covers the mistake that costs the most.
If you want to try this with your own team, you can sign up and use the first 20 texts, which are one-to-one sends, to test the inbox before you register. Compare features and pricing at tryready.com/pricing.