Skip across the chapter
Quota Playbook

Text follow-up review: 3 checks before coaching

Quota Playbook Editorial Team · Published · 12 min read

Before a rep's follow-up review, check message length, reply ratio, and delivery errors and content, then choose one coaching change.

Key takeaways

  • Check message length, including whether saved messages push past one piece.
  • Compare incoming and outgoing messages to spot reply patterns.
  • Read delivery error reasons and flag content that needs a compliance look.

Why check the texts before the talk

A coaching conversation goes better when you and the rep are looking at the same thing. If you walk in saying a rep "isn't following up enough," the rep can argue with the feeling. If you walk in with a thread, a few numbers, and one error message, the conversation is about the work.

Text follow-ups are a good place to start. They are short, time-stamped, and sit in a record you can read without asking anyone. You can scan a rep's outgoing messages in a few minutes and spot patterns that are hard to notice while the work is happening. But a text log also hides things. A message that reads fine on your screen may be handled differently when it is sent. A thread with no replies may point to a weak message, or to a sending problem the rep never saw.

Each check is quick, and each one tells you what to look at in the next. Run them in order.

One note before you start. These checks are a screen. They help you decide what to ask, and they do not replace your company's compliance process. They are not legal advice. When a question is about whether a message is allowed, bring in the person who owns compliance on your team.

Set up the review before you open a thread

Start by deciding what period you are reviewing. Use the same window for every rep on your team so the comparison is fair. A rep who had a slow stretch and a rep who had a busy one should not be compared across different dates without saying so in the notes.

Next, pull two things for each rep: the outgoing messages they sent, and the incoming replies from the same leads. If your tool shows which saved message or workflow produced a message, include that.

Keep a simple working note. For each message, record the lead, the date, the text, the source (typed by hand or pulled from saved text), and whether it got a reply or an error. Do not try to grade in your head while you scroll. A written note keeps you from remembering only the messages that stood out, which is a common way reviews get skewed.

Finally, decide what you want to leave with. Most reviews go wrong because the manager tries to fix five things at once. Before you start, write down the one change you most want to see. Everything else you find goes on a second list for later.

Check 1: Message length

The first check is the simplest, and it is often where a problem hides. Close's help center explains that messages longer than 160 characters are automatically split into parts, called segments, and then reassembled when they are received. The same page advises that you ensure your messages, especially saved messages used in workflows, stay below the 160-character limit. Source: Close Help Center, "A2P 10DLC - Stay Compliant".

For a front-line manager, the practical step is to count. You do not need special software for this. Paste saved text into a character counter, or count a sample of messages by hand. Focus first on saved messages and scripts, because they go out again and again. Check hand-typed messages as well as saved text. A message copied from a playbook, or one where a long company name or address fills in through a merge field, can run past the limit for every lead it reaches.

Be careful about what the check tells you. A message over 160 characters is not automatically a bad message. The question for your review is whether the length was a choice the rep made, or something that came with saved text the rep did not write. Those are different conversations, and mixing them up leads to unfair feedback.

When you find a long message, ask about it before you judge it. A good opening is: "Did you write this one, or did it come from the saved text?" If the rep wrote it, ask what the message was trying to do and whether a shorter version would do the same job. If it came from saved text, the fix belongs to whoever maintains that text. Note it and pass it along.

Keep the length check in proportion. A rep who writes shorter messages is not automatically doing better work, and a short message that says nothing useful is still a weak follow-up. Use length to find out what happened. Do not use it as a score. For related sending checks, see text-message caps before a seller texts a buyer.

Check 2: Reply ratio

The second check looks at replies. Close's help center says that when the ratio of incoming to outgoing SMS on a Long Number is more than 1:3, it signals to carriers that recipients aren't engaged, and that they may not have opted into the messages. The page spells out the direction of that ratio in its own terms, so read the source before you quote the exact wording in a review.

Why should a manager care? Because a reply ratio is a signal that goes beyond one rep's performance. It describes how recipients respond to messages sent from a number. If your team shares a number, one rep's pattern can affect what the others send from it. If each rep has a separate number, the ratio is closer to one person's work. Know which setup you have before you read anything into the figure.

To run this check, count outgoing and incoming messages for each rep over your review window. Do it by number and by list if your tool allows. Then look for the pattern. Does one list get far fewer replies than the others? Does one saved message get answers while another goes quiet? Did a rep's replies drop after they changed how they open a message?

Do not turn a low ratio into a verdict. Some audiences reply rarely, and some follow-ups are meant to be read rather than answered. A low ratio should lead you to a question, not a conclusion. Try something like: "Your replies look lower on the second list. Who was on that list, and what did you send first?"

Once you find a real pattern, separate the parts you can coach from the parts you cannot. A rep can change an opening line or the timing of a follow-up. A rep cannot change who is on a list that was handed to them. If the pattern comes from the list or the number, raise it with whoever owns those assets.

Check 3: Delivery errors and content

The third check looks at whether messages arrived, and whether anything in them needs a closer look. Start with the errors.

Close's help center explains that filtered messages fail with Error 30007, "Message Delivery - Carrier Violation," which means the destination carrier is filtering out the messages. The page also says that if you hover over the error message, you can see the reason it was undelivered. So an error is more than a red mark. It carries a reason, and the reason is what you need.

