Two-Way Texting Is a Reply Queue You Have to Staff

Updated 16 min read How we research

TL;DR: Two-way texting is not a send feature, it is an inbound queue, and the FCC writes part of the rulebook for it. Under 47 CFR 64.1200(a)(10) the words stop, quit, end, revoke, opt out, cancel and unsubscribe are per se revocations, and any other reply counts as a revocation when a reasonable person would read it that way, which is a sentence no keyword filter can enforce. Revocations have to be honored within a reasonable time not to exceed ten business days, and you may not designate an exclusive means of opting out. Run a texting protocol that cannot accept replies and the same rule makes you disclose on every message that two-way texting is not available and give another route out. So reply capacity is staffing, not customer experience. Size it from reply rate times send volume rather than message count, because 500 sends at a 10 percent reply rate is 50 live conversations landing inside an hour and one rep cannot hold 50. Watch four numbers, median minutes to a first human reply, the 90th percentile behind it, unassigned threads older than your coverage window, and opt-outs per thousand sends. Budget segments as well, since the character allowance per concatenated segment falls from 153 to 67 the moment a curly apostrophe or an emoji pushes a message out of the 7-bit alphabet. Kixie’s Team SMS holds the inbound thread in a shared inbox with automatic thread locking so two reps do not answer the same customer, and Team SMS, SMS templates and click-to-text are included on all three plans.

Your first two-way texting campaign will not fail on the send. The send is the easy half. It fails about nine minutes later, when forty replies are sitting in an inbox that nobody was assigned to watch.

That is the whole problem in one sentence. Teams buy this channel by comparing template builders, scheduling and CRM fields, then launch without answering the only question that decides whether it works. Who reads the replies, and how fast?

What two-way texting actually is

Two-way texting, also called two-way SMS or conversational SMS, is text messaging where the recipient can reply and a person or a workflow on your side answers. That is the definition. The part that costs money is what the definition hands you, which is an inbound queue attached to a clock.

Compare it to the channel it replaced. A one-way alert leaves your system and the job is done. A two-way message leaves your system and starts an obligation. Somebody now owes an answer to a person who is holding a phone and deciding whether your company is worth waiting for.

So read every question about this channel backward, from the reply. Staffing, routing, after-hours coverage, opt-out handling and cost per conversation are all downstream of two inputs: how many replies arrive, and how long they wait.

How a two-way texting reply gets back to you

The mechanics vary by platform and number type, but the chain is the same everywhere. Each link is also a place the channel breaks.

Chain of six milky frosted white glass links with thin purple edges stepping down a pale violet ground, the third link broken open with its two ends parted and the lower half of the chain sagging below the line of the upper half.
  1. Permission exists before the first message. You establish the consent or other legal basis that covers the message you are about to send, and you record where it came from.
  2. A business-enabled number sends. For application-to-person traffic to US numbers that means a registered number, not a rep’s cell phone.
  3. The reply lands in a system, not a pocket. This is the first failure mode. If replies route to a personal handset, the conversation is invisible to everyone else and dies when that rep leaves.
  4. The reply is matched to a record and an owner. Matching by number is easy. Deciding who owns the thread when the original rep is in a call block is the part teams skip.
  5. A person or a workflow answers. Automation can confirm an appointment or acknowledge receipt. It cannot read intent out of a sentence it has never seen.
  6. The exchange is written to the system of record. If the CRM still says no response after a four-message conversation, your pipeline reporting is wrong and your next rep will start from zero.

Registration sits underneath all of it. Carrier rules for 10DLC traffic decide whether your messages arrive at all, and that is a separate workstream from the one described here. Our text message marketing laws breakdown covers the registration and consent clocks in detail.

Two-way texting vs one-way SMS is a staffing difference

One-way SMS is outbound delivery. Codes, alerts, shipping notices, appointment reminders that do not invite an answer. It scales with budget. Double the spend and you double the sends, and nothing else in your operation has to change.

