SMS vs email for sales outreach — when to use each

Email and SMS are not the same message in two lengths. An email is a document with a folder problem: you can write as much as you like, and you will never learn where it landed. A text is a wire format with a price: 160 characters if every character sits inside one specific alphabet, 70 if a single one does not, billed per segment, sent from a number a registry vetted before you were allowed to use it. Those differences, not tone, decide which message belongs on which channel.

The two channels differ in unit, not in register

Both channels carry words, so teams reach for the same playbook and get surprised twice — once by the bill and once by the silence.

The unit of email is the message. Its marginal cost is close to zero, its length is unconstrained, it threads, it survives search, and it can carry a link, an attachment and a calendar invitation without ceremony. What it cannot do is tell you where it went. A message accepted by the receiving server and filed in spam looks exactly like a delivered one in your logs.

The unit of SMS is the segment. Its marginal cost is real and it multiplies, its length is constrained by an encoding decision you may not know you made, it does not thread reliably across senders, and it carries essentially nothing except characters and a link that will itself attract filtering. What it can do is reach a device directly, without a folder in between.

Everything practical follows from those two paragraphs. Email is where you make a case. SMS is where you make an arrangement.

An SMS is a wire format, and the encoding sets the price

This is the part most sales teams never learn, and it costs them money every month.

3GPP TS 23.038 defines the GSM 7-bit default alphabet used for SMS. A single short message carries 140 octets, and 140 times 8 divided by 7 gives 160 characters when everything you wrote sits inside that alphabet. Anything outside it forces UCS-2, a 16-bit encoding, and 140 octets at 16 bits per character gives 70 characters. Not 160 shortened a bit. Seventy.

Concatenation costs more again. A message longer than one segment carries a user data header so the handset can reassemble it, and that header eats payload: concatenated segments hold 153 GSM-7 characters or 67 UCS-2 characters each.

Now the trap. The characters that force UCS-2 are exactly the ones a word processor inserts for you. A curly apostrophe in "don't". A typographic quotation mark. An en dash between two numbers. An accented name. An emoji. Any one of them re-encodes the entire message. A 150-character text that looked like one segment becomes three the moment somebody pastes it out of a document, and you pay for three.

3GPP TS 23.038 also defines an extension table reached through an escape code, so a handful of characters that do look like plain ASCII — the braces, the square brackets, the backslash, the caret, the tilde, the pipe and the euro sign — each cost two septets rather than one. A message full of square brackets is shorter than it appears.

Three operational rules fall out of this:

• Write the SMS in a plain-text editor, never in a word processor, and paste nothing.
• Count segments before you count characters. The number that matters is segments, because that is the billing unit and the carrier-filtering unit.
• Personalisation tokens are variable-length. A template that is 155 characters with "Sam" becomes 168 with "Priyadarshini" and silently becomes two segments for part of your list.

Autocloz's sequence pre-flight computes this before a campaign starts, using exactly the arithmetic above — 160 or 70 for a single segment, 153 or 67 for concatenated ones — and warns when a step exceeds six segments, because many carriers reject messages beyond that. It also flags an SMS body with no opt-out hint, because several carriers expect one in the body itself.

What each channel lets you measure, and what it hides

The feedback asymmetry is larger than the cost asymmetry, and it changes how you should run each channel.

Email gives you a rich, partly untrustworthy telemetry stream. Bounces are real and classifiable. Complaints reach you through feedback loops. Clicks are real. Opens are the problem: Apple's Mail Privacy Protection pre-fetches tracking pixels, so a recorded open can mean a machine fetched an image. And placement — the single most consequential fact — is not reported at all. You learn about a spam-folder problem indirectly, from a reply rate that falls while acceptance stays flat.

SMS gives you almost nothing, but what it gives you is honest. A delivery receipt means a carrier accepted the message and, usually, that the handset acknowledged it. There is no open. There is no read receipt available to the sender. There is no link between "delivered" and "seen", because a modern handset may file an unknown sender into a separate list the recipient never opens. The one unambiguous signal SMS produces is a reply.