In your thread review, filter for failed or undelivered messages and read each reason. Sort them into two groups. The first group is errors that point to the rep's own sending, such as a message that failed because of how it was set up or sent. The second group is carrier filtering, such as 30007. A rep who sees many carrier filtering errors may be sending content the carrier is filtering out. That is a different conversation from writing skill. Investigate delivery problems; changing message content may help when that content causes filtering.

Carrier filtering can also be a team issue. Take that to the person who manages the sending setup, and keep it out of the one-on-one.

Next is content. Close's page addresses illegal content, which it defines as content that must be illegal in all 50 states and federally. It also points readers to T-Mobile's Code of Conduct, Section 5.2, for a list of all disallowed contact. You do not need to memorize these lists. You need to know when to escalate.

Use a quick screen on each flagged message. Does it make a claim the rep cannot back up? Does it use pressure, threats, or language that could be read as misleading? Does it touch a topic your company's policy has already marked as sensitive? If the answer is yes, or you are not sure, do not settle it in the review. Note the lead and the date, and send the message to whoever owns compliance on your team. Do not make a legal call on your own, and do not ask the rep to defend a message you have not checked.

When you raise a content concern, keep the conversation on the message, not on the rep's character. "This message needs a compliance look" is a fact about the text. "You're careless" is a judgment, and it will shut the conversation down.

Illustrative example: A shared-number review

Suppose a rep sends 50 outgoing messages and receives 10 incoming replies during the review window. These are illustrative counts, not a target.

The manager notes each message's source, whether saved or hand-typed. On the length check, a long company name fills in through a merge field and pushes a saved message past the character limit. On the reply check, the list receiving that message has fewer replies than the others. This connection gives the manager a question to ask; it does not prove the message caused the difference.

On the error check, the manager reads each reason and flags any content concern for compliance. The coaching conversation starts with the saved message and who owns its revision.

Turn the checks into one coaching conversation

You have three checks and a list of findings. Do not bring all of them to the rep at once. A review with five problems often leaves all five unfixed. Pick the one with the clearest evidence and the most direct effect on the rep's work.

A simple shape works well:

  • Start with what worked. Name one message or habit worth repeating.
  • Show the evidence. Put the message or the number in front of the rep.
  • Ask one question. Let the rep explain before you add your view.
  • Agree on one change, and set a date to look at it again.

An opening might sound like this: "I went through your follow-ups for the review period. I want to look at the second list with you, because the replies there are lower than on the others. Walk me through what you sent first."

Then listen. If the rep says saved text is the cause, check it together and decide who owns the fix. If the rep says the list is hard to work, ask what they have tried and whether the list needs a different approach. The point is to find the cause, not to win the argument.

Some questions are useful in almost any review:

  • Which of these did you write yourself, and which came from saved text?
  • What were you trying to get the lead to do in this message?
  • Did anything change in how you opened your messages during this period?
  • Have you seen any messages that did not arrive? What did the error say?
  • What is one thing you would like help with before the next review?

The last question matters. A rep who names their own problem is more likely to act on the change you agree on.

Close the conversation by writing down the agreed change, the date you will look at it again, and anything you owe the rep, such as corrected saved text or a question you will take to another team. A change with no date tends to drift. Use coaching follow-up tasks to plan that follow-through.

Mistakes to avoid

Several errors come up often in these reviews, and each one is easy to avoid once you know to look for it.

  • Grading from one thread. One conversation tells you little. Use the full review window so a single unusual lead does not drive the feedback.
  • Treating a low reply count as proof of weak work. Audience, offer, and timing all affect replies.
  • Blaming the rep for saved text. Check where the message came from before you speak to the rep about it.
  • Calling a delivery error the rep's fault before you read the reason. The reason often points to something else entirely.
  • Making the content call alone. A quick "I'm not sure" is a better answer than a wrong one.
  • Sharing more than you need to. Keep recipient phone numbers and full message logs out of group chats and out of wider channels. Keep the review to the rep and to the people who need to act on it.

A short checklist

Before each review, confirm the following:

  • The review window is set, and it matches the window used for every rep.
  • Outgoing messages are pulled, with each one marked as saved or hand-typed.
  • Saved and sampled messages have character counts recorded.
  • Reply counts are compared by number and by list.
  • Failed messages are sorted, and each error reason has been read.
  • Any content you are not sure about is flagged for compliance.
  • You have one question to ask and one change to agree on.
  • The next review date is on the calendar before the conversation ends.

Closing

The goal of these three checks is not to catch a rep out. It is to replace a general feeling with a few facts you can both look at. Length shows you what the messages look like on the page. Replies show you how recipients respond. Errors and content show you what is reaching people and what needs a second look from the right owner.

Today, choose a review window and pull the outgoing messages and incoming replies for the same leads. Start your working note before opening the first thread.

What to check before the review

Should message length be a performance score?

No, use length to investigate how a message was written. Check whether the rep wrote it or used saved text before deciding who owns the change.

Does a low reply ratio prove weak follow-up?

No, a low reply ratio is a reason to investigate. Compare lists, message sources, and the sending number before choosing a coaching question.

What should you do with a delivery error?

Read the error reason before assigning responsibility. Investigate shared sending problems with the setup owner, and take content concerns to the compliance owner.

Sources

  1. Transcript word boosting: 4 checks before calls
  2. Slack history: 4 checks before a rep review
  3. Call review folders: 4 limits to check before sharing
  4. Deal amount checks before deal review
  5. Buyer AI research: 5 facts for discovery coaching

More plays