TL;DR: Calls, texts and CRM records describe the same conversation, but they fail separately, and the follow-up dies in the gap between them. Fix it with one rule: every interaction ends with a recorded outcome, a named owner and a dated next step, written to the CRM by the phone system rather than by a rep at the end of the day. The consent state travels with the record, and the rules are specific. Under 47 CFR 64.1200(a)(10) a contact can revoke consent by any reasonable method, the words stop, quit, end, revoke, opt out, cancel and unsubscribe sent as a reply text are per se reasonable, other wording still counts if a reasonable person would read it as a revocation, you may not designate an exclusive way to opt out, and the request must be honored within a reasonable time not to exceed ten business days. A revocation left as a voicemail or email creates a rebuttable presumption under (a)(11), so a channel your texting tool never reads can still stop your campaign. One confirmation text is allowed under (a)(12) if it carries no marketing and is the only further message, and sending it within five minutes keeps it presumptively inside prior express consent. Prerecorded follow-ups carry their own rules under (b): the registered business name at the start, a working callback number during or after, and for telemarketing an automated opt-out mechanism within two seconds of that identification. Kixie writes these steps into the system of record, with two-way CRM integration, call disposition logging that can require an outcome before a rep moves on, and automated post-call text messages triggered by the disposition itself.
Why Business Call and SMS Follow-Ups Get Missed
Most teams do not miss follow-ups because reps forgot. They miss them because the interaction landed on a channel the record never heard about, nobody was named as the owner, and no dated next step was ever written down. Whose turn was it? If the system cannot answer that, nobody’s.
Walk the sequence. A prospect calls back at 4:40 and gets voicemail, a rep texts them at 9:10 the next morning from a shared number, and the prospect replies “can you call me Thursday” to that number. Nobody opens the shared inbox until Friday. The CRM record still shows the original outbound call from Tuesday as the last activity, so every report you run says this deal went quiet. It did not go quiet. It answered on a channel the record never heard.
That is the whole problem in one paragraph. Calls, texts and CRM entries are three separate state machines describing one relationship. Each one can advance without telling the others. So the question is not which channel to use. Which system owns the next step, and does every channel write into it? Answer that and most of this gets easy.
There is a second failure underneath the first. A deal marked no-response is meaningless without the attempt history behind it. Two calls and one text on consecutive mornings is not persistence. Closing that record out is a guess dressed as a decision. So before you buy anything, pull ten closed-lost records. Count the actual attempts, the channels and the gaps. A lot of times this is not a follow-up problem at all. It is a disposition problem, and the dispositions were never required.
The Business Call to CRM Follow-Up Workflow
Here is the spine. Seven steps, in order, and each one has to leave evidence in the CRM before the next one is allowed to run. If a step depends on a rep remembering, it is not a step. It is a hope.
Capture Each Call and SMS Interaction
Every inbound call, outbound call, voicemail and text belongs on the contact record with a timestamp, a direction and a number attached to it. Not a summary at end of day. The capture has to be automatic, because manual logging is the first thing that stops happening during a busy call block. Kixie’s two-way CRM integration writes the activity as it happens rather than asking the rep to retype it. That is the difference between a record you can route on and a record you can only read.
Watch for the quiet gap. Texts sent from a personal cell, or calls placed from a mobile app that logs to a different object than your desk softphone, are the interactions that vanish without anyone noticing they were supposed to exist. Pick one calling and texting path per rep and inspect it. Otherwise your activity data is a sample, not a record.
Match the CRM Contact or Create One
An inbound number either matches an existing contact or it does not, and both outcomes need a rule written in advance. A match opens the record before the rep says hello, so the conversation starts with context instead of a name spelled out twice. A non-match creates a record. Not a floating call log attached to nothing.
The failure mode here is duplicates. A prospect calls from a mobile that is not on the record, your system creates a second contact, and now the follow-up history is split across two records that neither rep can see in full. Decide in advance whether a new number attaches to an existing person or opens a new one. Then decide who merges them, because an unowned merge queue is just a slower version of the same problem.
Record the Call or SMS Outcome
This is the step that carries the rest of the workflow, and it is the one teams skip. So what counts as an outcome? Not notes. It is a value from a short controlled list that software can act on: connected, no answer, voicemail left, wrong number, not interested, callback scheduled.
Notes are for humans. Dispositions are for automation. If the follow-up is going to fire on its own, it has to read a field with predictable values, and free text will never be that field no matter how well the rep writes. Kixie’s call disposition logging auto-logs the outcome to the CRM, and it can require an outcome before the rep moves to the next call. That turns a good intention into a gate. For which fields actually survive a real call block, see how to get sales reps to log calls your CRM can actually use.
Assign a Follow-Up Owner
Every open interaction needs exactly one name on it. Not a team. Not a queue. Not a shared inbox that four people assume someone else is watching. One name.
Shared numbers are where this breaks hardest. An SMS reply lands in a pooled inbox, three reps see it, and the social math quietly tells each of them that one of the other two is already handling it. Assign the reply to the owner of the contact record on arrival. No owner? Then the routing rule picks one. Unassigned is a defect, not a category.
Schedule the Next Follow-Up
The next step gets a date the moment the outcome is recorded, and the outcome sets it rather than a rep’s judgment call at 5pm on a Friday. No answer on a warm inbound lead is not the same wait as no answer on a cold record, so the rule should differ by lead temperature. A dated task with no owner is not scheduled. An owner with no date is not scheduled either.
This is where automated texting earns its place. Kixie’s automated post-call text messages send based on the call outcome, with templates and timed follow-ups, so a voicemail disposition produces the text immediately rather than three hours later when the rep finally clears their queue. Kixie’s outbound cadences handle the structured multi-touch version of the same idea.
Escalate Overdue Follow-Ups
Overdue has to be a defined number, visible to a manager, attached to a consequence. Without that, the oldest records sink, because new leads arrive every day, they are more interesting than a four-day-old callback, and the queue quietly reorders itself by recency instead of by value. What is your threshold? If nobody can say it out loud, there isn’t one.
So pick the threshold, show the list, and route the overdue item somewhere. Reassigning it counts as a decision when the current owner’s queue is the actual blocker. So does deliberate disqualification. Letting it age is the only option that is not a decision.
Close or Nurture the Record
Closing is a judgment, and it should have to clear a bar: a defined number of attempts, across more than one channel, all of them visible on the record. So what has a rep who called twice and texted once actually established? Not no-response. They have established that three things happened.
Nurture is the other door. It needs its own consent posture, which is where the next section comes in. Moving a record to nurture refreshes nothing about what that contact agreed to receive.
Call and SMS Follow-Up Workflows by Scenario
The seven steps above are the general case. These five are where teams actually lose deals. Each one needs its own rule, written down.
Missed Business Calls
A missed call is an inbound intent signal, which makes it the highest-priority item in the queue for the next few minutes. Treat it like a form fill, because that is what the buyer just did with their thumb. The automatic response is a text acknowledging the call and offering a time. The human response is a callback from the owner. Do both. The text buys the window. The call does the work.
Inbound Sales Calls That Connect
A connected inbound call is the easiest follow-up to get right, and it is also the one most often left undocumented, because the conversation went well, the rep felt good about it, and the next dial was already ringing. Disposition it. Set the next step before leaving the record. Send the recap text while the call is still in memory. A connected inbound call with no next step is a leak, and it is a measurable one.
SMS Replies
Text replies need a response time measured in minutes, because unlike an email the buyer is holding the device in their hand right now. They also need classification, because a reply is one of three things: a question, a scheduling request, or an opt-out. The third is not an inconvenience. It is a legal event, and it is covered below in detail.
One operational note that costs teams money. A reply like “sounds good, Thursday works” and a reply like “please take me off this list” arrive in the same inbox, sit in the same list, and look identical to an unread-count badge. Route them differently, or a rep will eventually answer the second one with a pitch.
No-Response Follow-Ups
Cold records that never answer need a deliberate pattern with a defined end. Not an indefinite drip. Decide the attempts, the channels, the spacing and the stop condition in advance, then write the stop condition down where the person building the sequence will actually read it. A sequence with no exit is how a prospect ends up on touch fourteen, and that generates an opt-out and a complaint rather than a meeting.
Support Handoffs
When a sales contact raises a support issue, follow-up ownership moves, and the CRM has to record that it moved. Here is the common failure. The rep answers the support question personally, nothing is logged in the support system, and the next person to touch the account walks in with no idea the problem exists. Hand off explicitly. Record who owns the next step on both sides.
Consent Rules That Decide When a Follow-Up Can Fire
This is the part most follow-up advice skips. It is also the part that decides whether your automation is allowed to run at all. These are federal rules in 47 CFR 64.1200. They are written in terms your CRM has to model: who consented, to what number, on what channel, and whether they have since said stop.
Consent Attaches to a Number, Not a Person
Start with what consent legally is. 47 CFR 64.1200(f)(9) defines prior express written consent as a signed written agreement that clearly authorizes the seller to deliver advertisements or telemarketing messages using an automatic telephone dialing system or an artificial or prerecorded voice. And it has to identify the telephone number the signatory authorizes those messages to go to. Read that last part again. Consent names a number.
So a prospect hands a rep a second mobile on a call. Is that number covered by the form they filled in last month? No. The agreement also has to carry a clear and conspicuous disclosure which, per (f)(9)(i)(A) and (B), tells the signer that they are authorizing those calls and that they are not required to sign as a condition of buying anything. Electronic and digital signatures count under (f)(9)(ii), to the extent they are valid under applicable federal or state contract law.
The CRM implication is concrete. Store consent on the phone number, with the date and the source, rather than as a single checkbox sitting on the contact. One contact, three numbers, three different consent states is a normal situation, and a data model that cannot express it will eventually text the wrong line. Can yours express it today?
Revocation Can Arrive Any Way the Contact Wants
47 CFR 64.1200(a)(10) is the rule that breaks naive opt-out handling. A called party may revoke consent by any reasonable method. Three things count as reasonable per se: an automated opt-out mechanism on a call, a reply text using stop, quit, end, revoke, opt out, cancel or unsubscribe, or a website or phone number the caller designated for opt-outs. What if they use different words? The rule still binds you. The caller must treat that reply as a valid revocation if a reasonable person would understand the words to convey one.
So a keyword filter is a floor, not a compliance program. “Take me off your list” and “stop texting me please” contain none of the seven magic words, and both are revocations that your automation is obliged to act on. Somebody or something has to actually read the replies.
Two more specifics from the same paragraph. Requests made in any reasonable manner must be honored within a reasonable time not to exceed ten business days from receipt, and callers may not designate an exclusive means to request revocation. So “reply STOP” cannot be the only door you leave open. How many doors does your workflow have?
Then there is the cross-channel trap. Under (a)(11), other methods count too. A voicemail or email to a number or address intended to reach the caller creates a rebuttable presumption that the consumer revoked consent, once the called party produces evidence the request was made. So a revocation can land in a voicemail box your texting platform never reads. Does your consent state live only inside the SMS tool? Then you have a gap.
The Confirmation Text Has a Five-Minute Clock
You are allowed to confirm. 47 CFR 64.1200(a)(12) says a one-time confirmation text does not violate (a)(1) and (a)(2), provided it merely confirms the revocation, carries no marketing or promotional content, and is the only additional message sent after the request. Send it within five minutes of receipt and it is presumed to fall within the consumer’s prior express consent. Take longer and the sender has to show the delay was reasonable. Five minutes is an engineering requirement, not a nicety.
There is a useful allowance for teams running several message types. If the recipient consented to several categories, the confirmation may ask which ones the revocation was meant to cover, but the sender must stop all texts requiring consent unless the recipient clarifies that they want some of them to continue. Silence means stop.
Prerecorded and Voicemail Follow-Ups Have Their Own Script
Dropping a prerecorded voicemail is a follow-up step, and 64.1200(b) governs what that recording has to contain. At the beginning of the message, state clearly the identity of the business responsible for initiating the call, using the name it is registered under with the State Corporation Commission or comparable authority. During or after the message, state clearly a telephone number for that business. It may not be the number of the autodialer or message player that placed the call. It also may not be a 900 number, or any other number charged above normal transmission rates.
There is more for telemarketing. For telemarketing messages and the exempted categories in (a)(3)(ii) through (v) delivered to residential subscribers, that number must let anyone make a do-not-call request during regular business hours. And under (b)(3) the message must provide an automated, interactive voice or key press opt-out mechanism, with brief instructions. It has to appear within two seconds of the identification required by (b)(1).
Two seconds is a production constraint, not a legal footnote. Because the compliance language has to sit inside the recording itself, a team that records Voicemail Drop messages per campaign needs every template to carry the identification and the opt-out from the first take. And somebody checks that it still does after the next rewrite.
What to Look for in Call, SMS, and CRM Follow-Up Tools
Do not evaluate this category on feature lists. Evaluate it on two things: what the rep stops doing manually, and what the manager can inspect afterward. Everything else is packaging.
Ask these, in this order. Does the call or text write to the CRM without a rep action, and to which object and fields? Can the system require a disposition before the rep advances? Does the disposition value trigger the next step, or does it only report? When a text arrives, who does the system assign it to, and what happens if that contact has no owner? Where does consent live, is it stored on the number rather than the person, and does an opt-out on one channel stop the others? Can a manager pull every record with a connected call and no next step, in one view?
A vendor that answers the first five and fails the last one is selling a logging tool, not a follow-up system. The difference shows up a quarter later, when nobody can explain where the pipeline went. And which CRM to standardize on? That is really a telephony question, worked through in best CRM for sales call logging.
CRM Metrics for Business Call and SMS Follow-Ups
Pick metrics that name a controllable input. Revenue tells you the quarter was bad. It does not tell you which step to fix Monday morning.
Track time from inbound interaction to first outbound attempt, by channel. Look at the median and the tail, not the average. Track the share of connected calls that end with a recorded disposition. Then the share of those dispositions carrying a dated next step. Track open interactions with no owner. That should be close to zero and almost never is. Track overdue follow-ups by age bucket and by rep. Track attempts per closed-lost record, across channels, because that one number tells you whether your no-response category is real.
Each of those turns a lagging result into something a manager can act on this week, which is the only test a follow-up metric has to pass. Does the number change routing, staffing, priority or coaching? If not, drop it from the dashboard.
A CRM Checklist for Managing Business Call Follow-Ups
Run this against your own system before you change tools, because most of what follows is configuration you already own rather than something you have to buy. Work it as a list, not a philosophy.
Every call and text writes to the CRM automatically, from every device a rep actually uses. Dispositions are a short controlled list, and recording one is required rather than encouraged. Each disposition maps to a defined next step carrying both an owner and a date. Inbound numbers resolve to a contact or create one, under a duplicate rule somebody wrote down. SMS replies route to the contact owner on arrival and get classified before anyone answers them. Consent is stored per phone number with a date and a source. An opt-out on any channel, in any wording, stops every consent-dependent message to that number, and the clock you actually work to sits well inside ten business days. Prerecorded templates carry the business identification, the callback number and the opt-out mechanism. Overdue thresholds are defined, visible and escalated to a named person. Closed-lost requires a minimum attempt history across more than one channel.
Work the list top to bottom. The first item that fails is usually the one producing the symptom you noticed.
Business Call, SMS, and CRM Follow-Up FAQs
Can calls and texts be logged automatically in a CRM?
Yes, when the phone system is integrated with the CRM rather than sitting beside it. Kixie’s two-way CRM integration logs call and text activity to the contact record as it happens, and the disposition can be written at the same time. Here is the practical test: can a rep finish a call, touch nothing in the CRM, and still leave a complete record behind? If not, the integration is partial.
How quickly should a business follow up?
Fast enough that the buyer is still in the same frame of mind, which for an inbound call or a text reply means minutes rather than hours. Rather than adopting a borrowed benchmark, measure your own elapsed time from interaction to first attempt, then fix the slowest step in that chain, which is usually assignment rather than rep effort. The mechanics are covered in lead response time best practices.
How should missed calls be handled?
As inbound intent. Send an automatic acknowledgment text, assign the callback to the contact owner immediately, and put it at the front of the queue rather than at the end of a list somebody works through in order. A missed call that waits until tomorrow is a lead you paid for and did not work.
What should be recorded after each interaction?
Four things: the outcome as a controlled value, the owner of the next step, the date of the next step, and any change to consent state. Notes are useful, but they are not any of those four, because no routing rule, escalation timer or suppression list can read a paragraph.
Does an opt-out by text stop phone calls too?
Under 47 CFR 64.1200(a)(10) a revocation covers further calls and text messages made under the paragraphs it references, so treating it as an SMS-only event is the wrong default. Build the consent state so that a stop arriving on one channel suppresses the others to that same number, and keep a written record of when the request arrived and when you acted on it.
Sources
- Code of Federal Regulations, 47 CFR 64.1200, Delivery restrictions, covering the definition of prior express written consent at (f)(9), revocation of consent by any reasonable method and the ten business day deadline at (a)(10), the rebuttable presumption for other revocation methods at (a)(11), the one-time confirmation text and five minute presumption at (a)(12), and the identification, callback number and two second opt-out requirements for artificial or prerecorded voice messages at (b)(1) through (b)(3). Reviewed October 22, 2026.
- Electronic Code of Federal Regulations, 47 CFR 64.1200, current consolidated text, used to confirm the currently effective wording of the revocation, confirmation and prerecorded message paragraphs. Reviewed October 22, 2026.
- Kixie, two-way CRM integration, describing automatic CRM logging of call and text activity. Reviewed October 22, 2026.
- Kixie, call disposition logging, describing auto-logged CRM dispositions and the require outcome feature. Reviewed October 22, 2026.
- Kixie, automated post-call text messages, describing automated texts sent on call outcomes with templates and timed follow-ups. Reviewed October 22, 2026.
Sources verified by the Kixie Research Team on October 22, 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