So the measurement discipline differs. On email, instrument placement independently and distrust opens — the difference between an open, a delivery and a placement is worth internalising before you build a report on any of them. On SMS, track the ratio of provider-accepted to carrier-delivered per carrier, because a gap that opens on one carrier and not the others is a classification problem rather than a list problem, and it is the only early warning the channel offers.

Two different ways of being vouched for

Both channels require somebody to vouch for you before your messages are trusted. The mechanisms are not alike.

Email vouching is cryptographic and self-service. You publish SPF and DKIM records, align them under DMARC, and the receiving provider verifies them on every message. Nobody approves you. Google's bulk sender requirements ask senders of 5,000 or more messages a day to authenticate with SPF and DKIM, publish DMARC for the sending domain, support one-click unsubscribe, and keep the spam rate reported in Postmaster Tools below 0.30%. Microsoft applied comparable requirements to Outlook.com consumer mail from 5 May 2025, rejecting non-compliant high-volume senders with 550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level. You can set all of this up on a Tuesday afternoon.

SMS vouching is a registration you apply for. In the United States, application-to-person messaging over ordinary ten-digit numbers runs through 10DLC, where The Campaign Registry verifies both the brand and the campaign. The registry states that Verified brand status "is a requirement to register campaigns and send messages on 10DLC" and that an EIN or tax ID is required so the brand's identity can be confirmed. Throughput is assigned by that registration rather than negotiated: The Campaign Registry describes AT&T as assigning throughput per campaign through a message class, and T-Mobile as allocating a daily allowance per brand tied to the brand's EIN and shared across all of that brand's campaigns.

India runs the same principle through a different instrument. TRAI's Telecom Commercial Communications Customer Preference Regulations, 2018 — issued 19 July 2018 and in force from 28 February 2019 — mandate distributed ledger technology for registration of senders, headers and content templates, and define a header as "an alphanumeric string of maximum eleven characters or numbers assigned to an individual, business or legal entity".

The practical consequence for planning: you can start emailing this week and you cannot start texting this week. Registration takes days at best, and it gates the channel entirely rather than degrading it.

The consent regimes point in opposite directions

This section is a summary for planning, not legal advice, and the right answer depends on the recipient's jurisdiction rather than yours.

United States email is an opt-out regime. The CAN-SPAM Act of 2003 requires accurate headers, a non-deceptive subject line, a valid physical postal address and a working opt-out honoured within 10 business days, and the Federal Trade Commission states that the law makes no exception for business-to-business email.

United States texting is an opt-in regime with a fast clock. 47 CFR 64.1200(a)(10), effective 11 April 2025, requires a caller to honour a request to revoke consent within a reasonable time not exceeding 24 hours. One portion of that rule — the requirement to treat a revocation received in response to one type of message as applying to all future robocalls and robotexts from that caller on unrelated matters — was granted a limited waiver by the FCC's Consumer and Governmental Affairs Bureau in DA 25-312 on 7 April 2025, and the Bureau has since extended that portion further, to 31 January 2027, in DA 26-12. The rest of the rule took effect as planned.

Carrier policy sits on top of the statute and is stricter in one specific way that invalidates a common growth tactic. CTIA's Messaging Principles and Best Practices states that a consumer opt-in "should not be transferable or assignable" and "should apply only to the campaign(s) and specific Message Sender for which it was intended or obtained". A list bought from a vendor who collected consent for their own programme fails that standard whatever the contract says. The full TCPA, 10DLC and carrier picture is the reference to work from before a first send.

Where SMS actually earns its cost in a sales motion

Given the price, the registration and the near-total absence of feedback, SMS earns its place in a narrow band — and it is a genuinely valuable band.

Use it where the message is a coordination message to somebody who is already expecting to hear from you:

