When to move from text to a call

Most teams choose a channel by habit. The setters text because texting scales, the closers call because calling is what they know, and the customer gets whichever one the last person preferred. That is how a thread ends up with four messages trying to explain a price, and how a customer who just wanted a document gets three voicemails. The channel should follow the decision in front of the customer, and the switch between channels should be announced rather than sprung.

The rule: the channel follows the decision

Text is excellent at delivering a fact, confirming a detail and reaching someone who cannot talk. It is poor at anything with branches. The moment an answer depends on information you do not have, or has three versions depending on what the customer says next, you are writing paragraphs into a medium built for one line, and the customer stops reading halfway down.

The phone is the opposite. It handles branches in seconds, it lets you hear hesitation, and it is the only channel where you can answer the objection the customer did not type. It is also easy to ignore, which is why the way you ask for the call matters as much as the decision to make it.

Four moments that belong on the phone

The number depends on facts you do not have

“What would I pay a month?” is not a text question when the honest answer depends on coverage limits, a deductible, a start date or an approval you do not have yet. Sending one number turns a guess into a promise someone will have to live with. Sending a paragraph about why you cannot send a number reads as a dodge. Say in one line that the real figure takes a few minutes to build properly, and ask for those minutes.

There are more than two choices

Two options can be compared in a thread. Four cannot. Once the customer is weighing coverage levels, start dates, add-ons and price at the same time, a phone call does in three minutes what twenty messages will not finish, and it lets you hear which of the four actually matters to them.

Something went wrong

The option they wanted is no longer available, the meeting was missed, the quote came back higher than expected, the approval was not what they hoped. Bad news by text reads colder than it is, and it invites a short reply that ends the relationship. Call, say the thing plainly in the first sentence, and bring an alternative with you.

The customer is ready to pick a time

You can set a meeting by text, and plenty of good ones are set that way. But a customer who is deciding between Thursday and never is easier to read on the phone, because the pause before the yes tells you what the words do not. If the thread has real interest in it, call to set the time, then confirm it in writing.

How to ask for the call so it gets answered

An unannounced call from an unknown number is the easiest thing in a customer's day to ignore. Ask first, in the thread, with three elements: the reason, the length and two windows.

Synthetic example: “Hi Dana, this is Marcus at the agency. The premium depends on the deductible and the coverage limits you pick, so let me walk you through the two or three ways it can be set up. It takes about five minutes. Are you better around 11:00 or after 4:00? I will call from this number.”

That message does the work of three. It explains why the call exists, so the customer is not wondering what they are being sold. It caps the time, which removes the fear of a twenty-minute pitch. It gives two windows rather than asking “when is good?”, which is a scheduling problem in disguise. And it names the number, so the phone that rings is already familiar.

Four moments that belong in the thread

• Delivering what you promised. The quote, the document, the comparison, the meeting link. Send it, then say what it means in one line.
• Logistics before a meeting. The time, who they will talk to, how to join, what to have ready. Nobody wants to take a call for this, and they will want to reread it before the meeting.
• Reaching a customer who cannot talk. Plenty of customers are on a job site or a shop floor all day. For them the thread is the only live channel you have.
• Recovering a missed time. Call first, and if there is no answer, text right away with one specific alternative and no guilt in it.

Texting a customer is governed by rules separate from anything to do with call recording. The FCC's rules at 47 CFR 64.1200 cover text messages as well as calls: sending one with an automatic telephone dialing system to a mobile number takes the customer's prior express consent, and a marketing text sent that way takes prior express written consent. A customer may revoke consent by any reasonable means, including replying “stop,” and the rules give the sender no more than ten business days to honor it. Teams commonly ask permission on the call, note it in the customer record, identify the company in the first message and honor stop requests right away across every list. Have your own counsel review your texting program. This is general information, not legal advice.

When they will not take the call

Some customers will never pick up, and that is information rather than rejection. After two asks and no call, stop asking and start working the thread properly. Break the complicated answer into its smallest honest pieces and send them one at a time, each ending in a question that takes four words to answer. Give the range and what moves it rather than a single figure you cannot support. If the customer keeps reading and never replies, change what you are offering rather than how often you send it.

One thing is worth saying out loud in that situation: “I can keep doing this by text. It will just take longer, and you will get a range instead of a real number.” Many people who hear that pick up the phone.

The handoff problem: two channels, two people

The expensive version of this is not a channel problem at all. It is a customer who texts a setter, gets called by a closer who has not read the thread, and repeats everything they already typed. The customer concludes that nobody at your company talks to anybody else, and they are right.

Three rules fix most of it. First, whoever makes the call reads the whole thread, including the parts written before they were involved. Second, the call opens by referring to the thread, so the customer hears that their words were read. Third, the person who takes over says so by name in the thread, so the customer knows who owns the conversation now.

Close the loop in writing, every time

After every call, write the outcome back into the thread. Two lines is enough: what you agreed, and what happens next with a date on it. This is the habit that makes a mixed-channel conversation readable by the next person, and it protects the customer from having to explain themselves twice.

It also creates the only reliable record of what was promised. A conversation that lives half on the phone and half in a thread, with nothing connecting them, is one you cannot manage, coach or defend.

What to do this week

1. Read ten threads that went quiet and mark the message where a phone call should have replaced the typing.
2. Write your team's bridge message, with a reason, a length and two windows, and put it where the team can copy it.
3. Check whether anyone quoted a firm price in a thread last week before they had the details it depends on, and replace that pattern with the call ask.
4. Make reading the thread a rule before any call to a customer who has already texted your team.
5. Spot check twenty threads for a two-line summary after each call, and add it where it is missing.