The Problem With SMS Provider Selection
Every bulk SMS provider homepage looks the same: "99.9% delivery rates," "enterprise-grade," "global coverage," "instant delivery." All of them claim to be the best. Few of them have meaningful differences on the surface.
The differences that actually matter are underneath: routing quality, the honesty of their DLR data, pricing transparency, compliance support, and what happens when something goes wrong.
This is the framework we'd use if we were a buyer.
First: Define What You Actually Need
Before comparing providers, be honest about your requirements:
Volume: How many messages per month? Per day? Peak per hour? Some providers are excellent for 10,000 messages/month but have throttling issues at 500,000.
Destinations: UK only? UK + EU? Global? Some providers have excellent UK direct routes and poor international routing. Others are the opposite.
Protocol: Do you need HTTP API, SMPP, or both? Not all providers offer SMPP.
Inbound SMS: Do you need to receive replies? What happens to STOP replies? Can your system process them programmatically?
Sender ID: Do you need alphanumeric sender IDs? Virtual numbers? Shortcodes?
Compliance support: Do you need a Data Processing Agreement? Sender ID registration assistance? Some providers offer this, many don't.
Write down your requirements before you start evaluating providers. It prevents being swayed by features you don't need.
The Questions That Separate Good Providers from Bad
"Do you use grey routes?"
This is the most important question. Grey routes are unofficial paths through carrier networks — cheaper, less reliable, with fake or delayed DLRs. Any provider that doesn't know what grey routes are, or that hedges the answer, is using them.
Good answer: "We use only direct and tier-1 routes. Here are the specific routes we use for UK and [your destinations]."
"Are your DLRs genuine final-status confirmations from destination networks?"
Some providers send you a "delivered" DLR when the message hits their SMSC, not when the destination network confirms delivery. These are useless for list hygiene — they tell you nothing about whether the message reached the handset.
Good answer: "We pass through DELIVRD/UNDELIV/REJECTD final status codes from destination networks. Our DLR architecture is [explanation]. Average DLR latency is X minutes."
"What is your real delivery rate for UK Tier-1 routes?"
"99.9%" claims are nearly always based on soft metrics. Ask for actual delivery rate data for UK sends over the last 30 days, broken down by DELIVRD, UNDELIV, ENROUTE, EXPIRED, and REJECTD.
A legitimate provider will share this. Anyone who can only give you the marketing number and nothing behind it should be viewed sceptically.
"What's your uptime SLA and how was it met last quarter?"
Any enterprise-grade provider should have an uptime SLA and should be able to tell you how they performed against it. Ask to see their status page history, not just the current status. Providers with frequent outages or lack of transparency about downtime history are a risk.
"What happens when I hit a delivery issue at 2pm on a weekday?"
This tests their support model. Do they have: direct phone support? 24/7 chat? Email with a defined SLA? An account manager?
Providers who point you to a ticket system with "we'll get back to you in 24 hours" for a production SMS system are inadequate for anything time-sensitive.
Pricing: What to Watch For
Bulk SMS pricing looks simple on the surface but has hidden complexity.
Per-segment pricing vs per-message pricing: Most providers quote per-message, which is the same as per-segment for 1-segment messages. For longer messages (multi-segment), the total cost is segments × rate, not messages × rate. Make sure you're comparing segment prices, not message prices.
Mandatory credit top-ups: Some providers require you to buy in chunks of £50, £100, or £500. Your unused credit may expire. Check the minimum purchase and expiry terms.
Monthly fees: BulkSMSRates has no monthly fees. Many providers charge £25–£150/month for access to features that should be standard (SMPP, DLR webhooks, sender ID registration).
Inbound SMS fees: Receiving replies often costs extra. Some charge per inbound message. Clarify what you're actually paying for two-way messaging.
Shortcode fees: If you need a shared or dedicated shortcode, these typically cost £200–£500/month in the UK. Factor this in if your campaign model requires it.
A useful exercise: take your expected monthly volume and destination mix and get a full cost estimate (including all fees) from 3–4 providers. Then compare. The headline rate often looks different from the total cost.
The Major Providers: A Realistic Assessment
We'd be doing this guide a disservice if we didn't mention the major players and what they're genuinely good and bad at.
Twilio
Genuinely excellent developer experience. Best-in-class API documentation. Strong global coverage. Very reliable.
Expensive compared to alternatives — UK SMS is around £0.0383/segment vs £0.0300 at BulkSMSRates. For low-volume developers testing an integration, the documentation and SDK quality justifies the premium. For high-volume production sends, the difference compounds quickly: 1 million messages/month = £6,000 more per year.
No SMPP on standard plans. Support is ticket-based unless you're on an enterprise plan.
MessageBird / Bird
Strong European coverage. Good API quality. Has WhatsApp Business API alongside SMS.
Pricing is competitive for enterprise accounts but can be opaque for smaller customers. Some customers report inconsistent support response times.
ClickSend
Popular for small to medium businesses. Good UI for non-technical users. No SMPP support — if you need that, they're not the right choice.
Vonage / Nexmo
Enterprise-focused, strong carrier relationships, comprehensive API. Pricing is enterprise-level to match.
VoodooSMS
UK-focused, competitive pricing for UK sends, simple platform. Less suited for high-volume international or SMPP use cases.
BulkSMSRates
Yes, we're comparing ourselves here. We're transparent about where we win: lowest UK pricing, SMPP and HTTP API on all accounts, no monthly fees, direct tier-1 routes with genuine DLR. We're a good fit for price-sensitive high-volume senders and technical teams who need SMPP. We're not going to win a comparison on brand name recognition or documentation depth vs Twilio.
The Checklist
Use this when evaluating any provider:
Routing and Delivery:
- •[ ] Confirm: no grey routes for your target destinations
- •[ ] Confirm: genuine final-status DLRs from destination networks
- •[ ] Request: actual delivery rate data for your destination mix (last 30 days)
- •[ ] Check: uptime history (ask for or find their status page)
Pricing:
- •[ ] Get per-segment rate (not per-message) for your destinations
- •[ ] Clarify: inbound SMS cost
- •[ ] Clarify: monthly fees
- •[ ] Clarify: minimum purchase / credit expiry
- •[ ] Clarify: shortcode fees if needed
Technical:
- •[ ] API documentation quality (can you actually integrate from this?)
- •[ ] SDK availability for your language
- •[ ] SMPP availability (if needed)
- •[ ] DLR webhook / callback support
- •[ ] Batch sending capability
- •[ ] Number validation / HLR lookup
Compliance:
- •[ ] Data Processing Agreement available
- •[ ] Sender ID registration support
- •[ ] STOP/opt-out processing (automatic or manual?)
- •[ ] Data residency (UK/EU, relevant for GDPR)
Support:
- •[ ] Support hours
- •[ ] Contact methods (phone, chat, email)
- •[ ] Response time SLA
- •[ ] Account manager for high-volume accounts
Integration and onboarding:
- •[ ] Free trial / test credits available
- •[ ] Time to first message (documentation, API key, first send)
- •[ ] Migration support (if switching from another provider)
Run all providers through this checklist before committing. The differences become much clearer when you're comparing across the same criteria rather than each provider's marketing claims.
Making the Switch
If you're already with a provider and considering switching: check your contract for notice periods (some require 30–90 days notice), plan the migration during a low-volume period, and test the new provider thoroughly before cutting over production traffic.
BulkSMSRates offers migration support and can match your existing sender IDs and pricing in most cases. Start with a free account, send some test messages, verify DLRs are genuine, and compare delivery rates side by side. The pricing page shows what you'd pay versus your current provider — no commitment required.