• A meeting confirmation and a same-day reminder, where a missed meeting costs far more than a segment.
• A "running five minutes late" note before a call you both booked.
• A link to a document you agreed on a call to send, where the text is the pointer and the email is the payload.
• A short re-confirmation after a no-show, which is the highest-value text most sales teams never send.
• A reply nudge on a thread the prospect started, where the relationship and the consent both already exist.

Do not use it as a first touch to a purchased number. That is where the registration risk, the complaint risk and the legal risk all concentrate, and it is also where it works least well, because a cold text from an unknown number reads as a scam to a 2026 buyer.

Autocloz's free plan runs email and SMS as steps in the same sequence with a shared suppression list and per-channel daily caps — 1,000 email sends and 250 texts a day across 5 users and 10 mailboxes — so you can start free and test the confirmation-and-reminder pattern above without touching the cold-first-touch pattern at all.

A decision rule by message purpose rather than channel preference

Sort each message you want to send by what it is asking for, and the channel picks itself.

• Making a case — a point of view, a reason to care, a link to something worth reading. Email. Length is free there and expensive here.
• Making an arrangement — a time, a confirmation, a reminder, a short yes-or-no. SMS, if consent exists. Immediacy is what you are paying for.
• Sending an artefact — a proposal, a deck, a contract. Email, always. The text can point at it; it should never carry it.
• Reaching somebody who has never heard of you — email, or a call, or LinkedIn. Not SMS.
• Reaching somebody who asked you to follow up — whichever channel they used to ask, which is a rule that costs nothing and is broken constantly.

Two structural requirements make this workable rather than theoretical. First, one suppression list: an opt-out on either channel has to be read by both, because a person who replied STOP to a reminder and then receives a marketing email has been told the two systems do not talk. Autocloz writes a stop keyword against the wildcard channel so the suppression covers SMS, WhatsApp and calling for that number, and matches both the raw and E.164 spellings so a differently formatted import cannot slip past it. Second, one place to read the replies, because an SMS reply and an email reply to the same sequence are the same conversation — which is what a single inbox across all five channels is for, alongside the sender, template and quiet-hours configuration for texting itself. If you already have a carrier relationship, connecting it directly through the Twilio SMS integration keeps the registration you have.

What SMS cannot do, and what Autocloz does not do

SMS cannot tell you it was read, cannot carry a case, and cannot be started cold without accepting a category of risk that is different in kind from email's. Any advice that treats it as email with urgency is advice that has not paid an SMS bill or read a carrier policy.

On the product side, four boundaries stated plainly. Autocloz does not verify your 10DLC or DLT registration before dispatching a text. The pre-flight surfaces it as guidance and the channel-health view flags a missing registered template, but the send path itself will hand an unregistered message to your provider and let the carrier decide. Registration is a prerequisite you confirm; it is not a gate the software enforces.

The consent ledger is recorded on SMS but not enforced on it. Opt-in enforcement is off by default and switched on per workspace, and today only the WhatsApp dispatch path reads that setting. A workspace that turns on opt-in enforcement expecting it to cover texts is expecting something the code does not currently do — the do-not-contact list is checked on every text, the consent ledger is not.

The segment estimator is an approximation. It treats any character above ASCII 127 as forcing UCS-2, which is the right call for the smart quotes and accents that cause most real incidents, but it does not charge the extension-table characters their second septet. A body full of braces, brackets or euro signs can therefore cost one more segment than the pre-flight predicted.

And quiet hours on SMS are evaluated in the campaign's configured timezone if one is set, otherwise in the sending account's timezone. They are never computed from the recipient's own timezone — only the email path consults a lead's timezone, and only where the campaign carries a sending window. For a channel where the permitted window is defined by law as local time at the called party's location, that difference is the one to configure deliberately rather than inherit. None of this is legal advice: the gate enforces the rules you configure, in the jurisdictions you name, and knowing which rules apply to a given recipient stays with you.