Skip to content
Notifications
Clear all

Brevo's SMS pricing is a trap - check the per-credit cost carefully.

4 Posts
4 Users
0 Reactions
3 Views
(@crm_hopper_2025)
Estimable Member
Joined: 2 months ago
Posts: 113
Topic starter   [#10179]

Alright, fellow platform nomads, I need to vent about something that just burned me during my latest evaluation phase. I've been poking at Brevo (formerly Sendinblue) for a lightweight marketing stack, and their SMS offering looked promising at first glance. But let me tell you, the pricing model is one of those classic "looks cheap until you run the numbers" scenarios. It's a trap for anyone who doesn't do the per-credit math.

We all know the drill—you see a price like "$15 for 5,000 credits" and think, "Wow, that's a lot of SMS!" Nope. That's not how it works. The trap is in the credit cost *per message segment*, which varies wildly by country. And a "message segment" isn't even a full SMS in many cases.

Here’s what I mean. Brevo states that **1 credit = 1 SMS segment**. But an SMS segment is only **160 characters** for GSM encoding (standard Latin alphabets) or **70 characters for Unicode** (emojis, special characters). Go over that by even one character, and you're charged for a second segment. So your "single" SMS can easily cost 2, 3, or even 4 credits.

Let's break down the real cost with their current credit packs:

* **Starter Pack:** $25 for 5,000 credits. That's **$0.005 per credit**.
* **To send a 2-segment SMS (say, 161 characters) to a US number:** Cost = 2 credits. That's **$0.01 per message**.
* Sounds cheap, right? But compare it to a direct, volume-based provider like Twilio. Their pay-as-you-go price for a US SMS is **$0.0075 per segment**. For that same 2-segment message, that's **$0.015**.

Wait, so Brevo is cheaper? Not so fast. This is where the country-based multiplier hits you. Brevo doesn't just charge 1 credit per segment for every country. They have a hidden multiplier based on the destination.

For example, to send to the **UK or Germany, it's 2 credits per segment**. To **Brazil, it's 3 credits per segment**. Suddenly, that 2-segment message to Brazil costs **6 credits**. With the Starter pack pricing, that's **$0.03 per message**. Twilio's direct rate to Brazil is **$0.08 per message** (not per segment), so Brevo can still be cheaper here, but you MUST check their destination list.

The real kicker? **You're buying credits upfront.** If you don't use them, they sit there. If you need more in a month, you buy another block. It lacks the transparency of a pure per-message model and ties up your cash. You become a credit manager on top of everything else.

My migration war story here is short: I almost signed up for a yearly plan based on the "credit volume" before I dug into the per-destination tables and did the math for my international audience. The cost would have been nearly double my initial estimate. I ended up sticking with a direct provider for SMS and using Brevo for email only.

Always, *always* pull out your spreadsheet and calculate:
1. Your average message length in characters.
2. Your top destination countries.
3. The per-segment cost in credits for those countries from Brevo's list.
4. The actual credit cost from your chosen pack.

Has anyone else fallen into this trap or found a clever way to make Brevo's SMS work cost-effectively for a specific use case? I'd love to hear your experiences.

Hopefully last migration,
crm_hopper_2025



   
Quote
(@integrations_jane_new)
Estimable Member
Joined: 3 months ago
Posts: 106
 

Yeah, that segment pricing gets a lot of people. The Unicode vs GSM split is especially painful if you're sending any kind of transactional message with a checkmark or a location pin.

I'd add to check their **dedicated number pricing**. If you need a sender ID, the monthly fee for a dedicated virtual number isn't included in those credit packs and adds up quick. It turns that "lightweight" cost into something pretty substantial for regular use.

Have you compared it to something like Twilio directly for SMS? The per-segment cost is clearer there, even if you need to handle more of the setup.



   
ReplyQuote
(@infra_auditor_nina)
Reputable Member
Joined: 4 months ago
Posts: 159
 

> the Unicode vs GSM split is especially painful

That's putting it mildly. If your monitoring or alerting system uses non-GSM characters, you're automatically paying double, sometimes quadruple, for the same message content. It's a cost that's invisible until you get the bill.

Twilio's pricing is clearer, sure, but their complexity just shifts elsewhere. You're on the hook for carrier filtering, number provisioning, and managing your own compliance logs. For a small team, that's a full-time audit trail waiting to be neglected.


- Nina


   
ReplyQuote
(@devops_barbarian_v2)
Estimable Member
Joined: 3 months ago
Posts: 123
 

> "Have you compared it to something like Twilio directly for SMS?"

Oh sure, Twilio. The platform where you get to pay for the privilege of debugging carrier filtering at 2am. No thanks.

The dedicated number fee is a valid gotcha, but at least Brevo's credit model is predictable once you run the math. Twilio's per-segment clarity just means you see exactly how much you're being nickel-and-dimed for every delivery receipt and compliance log you're supposed to manage.

You're trading one invisible cost for another. I'd rather take the credit trap I can spreadsheet than the compliance trap I can't automate away.



   
ReplyQuote