Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Our Twilio bill jumped and I do not know why

Short answer

Start with the usage records by category and day. Twilio charges for each SMS segment sent or received, and a message longer than 160 GSM-7 or 70 UCS-2 characters splits into several. Retry loops, unregistered US traffic and international calls are other documented causes. Set a usage trigger so you hear about the next spike.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • This month's Twilio charge is far above the usual.
  • Message count looks normal but cost does not.
  • One day shows a large spike.
  • Customers are receiving the same message more than once.
  • Nobody knows which app or team is using the account.

Why does this happen?

  1. Long messages count as several

    Twilio charges for each segment sent or received. A body above 160 GSM-7 characters, or 70 UCS-2 characters, is split into segments. Which encoding applies depends on the characters in the text, so a template change can change the segment count.

  2. A loop sends the same message again and again

    A retry that does not stop, or a callback that triggers a new send, can multiply messages. Twilio notes that status callbacks can come more than once for a usage trigger, so your handler must cope with repeats.

  3. US traffic is not registered

    Twilio says customers who send from a US 10DLC number without registering receive additional carrier fees.

  4. International calls or messages were enabled

    Twilio notes international calling needs permission in the console's Global Permissions settings. If it was turned on for a test, traffic to far destinations could follow.

  5. Abuse of an open sign-up or code form

    A public form that sends a text code to any number can be used by bots to send thousands of messages. This is a design weakness, not a Twilio setting.

What can I do about it today?

  1. Look at usage by category and by dayFind the day it jumped and which category: SMS, voice, phone numbers, lookups.
  2. Open the message log for that dayAre there many messages to the same few numbers, or to countries you do not serve?
  3. Do not close the account in a panicClosing it can cut real customers off. Ask whoever runs the app to pause the specific sender first.
  4. Ask what changed that weekA new feature, a new campaign, a longer template, a deployment.
  5. Set a usage triggerTwilio lets you set a trigger on a usage category that notifies your app when it passes a threshold, so a spike is seen the same day.

When should I bring someone in?

  • You see bursts to numbers that are not your customers.
  • A code-sending form is public and has no limit.
  • You cannot tell which app owns the traffic.

How do I handle it?

  1. Break the bill downI read the usage records by category and day, then match the spike to deployments and templates.
  2. Trace the send to its triggerI find which code path sent the extra messages: a loop, a retry, a public form.
  3. Add limits at the sourceI add rate limits per number and per visitor, a block on destinations you do not serve and a cooldown on repeat sends.
  4. Shorten and simplify messagesI check templates for segment count and encoding, so one text stays one segment where possible.
  5. Set alerts and a named ownerA usage trigger or a daily check warns a named person, and the account's owner is recorded.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Why did a small wording change raise the cost?

Twilio documents different limits for each encoding: 160 characters for GSM-7 and 70 for UCS-2. A text in the shorter-limit encoding needs more segments for the same length.

Can Twilio warn me about a spike?

Twilio documents usage triggers, which notify your application when usage crosses a threshold you set.

Will Twilio refund unexpected charges?

That is Twilio's decision. Gather the usage records and ask their support, but do not rely on it.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.