Two frosted white glass tubes on a pale violet ground, the left one with a single glass bead leaving its mouth and nothing returning, the right one with seven beads of mixed sizes piled up and congesting its opening.

Two-way texting scales with people. Double the sends and you double the replies, and replies are handled by humans with calendars and call blocks. That is the real distinction, and it is the one vendor comparison pages tend to leave out.

There is also a regulatory asymmetry worth knowing before you choose. The FCC rule treats a reply as the normal route out of your messages. If a sender uses a texting protocol that does not allow reply texts, 47 CFR 64.1200(a)(10) requires a clear and conspicuous disclosure on each message saying two-way texting is not available because of technical limitations, plus reasonable alternative ways to revoke consent on each message. Turning off replies is not the cheap option. It buys you a per-message disclosure obligation instead of a staffing one.

Neither direction is better in the abstract. A delivery notification does not need a conversation. A follow-up to someone who just filled out a form does, because the next step depends entirely on what that person says back.

The reply capacity math behind two-way texting

Here is the arithmetic that should happen before the first campaign goes out. Run it with your own numbers, not with a benchmark from a vendor blog. If you do not have a reply rate from a previous send, you do not have a send plan yet, you have a hope.

Take a batch of 500 messages and a 10 percent reply rate. That is 50 inbound conversations. Text replies are fast, so most of them arrive in the first hour, not spread politely across the afternoon. Now ask what one rep can actually hold. A rep juggling live text threads while also dialing is not giving each thread an hour; they are giving it a few minutes of attention at a time, and after roughly half a dozen open threads the quality of the answers falls off a cliff.

So 50 conversations in an hour is not a two-rep job. Divide your reply volume by the number of threads a rep can genuinely hold at once, and you get your coverage requirement. Then compare that to who is actually rostered during the hour you scheduled the send. Most teams find out the hard way that the send window and the coverage window are not the same window.

Then there is the compounding part, which is the one that bites in month two. Replies do not arrive once and clear. A thread opened on Tuesday is still open on Wednesday while Wednesday’s batch is landing on top of it. If you have no rule for priority, no rule for how long a thread can sit unanswered, and no rule for what happens at the end of the day, the oldest conversations get buried under the newest ones. The buyer who replied first gets answered last.

Fix the schedule before you fix the staffing. Sending in smaller batches against known coverage hours costs nothing and flattens the spike.

Who owns the reply when it lands

Ownership is the first thing to write down and the last thing most teams define. A reply with no owner is not a conversation, it is a notification that everybody assumes somebody else saw.

Three failure modes show up over and over. Two reps answer the same customer within a minute of each other, because both got the alert and neither could see the other typing. A thread sits unassigned because its owner is in a call block and no rule moved it. And a rep leaves, taking the entire history of a live deal with them, because the conversation only ever lived on their device.

All three are solved by the same design, not by three features. Put the inbound thread somewhere shared, give it an explicit owner, and make reassignment a rule rather than a favor. Kixie’s shared SMS inbox is built around that specific problem: multiple agents manage and respond to incoming texts from one inbox, and automatic thread locking stops two people from replying to the same customer at once. Calls, texts, outcomes and recordings log to the CRM automatically, so the thread survives the rep.

Then write the boring rules down. Who covers the inbox between 5 p.m. and the next morning. What happens to a thread its owner has not touched in two hours. What a rep does when a message needs somebody more senior. None of that is software. All of it determines whether the software helps.

The opt-out rule that lives inside your reply queue

This is where the inbound half stops being an operations preference and becomes a rule you have to meet. The relevant text is 47 CFR 64.1200(a)(10), and it is worth reading closely because most teams only know half of it.

The half everyone knows: a reply containing stop, quit, end, revoke, opt out, cancel or unsubscribe is a per se reasonable means of revoking consent. Those seven words are the easy case, and any decent platform matches them automatically.

