Working with Twilio?

Twilio messages not arriving? We fix it.

A Twilio account that looked fine in testing can go quiet the moment real US numbers are involved, because carriers are filtering traffic that was never registered properly. We untangle the registration side and the code side together so messages actually land.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

twilio-errors.log

still failing

What it is

Twilio at a glance

Twilio is a communications platform that lets software send text messages, place phone calls, verify users with one-time codes and run full contact centres through an API rather than through phone company paperwork. It is used by banks, healthcare providers, retailers and startups to reach customers on the channel the customer prefers.

The company is Twilio, Inc., listed on the New York Stock Exchange as TWLO, founded in 2008 by Jeff Lawson, Evan Cooke and John Wolthuis. Its product line now covers SMS, MMS, voice, WhatsApp, email through SendGrid (acquired in 2019), the Segment customer data platform (acquired in 2020), Verify for two-factor codes, Flex for contact centres, Studio for low-code call and message flows, Programmable Video, and TwiML for scripted call control.

Since 2023, US carriers require application-to-person SMS traffic to be registered under the A2P 10DLC framework, with a brand and a campaign that describe who is sending and what they are sending. Unregistered traffic is throttled or dropped outright, which is where most Twilio problems now begin.

Type
Communications APIs (CPaaS)
First released
2008
License
Proprietary SaaS
Maintained by
Twilio, Inc.
Typically used for
SMS and MMS, voice, 2FA, appointment reminders, contact centres, WhatsApp Business

The honest version

Twilio pros and cons

No technology is all upside. This is where Twilio earns its place and where it tends to cause trouble.

Where Twilio is strong

  • One account, many channelsSMS, MMS, voice, WhatsApp, email through SendGrid, video and Verify all run under a single billing relationship and a single set of credentials.
  • Global reachPhone numbers and routes are available in most countries, which saves signing separate contracts with local carriers for every market you expand into.
  • Mature SDKs and documentationOfficial libraries exist for every mainstream language, and the API reference is detailed enough that engineers rarely have to guess at behaviour.
  • Studio for low-code flowsBusiness users can draw simple IVR menus and SMS conversations in a visual editor without a developer writing a state machine from scratch.
  • Strong carrier relationshipsFor US SMS in particular, Twilio has direct arrangements with the major carriers, so registered and compliant traffic tends to deliver reliably.

Where Twilio bites

  • A2P 10DLC paperwork up frontBefore a single text goes out to a US number, your business brand and each campaign must be registered and approved, with sample messages and opt-in evidence.
  • Toll-free verification is slowA toll-free number sending any volume of SMS must be verified by the carriers, and the queue currently runs twelve to fourteen weeks with little visibility into progress.
  • Carrier filtering is opaqueMessages can be blocked by a carrier for content reasons without a clear error, and the only way forward is often rewording the template and resubmitting.
  • Invoices are hard to predictPricing combines per-segment message fees, per-destination voice rates, phone number rentals, carrier pass-through surcharges and campaign fees, so a single spike in usage can land as a bill that nobody expected.
  • Verify fraud guard overreachesThe built-in fraud protection sometimes blocks legitimate users on certain carriers, and tuning it requires working through support.
  • Deprecated products hurt customersAutopilot and Programmable Chat were both shut down with migration deadlines that caught teams off guard, and Flex pricing has climbed in ways that make budgeting hard.

Sound familiar?

Common Twilio problems we fix

The Twilio problems that bring people to us, and what you have once each one is fixed.

Error 30034 · not registered

US texts are silently dropped

Traffic is going out through a long code that has never been registered under A2P 10DLC, so the carriers quietly block it at the network edge.

Brand and campaign approved, messages delivering

verification pending 12+ weeks

Toll-free verification is stuck

The submission is sitting in a carrier queue with no reply, or came back rejected for a reason the form did not make obvious.

Submission corrected and tracked through approval

Error 30007 · carrier violation

Carriers are flagging content as spam

A legitimate message template looks like promotional spam to the filters, usually because of shortened links, all-caps words or missing opt-out wording.

Templates reworked to pass filters

bill up 3x month on month

The invoice is unpredictable

International voice destinations, extra phone numbers, Verify attempts and carrier surcharges stacking up where nobody was watching.

Usage auditable and alerts in place

Verify blocked legitimate user

Real customers cannot sign in

Fraud guard is refusing to send one-time codes to certain carriers or regions, and the signup funnel is dropping users without an explanation.

Fraud rules tuned to real traffic

previous developer gone

Nobody knows how the account is wired

TwiML applications, Studio flows, webhooks and credentials that were set up by someone who has left, with no documentation to go on.

Account mapped and back under your control

signature validation failed

Webhooks are being spoofed or rejected

Status callbacks either fail signature checks and get dropped, or no signature is checked at all and anyone can post to the endpoint.

Webhooks signed, verified and monitored

What we do

Twilio help, from one number to the whole account

Call us for one blocked campaign, or hand us the whole Twilio project.

A2P 10DLC and toll-free registration
Brand, campaign and toll-free submissions done properly the first time, including the opt-in evidence carriers now ask for.
Delivery rescue
Messages not arriving, carriers blocking content, or short codes underperforming. We work the error codes back to a root cause.
2FA with Verify
One-time codes built the right way, with sensible fallbacks, rate limiting and fraud rules that do not lock out real customers.
Voice, IVR and Flex
Call flows in TwiML or Studio, contact centre work in Flex, and SIP trunking integrated with your existing phone system.
Cost and usage audits
A line-by-line read of the invoice, with numbers kept, numbers released, and alerts so the next surprise does not happen.
Managed Tech
Ongoing monitoring, template updates and a team to call when a carrier changes the rules again.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Twilio alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Twilio questions

Something else? Call+1 737 727 7327

Why are our Twilio SMS messages not delivering?

For US traffic the most common reason today is A2P 10DLC. If your brand and campaign are not registered and approved, carriers block or heavily throttle the messages, often with error 30034 or an opaque 30007 or 30008. After that we look at content filtering, opt-in records, and whether the right sender type (long code, toll-free or short code) is being used for the volume.

Can you help us register for A2P 10DLC and toll-free verification?

Yes. We handle the brand registration, pick a campaign type that fits your use case, write the sample messages and opt-in description the way the carriers want to see them, and track the submission through to approval. Toll-free verification currently runs twelve to fourteen weeks, so we normally start it in parallel with the rest of the build.

Why is our Twilio bill unpredictable?

Twilio pricing mixes per-segment messaging fees, per-destination voice rates, phone number rentals, carrier surcharges and campaign fees, and some products add usage-based charges on top. We read the invoice back to the account usage, retire anything that is not earning its keep, and put alerts in place so a spike shows up before the month closes.

Can you take over a Twilio project from a previous developer?

Yes, and we do this often. We map the phone numbers, TwiML apps, Studio flows, messaging services, Verify services and webhooks, move ownership and credentials into your names, and document what is actually running so the next person does not start from zero.

How do we build 2FA with Twilio Verify properly?

Use Verify rather than rolling your own code sender, keep attempts rate limited per account and per IP, offer a voice fallback for users whose carrier filters SMS, tune or disable fraud guard rules that block legitimate traffic, and log every attempt so support can see what a stuck user actually experienced.

How much does Twilio help cost?

Estimates are free. Describe what is going wrong or what you are trying to launch and you get a price before any work begins.

Free estimate

Twilio giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.