You're probably paying for twice the messages you think you're sending.
Credit-based billing is built to be opaque. Here's what's actually happening to your SMS budget, and the questions to ask before you sign anything.
"You have to really watch their billing. It rarely matches what you are quoted, but they will fix it when you point it out."
Verified review — Capterra and Software Advice
Why SMS billing is confusing by design
Most Salesforce SMS platforms sell you message credits, not messages. The distinction sounds minor. It isn't.
When you buy 10,000 credits, you're not buying 10,000 conversations. You're buying a pool that drains in ways that are nearly impossible to predict at contract time. Message segmentation, carrier surcharges, MMS versus SMS rates, number type differences, and international delivery fees all pull from the same pool, often with no line-item visibility until the invoice arrives.
You budget for volume, get billed for credits, and spend time reconciling the difference every month.
This is the default behavior of any platform billing by credits without real-time segment transparency. Sharp admins learn to "really watch the billing."
This is the default behavior of any platform billing by credits without real-time segment transparency. It's also why sharp admins learn to "really watch the billing."
The segment problem, explained plainly
SMS was built on a 160-character limit. Everything above that splits into chunks called segments, each billed separately. Once a message exceeds 160 characters, the per-segment limit drops to 153 characters to make room for stitching headers. A 320-character message isn't 2 segments. It's 3.
Add a personalization token, your company name, a call-to-action, and a URL. Your "one message" is already multiple credits before anyone reads it.
That's a normal, professional follow-up message. No fluff. It costs twice the quoted rate every time it sends.
The emoji problem is worse
Adding a single emoji to a message changes the encoding from GSM-7 to UCS-2. That one change cuts the per-segment character limit from 153 to 67. A message that sent as 2 segments clean can become 4 or 5 segments with a smiley face attached.
The mechanism: standard SMS uses GSM-7 encoding, which fits 160 characters into 140 bytes. Unicode (UCS-2) uses 16 bits per character instead of 7, leaving room for only 70 characters per single segment, or 67 per segment in a multi-part message. The switch is automatic and applies to the entire message the moment any non-GSM character appears, including emojis, smart quotes copied from a word processor, or certain accented letters.
Sales teams use emojis. Marketing teams use emojis. Your automated follow-ups probably use them too. On a credit-based platform, every one of those messages is consuming more credits than the rep who set up the template realized.
Run your actual templates through a segment calculator before you agree to any credit-based pricing. The number will surprise you.
What transparent billing actually looks like
Either you know what you're paying before the message sends, or you're reconciling surprises after the fact. Those are the only two options.
| Billing Factor | Credit-Based Platforms | Conversations |
|---|---|---|
| Pricing unit | Message credits | Per message, flat |
| Segment surcharges | Applied automatically, often silently | Included, no multiplier |
| Emoji / UCS-2 penalty | Encoding switch multiplies credits consumed | Flat rate regardless of encoding |
| Carrier fees | Additive to credit pool | Bundled in quoted rate |
| Overage visibility | Post-invoice discovery | Real-time usage dashboard |
| Invoice predictability | Requires monthly reconciliation | Matches quoted volume |
| Budget planning | Estimate, buffer, hope | Message volume = billing volume |
Good billing feels boring. You approve the budget once and never audit it again.
7 questions to ask any SMS vendor before you sign
Most buyers don't know what they don't know when evaluating SMS platforms. These questions surface what doesn't show up in a demo.
-
Q1
Does your pricing include carrier surcharges, or are those additive?Carrier fees for 10DLC, toll-free, and short code delivery can add 15–30% to your effective per-message cost. If they're not in the quote, they show up in the overage.
-
Q2
How do you count segments for messages over 160 characters?The single biggest hidden cost in SMS. If the answer is "it depends," ask them to demo billing on a 250-character message in real time.
-
Q3
Does adding an emoji change how credits are counted?Any non-GSM character, including emojis, switches encoding from GSM-7 to UCS-2, dropping the per-segment limit from 153 to 67 characters. On a credit platform, that can triple the cost of a single message.
-
Q4
Can I see a real invoice from a current customer at similar volume?Quotes are optimistic. Invoices are real. A vendor confident in their billing will show you one without hesitation.
-
Q5
What happens when I hit my credit limit mid-month — does sending stop, or do overages auto-apply?Auto-overage billing at peak campaign times is a common budget surprise. Explicit control beats a platform that keeps sending and charges you afterward.
-
Q6
Is there a real-time usage dashboard inside Salesforce showing credits consumed versus remaining?If your ops team has to log into a separate billing portal to check consumption, they won't, until after the overage. Usage visibility inside the tool you already use isn't optional.
-
Q7
What's your billing dispute process, and how long does resolution typically take?The verified review we opened with exists for a reason. A platform with clean billing has a short, boring answer to this question.
Print this list. A platform that can't answer these questions in the meeting, without a follow-up email, is one whose billing you will audit every month.
Know your number before you commit.
See what your current or projected message volume actually costs under a credit-based model, then compare it against flat-rate billing.