The half that matters to a reply queue: if a reply uses words other than those seven, the rule still requires the sender to treat that reply as a valid revocation request when a reasonable person would understand those words to convey a request to revoke consent. Read that as an operating instruction. “No thanks, please don’t message me again” contains none of the seven keywords. A filter passes it straight through to the next campaign. A person reading the queue catches it in two seconds.

Two more clauses change how you build the workflow. Revocation requests made by any reasonable means must be honored within a reasonable time not to exceed ten business days from receipt. And senders may not designate an exclusive means of requesting revocation, so “reply STOP only” is not a policy you can enforce against a customer who typed something else.

So the compliance requirement and the staffing requirement are the same requirement. You cannot honor a plain-English opt-out that nobody read. Note too that this section is under active amendment, with a revision published in the Federal Register on October 26, 2026 and effective November 25, 2026, so check the current text before you write policy from it. This is operating guidance rather than legal advice, and the specifics of your consent language belong with qualified counsel.

What a reply costs you to send

Carriers bill per segment, not per conversation, and the segment boundary is set by an alphabet rather than by your word count. It catches teams by surprise in exactly one place, which is the free-text replies reps write by hand.

The 3GPP short message specifications set the numbers. A single message packed in the GSM 7-bit default alphabet fits 160 characters into 140 octets. Switch to the 16-bit character set and the same 140 octets hold 70 characters. Once a message runs long enough to be split and reassembled, each piece carries a header, so the allowance per segment drops to 153 characters in the 7-bit alphabet and 67 in the 16-bit one.

Here is the operational consequence. A curly apostrophe pasted from a document, a dash copied from a web page, or a single emoji at the end of a friendly reply forces the whole message into the 16-bit set. A 150-character answer that was one segment becomes three. Nothing warns the rep. The bill arrives a month later. Our breakdown of SMS bot costs and consent walks through the full segment budget if you are automating part of the queue.

Two fixes, both cheap. Write templates in plain ASCII and check what your editor is inserting. Then put the segment count on the composer screen where the rep can see it before they send.

Two-way texting use cases that survive the reply volume

Pick use cases by the shape of the reply they generate, not by how good they sound in a deck. A workflow that produces short, predictable answers is cheap to run. A workflow that invites open-ended questions needs a staffed queue behind it.

Following up on an inbound lead

Someone filled out a form and is sitting at their desk right now. A text gets read in a way a voicemail does not, and the reply tells you whether to call. This is the highest-value use of the channel and also the most time-sensitive, which is why the measure that matters is elapsed minutes rather than messages sent. Our work on lead response time covers the handoff logic behind it.

Qualifying before you spend a call on it

One concise question can sort a list faster than a day of dialing. Keep it to one question with a short answer, and use the reply to earn the call rather than to run the whole discovery by text. Complex qualification over SMS is slower than a five-minute phone conversation and it reads as an interrogation.

Confirming and rescheduling meetings

The cheapest workflow on this list. Replies are short, the intent is usually one of three options, and most of it automates cleanly. Build the reschedule path before you launch, because “can we do Thursday instead” is the reply you will get most and it needs a human or a calendar link, not an acknowledgement.

Setting the next step after a call

A text sent straight after a conversation keeps the next step in writing where both sides can find it. It also creates a thread the buyer will use later, so count it in your coverage planning rather than treating it as a one-off send.

Answering routine service questions

Order status, hours, simple how-to questions. Fine over text. Account changes, anything involving confidential detail, and anything a frustrated customer wants resolved properly should move to a call. Make the handoff easy rather than making the customer repeat themselves.

What to check in two-way texting software

