TL;DR: Deciding when to text prospects instead of calling is not a style preference, it is a permission question, and the tier is set by who sent the first message and what your message does, not by how warm the lead feels. CTIA’s Messaging Principles and Best Practices sorts business texts three ways. Conversational means the prospect texted you first and you answered, and no additional permission is expected. Informational means the prospect handed over a number and asked to be contacted, and that needs express consent for the specific purpose they agreed to. Promotional means the message carries a call to action, and that needs express written consent before the first send. CTIA also says senders should not text opt-in lists that were rented, sold, or shared, so a purchased list carries no texting consent at all. Calling runs on separate rules. 47 CFR 64.1200(c)(1) bars telephone solicitations to a residential telephone subscriber before 8 a.m. or after 9 p.m. local time at the called party’s location, and 64.1200(c)(2) requires national Do Not Call registrations to be honored indefinitely. Once someone opts out of covered texts, 64.1200(a)(10) makes “stop,” “quit,” “end,” “revoke,” “opt out,” “cancel,” and “unsubscribe” a per se reasonable revocation, requires you to honor other wording a reasonable person would read the same way, caps you at ten business days, and forbids designating an exclusive revocation channel. 64.1200(a)(12) permits exactly one confirmation text with no marketing in it, presumed inside prior express consent when it goes out within five minutes. So text what resolves without a reply, meaning confirmations, two time slots, a short update the prospect asked for. Call what needs a conversation to finish, meaning discovery, pricing, objections, and anything where the next question changes the answer. Then record the tier, the consent source, and the opt-out in one field the next rep can actually read.
Most advice on when to text prospects instead of calling reads like a tone guide. Texting is casual, calling is personal, pick the one that fits the moment. That framing skips the only gate that actually stops you.
Calling a prospect and texting the same prospect sit under different permission regimes. You can usually pick up the phone and dial a business number. You cannot always send that same number a text. Whether you can has almost nothing to do with how well the rep thinks the relationship is going, and almost everything to do with who started the exchange, what the message is trying to do, and what your company wrote down when the number first entered the CRM. So there is a question before the channel question. What permission do you actually have, where did it come from, and is it recorded anywhere a second rep could find it?
When to text prospects instead of calling, the short version
Here is the operating rule, and it survives almost every edge case a rep will throw at it. Text the messages that finish without a reply, meaning the prospect can read it, act on it or ignore it, and nothing is left hanging that your pipeline depends on. Call the messages that need a conversation to finish.
A confirmation finishes without a reply. Two proposed times finish without a reply, because the prospect either picks one or does not. A short update the prospect asked for finishes without a reply. Discovery does not. Pricing does not. An objection does not, because the useful part is the second and third question, and a text thread makes you wait a day between them.
So test the message before you pick the channel. Does this one end when it lands, or does it only start something? If it only starts something, dial.
That rule tells you which channel fits the message. It does not tell you whether you are allowed to send it. For that, you need the consent tier.
The three consent tiers that decide whether you can text a prospect
CTIA’s Messaging Principles and Best Practices is the industry document carriers and messaging providers operate against. It sorts business texts into conversational, informational, and promotional, and attaches a different consent expectation to each. So what sets the tier? Who sent the first message, and what your message does. Not lead temperature. Not deal stage. Not how friendly the last call was.
Conversational texts when the prospect messaged you first
CTIA describes conversational messaging as a back and forth where the prospect texts first and the business responds quickly with a single message, and it is clear that the permission runs on who opened the exchange rather than on what the business would like to say next. In its words, if the consumer initiates the conversation and the non-consumer simply responds, then no additional permission is expected. That is implied consent. It is also the narrowest tier you have.
Read the boundary carefully, because reps blow through it constantly. The prospect texted to ask whether your product does call recording. Answering that is conversational. Is following up four days later with a case study still conversational? No. You sent the first message in that exchange and it promotes something. One inbound text does not convert the record into a texting subscriber.
Informational texts when the prospect handed over the number
Informational messaging is what CTIA describes when a consumer gives a business their phone number and asks to be contacted in the future, which is the tier most inbound sales motions are actually operating in whether or not anyone has labeled it that way. Appointment reminders, welcome texts, and alerts land here, because the first text fulfills a request the prospect already made. The consent expectation is express consent, and CTIA is specific that the prospect needs to agree to receive texts for a specific informational purpose when they hand over the mobile number.
The phrase that does the work is “specific informational purpose.” A prospect who checked a box to get a demo reminder agreed to a demo reminder. Did they agree to a quarterly product roundup? They did not. Reps treat one consent record as a key to the whole contact, and that is where informational quietly turns into promotional without anyone deciding to do it. Nobody signs off on that drift. It happens one helpful message at a time, usually from a rep who is trying to be useful.
Promotional texts need written consent before the first send
Promotional messaging is any text containing a sales or marketing promotion, and the boundary is thinner than reps expect, because CTIA notes that adding a call to action, even a coupon code bolted onto an otherwise informational text, can move the whole message into this category. So how much promotion does it take? Less than one sentence. The consent expectation here is express written consent, given before the send.
Federal rule text sets what “written” means for the calls and texts it covers. 47 CFR 64.1200(f)(9) defines prior express written consent as an agreement in writing bearing the signature of the person called, clearly authorizing delivery of advertisements or telemarketing messages to a specified number, including a clear and conspicuous disclosure that the person is authorizing those messages and that signing is not a condition of buying anything. An electronic or digital signature counts where federal or state contract law recognizes it.
Now the line that should change how your team builds lists. CTIA says message senders should not use opt-in lists that have been rented, sold, or shared, and should create and vet their own. So where did your list come from? If the answer is a vendor, you have a calling list. It is not a texting list, and no amount of warm language in the first message makes it one.
Why texting a prospect and calling a prospect are not the same permission
The federal calling restrictions most sales teams can name are written narrowly, and the scope is the part that gets dropped. 47 CFR 64.1200(c)(1) says no person or entity shall initiate any telephone solicitation to any residential telephone subscriber before the hour of 8 a.m. or after 9 p.m., measured as local time at the called party’s location. The subject of that sentence is a residential telephone subscriber, not every number in your CRM, and the trigger is a telephone solicitation, not every call. 64.1200(c)(2) adds the national Do Not Call registry, and says those registrations must be honored indefinitely until the consumer cancels or the administrator removes the number.
Texting consent does not come from that paragraph. It comes from the consent tier, from the carrier and messaging provider rules your sending number is registered under, and from the written consent requirement that attaches the moment the message promotes something. CTIA is explicit that individual service providers may add their own measures, and it lists campaign pre-approval, provider vetting, in-market audits, and message filtering as examples. So why does a text that is fully consented still never arrive? Usually because the sender was never registered for that campaign, and nothing in the CRM tells the rep that, so the rep keeps sending into a filter and reading the silence as disinterest. If your team has not worked through 10DLC compliance for outbound sales texting, that is the first thing to fix, because none of the channel strategy below matters if the messages are being filtered.
Which failure is yours? Start by assuming both. So the two channels fail in different places. A call fails at the time of day, the registry, and the suppression list. A text fails at the tier, the written consent record, and the campaign registration. Which set does your onboarding actually teach? For most teams it is the calling set, which is why a rep who can recite the Do Not Call rule will still text a purchased list without blinking, and the mistake stays invisible right up until a complaint arrives.
When to call prospects instead of texting them
Call when the conversation can branch. What branches? Discovery branches. Pricing branches, because the first objection is rarely the real one. Security review, procurement timing, and anything involving a second stakeholder all branch, and every branch that happens over text costs you a day while the prospect decides whether answering is worth the thumb time. Over a two week cycle that is the whole cycle.
There is a failure mode worth naming, because it does not look like a failure. The rep texts a prospect a question that needs three follow-ups, the prospect answers the first one, two days pass, the rep sends a nudge, and the thread dies without anyone marking it dead. The CRM shows activity. The deal shows movement. Nothing actually happened. Why does this keep happening? Because a dead text thread is harder to see than a missed call, and because reps drift toward it after a few rejections. It feels like work. It never gets you told no.
Calling is still the strongest medium for negotiation, nuance, and live objection handling, and it works best as part of a coordinated phone, text, and email motion rather than as the only channel anyone is allowed to use. That cuts in the other direction too. A rep who burns a live connect on “confirming we are still on for 2” has just spent the single best thirty seconds of their day on something a text would have closed while they were walking to the kitchen.
If you are deciding across more than two channels, the sequencing logic in our breakdown of SMS versus email for sales campaigns applies here too, and the pros and cons of sales SMS covers what texting does to reply quality once you have the permission sorted.
What happens when a prospect opts out of your texts
This is the part teams get wrong most expensively. The rules are specific. The systems usually are not.
For the calls and texts it covers, 47 CFR 64.1200(a)(10) says a called party may revoke prior express consent by any reasonable method, and it then names the ones that are reasonable per se so there is no argument about them later. In reply to a text, the words “stop,” “quit,” “end,” “revoke,” “opt out,” “cancel,” or “unsubscribe” definitively revoke consent. If a reply uses different words, you must still treat it as valid when a reasonable person would understand those words as a request to revoke, which puts the interpretation burden on you rather than on the prospect who wrote it. Every reasonable-manner request has to be honored within a reasonable time not to exceed ten business days from receipt. And you may not designate an exclusive means of revoking.
Four operational consequences follow from that last sentence. Your opt-out cannot be “reply STOP only.” A prospect who tells a rep on a call to stop texting has revoked. A prospect who emails the rep has created, under 64.1200(a)(11), a rebuttable presumption that consent was revoked once they produce evidence they sent it. And what about a prospect who replies “please take me off this” instead of the magic word? Also revoked. A reasonable person reads that as a revocation, which is the standard the paragraph sets. CTIA says the same thing from the industry side, adding that opt-outs should be supported by phone, email, and text, and that capitalization, punctuation, and letter-case variations do not invalidate the request.
You get exactly one message after that. One. 64.1200(a)(12) permits a single confirmation text, provided it only confirms the revocation, contains no marketing or promotional content, and is the only additional message sent. Send it within five minutes and it is presumed to fall inside the prospect’s prior express consent. Take longer and you are making an argument instead of relying on a presumption.
Here is the question that exposes whether any of this works at your company. A prospect tells a rep on a call to stop texting them. Where does that get recorded, how long does it take, and does it reach the system that actually sends the texts? Does anyone find out if it does not? If the answer to any of those involves a person remembering to update a field between calls, you do not have an opt-out process. You have an opt-out intention.
Build the text and call sequence around the prospect’s last signal
A sequence that sends the same five touches to every record is not a sequence. It is a schedule. The useful version reacts to what the prospect last did, which means the cadence has to know the difference between a record that has gone quiet for three weeks and a record that replied to a text an hour ago and is sitting in the same step anyway.
A fresh signal should change the next action immediately. The prospect replied to a text, so the next step is a call. Not touch four of the cadence. A warm event earns specific, immediate outreach. Cold records get a deliberate multichannel pattern until something changes their status, and if nothing changes it, they get disqualified rather than sitting in the queue forever. How fast is your team at disqualifying? That number tells you more about next quarter than the dial count does.
Then there is the queue, which compounds. Records that do not answer today roll into tomorrow while new leads keep arriving, and if retry rules and priority are not written down anywhere, the oldest opportunities sink underneath the newest ones until a rep stumbles on them by accident months later. At that point the texting question is academic. Nobody is reaching those records at all. Set the rule first. Then pick the channel.
Where to record text and call consent so the next rep can see it
Consent that lives in one rep’s memory is not consent your company can prove. So what does the record need? Four things. Which tier the permission covers. Where it came from, meaning the form, the checkbox, the inbound text, or the call. When it was captured. And whether it has been revoked.
That is a CRM field problem before it is a tooling problem. Still, the tooling decides whether the field gets filled. If a rep has to open a second tab and type the outcome after every conversation, the field will be empty by Thursday. Not because the rep is lazy. Because the twelfth one lands at 4:40 on a day that already went badly.
Kixie is sales engagement software for business calling and texting, and the relevant part here is not the feature list, it is where the evidence ends up when the rep is done. Calls, texts, outcomes, and recordings log to the CRM automatically, so the activity history exists without anyone retyping it at the end of a call block. SMS templates keep the sent text consistent with what the consent record says the prospect agreed to. Kixie’s business texting supports checks against the National Do Not Call Registry and your internal suppression lists, and customers remain responsible for their own calling and texting practices and legal review. None of that decides your consent policy. It decides whether the policy is observable.
What a manager should inspect before reps text or call prospects
Four things. All of them are checkable this week.
First, pull ten records your team texted in the last month and ask which tier each message was in and what evidence supports it. What if the answer is “they seemed interested”? Then you have found the gap. Second, trace one opt-out end to end, from the moment it was expressed to the moment the sending system actually stopped, and count the hours rather than the intention, because the gap between those two numbers is the entire exposure. Third, look at your text threads with no reply for more than a week and check whether anyone dispositioned them. That is where pipeline goes to quietly die. Fourth, check whether your purchased or imported lists are flagged as call-only. If they are not, somebody will text them.
Fix those four and the channel question mostly answers itself. The rep knows what they are allowed to send, the system knows when to stop, and the manager can see both without asking anyone. Then the only decision left is the easy one. Does this message finish without a reply, or does it need a conversation?
When to text prospects instead of calling FAQs
Is it legal to text a prospect who has not opted in
It depends on who started the exchange and what the message does. Under CTIA’s framework, if the prospect texts you first and you simply respond, no additional permission is expected. If you are sending the first message, you need express consent for an informational message and express written consent for anything promotional, and 47 CFR 64.1200(f)(9) sets what written means for the messages the federal rule covers, down to the signature and the disclosure that signing cannot be a condition of purchase. Is your specific message to your specific recipient covered? That is a question for counsel, not a blog.
How early is too early to text a prospect
The clearest federal timing rule is a calling rule, not a texting rule. 47 CFR 64.1200(c)(1) prohibits telephone solicitations to a residential telephone subscriber before 8 a.m. or after 9 p.m., local time at the called party’s location. Many teams apply that same window to texts as a floor rather than a ceiling. Is that required by the paragraph? No, it is a practice, and worth knowing as a practice. The operational point is simpler. Use the prospect’s local time, not your own, and make the system enforce it rather than the rep.
Should you text a prospect before calling them
Only if you already have the permission that text requires, which is usually a higher bar than the call rather than a lower one, which is the opposite of how most reps rank the two channels in their heads. If the prospect handed you a mobile number and asked to be contacted, a short confirming text before a scheduled call reduces no-shows. If the number came from a purchased list, no. CTIA says senders should not text opt-in lists that were rented, sold, or shared.
What should you do when a prospect does not reply to your text
Change the channel or close the record. Do not send the same ask again. A second identical text tells you nothing and costs you goodwill. Call once, leave a specific reason to call back, and set a disposition. A thread with no reply and no disposition is the most common way a deal gets counted as worked when nobody worked it.
Sources
How this article was built. The consent tiers and messaging conduct expectations are taken from the current CTIA best practices document, and the calling, revocation, and written consent requirements are quoted from the current federal rule text, both read directly on the review date at the publishers linked below, with the load-bearing language quoted rather than paraphrased so its exact scope travels with it. No reply rate, open rate, connect rate, or response-time benchmark is quoted for texting or calling, because published figures do not transfer to your segment, offer, list source, or regions, and no current primary source was available for the ones commonly repeated. The channel rules in this article, including the finishes-without-a-reply test, the sequencing guidance, and the four manager checks, are this article’s own operating guidance and are not requirements of any rule or document named here. CTIA’s principles are voluntary industry best practices and state that they do not constitute legal advice. Rules are amended and this article’s review date is the date its citations were verified. This article is general information for sales teams, not legal advice, and it does not analyze which requirements apply to any particular call, text, or recipient, including whether any given number or message falls within the paragraphs cited; consult qualified counsel about your own practices. Kixie publishes this article and sells sales engagement software for business calling and texting.
- 47 CFR § 64.1200, Delivery restrictions, the Electronic Code of Federal Regulations published by the Office of the Federal Register, section text as currently in force and last substantively amended March 25, 2026, for § 64.1200(c)(1) prohibiting any telephone solicitation to “any residential telephone subscriber before the hour of 8 a.m. or after 9 p.m. (local time at the called party’s location)”; for § 64.1200(c)(2) requiring national Do Not Call registrations to “be honored indefinitely, or until the registration is cancelled by the consumer or the telephone number is removed by the database administrator”; for § 64.1200(a)(10) naming “stop,” “quit,” “end,” “revoke,” “opt out,” “cancel,” or “unsubscribe” sent in reply to an incoming text as a reasonable means per se to revoke consent, requiring other wording to be honored “if a reasonable person would understand those words to have conveyed a request to revoke consent,” requiring all reasonable-manner requests to “be honored within a reasonable time not to exceed ten business days from receipt of such request,” and prohibiting senders from designating “an exclusive means to request revocation of consent”; for § 64.1200(a)(11) creating a rebuttable presumption of revocation when other means such as voicemail or email are used and the called party produces evidence of the request; for § 64.1200(a)(12) permitting one confirmation text that “does not include any marketing or promotional information” and is “the only additional message sent,” presumed within prior express consent if sent within five minutes; and for the § 64.1200(f)(9) definition of prior express written consent as “an agreement, in writing, bearing the signature of the person called” with a clear and conspicuous disclosure that the person “is not required to sign the agreement” as a condition of purchase.
- Messaging Principles and Best Practices, CTIA, the wireless industry association that publishes these voluntary best practices for its member companies, dated May 2023 and the version CTIA serves at this URL on the review date, for the Exhibit II classification of conversational, informational, and promotional messaging and their associated implied, express, and express written consent principles; for the statement that “if the Consumer initiates the conversation and the Non-Consumer simply responds, then no additional permission is expected”; for the requirement that “a Consumer needs to agree to receive texts for a specific informational purpose when they give the Non-Consumer their mobile number”; for the note that adding a call to action “may place the message in the promotional category”; for the guidance that senders “should not use opt-in lists that have been rented, sold, or shared to send messages”; for the opt-out guidance that senders “should support multiple mechanisms of opt-out, including phone call, email, or text,” should send “one final opt-out confirmation message per campaign,” and that validity “should not be impacted by any de minimis variances” such as capitalization, punctuation, or letter case; and for the note that individual service providers may add measures including “campaign pre-approval, Service Provider vetting, in-market audits, or Unwanted Message filtering practices.” The document states it does not constitute or convey legal advice.
- Kixie business text messaging, Kixie product documentation, for the present-tense description of shipped capability cited in this article: automatic logging of calls, texts, outcomes, and recordings to the CRM, SMS templates, and support for checks against the National Do Not Call Registry and internal suppression lists, with customers remaining responsible for their own calling practices and legal review.
Sources verified and content reviewed by the Kixie Research Team on October 5, 2026. All source links checked on October 5, 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