To route inbound text messages to sales reps, decide three things before you write any code: who owns a contact, what happens when that owner is away, and who gets the reply nobody picked up. Everything else is plumbing. A lead who texts back "yes, call me" and lands in a shared pile gets slower service than one who reaches a named person.
This guide is for sales teams setting up a shared number and for developers building routing into a CRM or a vertical SaaS product. We'll cover the rules first, then how they map onto an inbox with assigned teammates, then what you have to build yourself.
Start with the ownership rule
The direct answer: every contact should have exactly one owner at any moment, and every inbound text should be shown to that owner first. If a thread has no owner, it has a default queue and a clock.
Write the rule in one paragraph. Something like: "A contact belongs to the rep who first replied to them or the rep named on the deal. Anyone else who sees the thread leaves it alone unless the owner is away." That single sentence prevents most double replies and most dropped leads.
In Ready's Inbox, you name the owner with Assign in the thread header, and automations can message a contact's assigned teammate. Our guide to shared SMS inboxes for teams covers the claim-before-you-type habit in more detail.
Four routing strategies compared
The direct answer: pick one primary strategy and add the others only as fallbacks. Here's how the common ones differ.
| Strategy | Who gets the reply | Best for | Main risk |
|---|---|---|---|
| Assigned owner | The rep on the contact or deal | Active deals, repeat customers | Owner is out and nobody sees it |
| Same rep as last time | The rep who last texted this person | Long sales cycles | One rep gets overloaded |
| Round robin | The next rep in a rotation | New inbound leads | A lead gets a different rep than the one who called them |
| Shift based | Whoever is on shift | Support-heavy teams | Handoff gaps at shift change |
Notice that round robin only makes sense for contacts with no owner yet. The moment a rep replies, the contact has one, and the next inbound text should follow the owner rule, not the rotation.
The keep-the-same-rep rule
The direct answer: once a rep has texted a lead, route every later reply from that lead to the same rep, even if the rotation says otherwise. Switching reps mid-conversation is the fastest way to make a lead repeat themselves.
There's a second half to "same" that people forget: the number. A contact who texts a Ready account keeps talking to the number they already use, and when you send through the API without a from, Ready picks the number that contact already texts with. So the lead sees one number and one thread. Your routing layer only has to decide who looks at it.
If you build your own assignment, store the owner on the contact record, not on the message. Messages come and go. The owner is a property of the relationship.
After-hours handling
The direct answer: decide what a lead sees and what a rep sees outside working hours, and keep those two answers separate. The lead might get an automatic reply. The rep gets the thread when they're back.
Two platform facts shape this. First, Ready's "Auto-reply outside business hours" setting skips a reply that would land in quiet hours and never sends it later, so don't count on it to cover late evenings. Second, a reply typed in the inbox to a contact who texted in the last 24 hours can go out at any hour, while an after-hours reply built as an automation is held like any automation text. A text typed to one person in quiet hours is scheduled for their next allowed time and shows in the thread, so nobody retypes it.
A workable after-hours plan:
- Show the thread to the owner at the start of their next shift, sorted by oldest unanswered first.
- If you send an automatic acknowledgment, keep it short and make it a promise you can keep ("A teammate will reply when we open at 8 AM").
- Don't pull a second rep in just because the owner is offline. Wait for the clock in the next section.
Escalation: the clock that stops dead threads
The direct answer: give each owner a reply window, and when it expires, move the thread to a named backup, not to everyone.
A reasonable starting point for new inbound leads is a few minutes in working hours. Those numbers are yours to set based on your sales cycle, so treat any figure here as an assumption to tune. The pattern looks like this:
- Owner is notified when the reply lands. Ready can post each inbound reply to a Slack channel you pick, and automations can message the contact's assigned teammate.
- If the thread is still unanswered when the window ends, notify a backup or a manager.
- If the backup replies, reassign the thread to them so the owner rule stays true.
- Log who took over, so the next person has context.
Keep the escalation chain short. Three levels (owner, backup, manager) is plenty.
What you build yourself
The direct answer: Ready's Inbox gives you assigned teammates, but it does not ship a rule engine with round robin pools or reply-window timers. If you need those, you build them in your own app.
For a CRM or SaaS builder, the pattern is:
- Receive the inbound text through a webhook. The receive SMS API and inbound webhooks guide covers verifying and acknowledging them, and the API quickstart shows the key, first send and webhook setup.
- Look up the contact by phone number in E.164 format. If it has an owner, route to the owner.
- If it has no owner, pick the next rep from your rotation and write that rep onto the contact before you notify anyone.
- Start a timer. If the owner hasn't replied when it fires, run your escalation step.
- Check opt-outs before any automated send. A STOP is honored by Ready automatically, and you can read it with
GET /v1/opt-outs/:phone.
Make step 3 atomic. If two inbound texts from two new leads arrive at once, a naive "next rep" read can hand both to the same person.
Webhooks can arrive out of order, so write ownership with a version or timestamp check. Our post on out-of-order SMS webhooks explains why that matters.
A worked example, with assumptions
The direct answer: a small team can run on three rules and one timer. Assume a five-person sales team on one shared number.
Assumptions: new leads rotate across four reps (the fifth is a manager), owned contacts follow the owner, and the reply window is five minutes.
- Lead A texts at 10:02 AM with no owner. Rep 1 is next in rotation and is written onto the contact.
- Lead A texts again at 10:30 AM. The owner rule applies, so it goes to Rep 1, not Rep 2.
- Lead B texts at 6:40 PM. The owner is off shift, so the thread waits in Rep 3's queue with a morning reminder.
- Lead C texts at 10:10 AM and Rep 2 doesn't answer by 10:15 AM. The backup is notified and takes the thread, and the assignment changes to the backup.
Each of those is a few lines of logic. The hard part isn't the code, it's agreeing on the rule.
Frequently asked questions
Can Ready round robin new leads across reps?
Ready's Inbox lets you assign a thread to a teammate, but it doesn't include a round robin pool. If you need one, run the rotation in your own system or CRM and write the chosen rep onto the contact. Then use the assignment so the thread shows the right owner.
What should happen when a lead replies after hours?
The thread should wait for the owner, and the lead can get a short acknowledgment if you want one. Remember that an after-hours auto-reply setting skips quiet hours rather than sending later, so check how your reply is built.
Should a STOP reply be routed to a rep?
It doesn't need a rep to act. Ready honors STOP and clear phrases like "please stop texting me" automatically, and the contact can't be messaged again. A rep should still read replies with odd wording that no phrase list catches. Compliance remains the sender's responsibility, and the opt-out tools reduce risk rather than remove it.
Next step
Write your ownership rule today, then pick one escalation window and test it for a week. If you're building routing into a product, start with the webhook handler and the owner field before you add rotation. When you're ready to try it on a real number, sign up and send your first texts from the Inbox, or read the 10DLC explainer first so registration holds no surprises.