Do not evaluate this category on feature lists. Evaluate it on what the rep stops doing by hand, where the outcome gets written, what happens when nobody answers, and what a manager can inspect afterward. That narrows the demo to about eight questions.

  • Where does an inbound reply land, and who owns it? Ask them to show the assignment rule, not the inbox screenshot.
  • What stops two reps answering at once? Thread locking or equivalent, demonstrated live with two logged-in users.
  • Can a human review every reply before suppression runs? Keyword matching alone will not catch a plain-English opt-out, and the rule does not let you require keywords.
  • What happens to a thread after hours and over a weekend? Coverage rules, escalation, and what the customer sees.
  • Does the conversation write to the CRM automatically? If a rep has to copy it over, it will not be there.
  • Can another rep pick up the thread cleanly? Test the reassignment path, including history and consent state.
  • Is the segment count visible before sending? Cost control belongs on the composer, not on the invoice.
  • What number types and destinations are supported today? Carrier and country support changes, so confirm current specifics with the provider rather than from a blog.

On the Kixie side, Team SMS, SMS templates and click-to-text are included on all three plans, and business texting runs alongside the dialer in the same workspace, which matters mostly because the reply and the call belong to the same conversation.

Four numbers that say the reply queue is healthy

Delivery rate and reply rate tell you the send worked. They say nothing about whether the conversations went anywhere. Track four numbers instead, and make sure each one has an owner who can change it.

  1. Median minutes to a first human reply. Not an automated acknowledgement, a real answer. If this lives in hours, inspect routing and coverage before you inspect rep effort.
  2. The 90th percentile behind that median. The median hides the conversations that waited all afternoon, and those are the ones the buyer remembers.
  3. Unassigned threads older than your coverage window. One number, checked daily. If it climbs, your send volume has outrun your staffing and the schedule is the lever.
  4. Opt-outs per thousand messages sent. Rising opt-outs usually mean frequency, not copy. Check how many departments are texting the same list before anyone rewrites the template.

Read them together. A high reply rate is not a win if half the replies are people asking to be left alone, and a booked meeting that came after a call, an email and a text does not belong to the text.

So start narrow. One workflow, one owner, a batch small enough that your current staffing can answer every reply inside the hour. Watch the four numbers for two weeks. Then change one thing, and only one, before you scale the send.

Two-way texting FAQs

Can customers reply to business text messages

Yes, when the number and messaging setup accept inbound traffic. Support depends on the number type, the provider configuration, carrier requirements and the destination country, so confirm the specifics with your provider for the countries you message.

How many replies should one rep handle at once

Whatever your own floor measurement says, because there is no published number that fits every team. Count the open threads a rep holds during a normal shift, look at where answer quality or response time starts slipping, and use that as your ceiling. Then divide expected reply volume by it to get coverage.

Can two-way texting be automated

Parts of it. Acknowledgements, appointment confirmations and routing automate well because the replies are predictable. Open-ended replies and anything that looks like an opt-out need a person, since the revocation rule turns on whether a reasonable person would read the words as a request to stop.

Does two-way texting replace calls or email

No. It sits between them. Texting is best at short exchanges and scheduling, calling is still better for negotiation and objection handling, and email carries documents and long explanations. The useful question is which channel moves this deal forward today.

What is the difference between two-way SMS and a shared inbox

Two-way SMS is the channel, a shared inbox is how a team runs it. You can have two-way messaging without a shared inbox, which is how replies end up on one rep’s phone, and that is the arrangement that breaks first.

Sources

Sources verified and content reviewed by the Kixie Research Team on November 13, 2026.

Ready to close more deals with Kixie?

See how Kixie's AI-powered tools can transform your sales and support operations.

Start Free Trial

Kixie Research Team is the organizational byline for content created and maintained by Kixie’s staff writers and editors through a shared research and editorial process. The team covers sales technology, outbound calling workflows, CRM integrations, and revenue operations. This shared byline reflects organizational accountability; it does not mean every article reflects hands-on testing. Individual pages identify their sources, methods, and limitations.

How we research, source, and update this article

How Kixie researches, sources, and updates articles like this one is described in our editorial standards.

If you spot an error or an outdated detail, request a correction.

Third-party sources linked in this article

This list is generated automatically from the third-party links referenced in the article above.