Python Twilio SMS — Core Concepts

Why this matters in production

SMS has a 98% open rate compared to roughly 20% for email. For critical notifications — two-factor authentication codes, appointment reminders, fraud alerts, delivery updates — SMS is often the most reliable channel. Twilio makes it accessible from Python without needing telecom infrastructure or carrier relationships.

Over 10 million developers use Twilio, and companies like Uber, Airbnb, and Stripe rely on it for transactional messaging. Understanding how it works helps you build reliable notification systems that reach users regardless of whether they check their email.

How Twilio SMS works

The request flow

When your Python script sends an SMS through Twilio, this is the actual chain of events:

1. Your script makes an HTTPS POST request to Twilio’s REST API with the message details.
2. Twilio validates your credentials (Account SID and Auth Token).
3. Twilio routes the message to the appropriate carrier network based on the recipient’s phone number.
4. The carrier delivers the message to the handset.
5. Twilio receives a delivery status callback and updates the message record.

The Python SDK (twilio package) wraps this API call in a clean interface, but underneath it is a standard HTTP request.

Phone numbers

You need at least one Twilio phone number to send from. These are real phone numbers that Twilio provisions from carrier inventories. You can get local numbers (for specific area codes), toll-free numbers, or short codes (5-6 digit numbers used for high-volume messaging like marketing campaigns).

The type of number affects deliverability and cost:

• Local numbers — Best for transactional messages. Carriers trust them for moderate volume.
• Toll-free numbers — Good for higher volume. Require verification with carriers.
• Short codes — Designed for mass messaging. Expensive ($1,000+/month) but highest throughput and deliverability.

Messaging services

Instead of sending from a single number, Twilio offers Messaging Services — a pool of phone numbers that Twilio rotates through automatically. This prevents any single number from hitting carrier rate limits and improves deliverability for high-volume sending.

Key concepts

Delivery status

SMS is not fire-and-forget. Each message passes through several states:

• queued — Twilio accepted the request
• sent — Twilio passed the message to the carrier
• delivered — The carrier confirmed delivery to the handset
• undelivered — Delivery failed (invalid number, carrier rejection, phone off)
• failed — Twilio could not send the message (bad parameters, insufficient funds)

You can track status via webhooks (Twilio calls your URL with updates) or by polling the message resource.

Cost structure

Twilio charges per message segment. A standard SMS is 160 characters. Longer messages are split into segments:

• 1-160 characters → 1 segment
• 161-320 characters → 2 segments
• Each additional 153 characters → 1 more segment (due to multipart headers)

In the US, outbound SMS costs roughly $0.0079 per segment. International rates vary significantly — sending to some countries costs over $0.10 per segment. Always check the pricing page for your target countries.

10DLC registration (US)

Since 2023, US carriers require 10DLC (10-Digit Long Code) registration for application-to-person messaging. You must register your brand and messaging campaign with Twilio, which submits it to The Campaign Registry. Without registration, your messages will be filtered or blocked.

This is not optional. It applies to all businesses sending SMS to US numbers from local phone numbers.

Common misconception

Many developers assume SMS delivery is instant and guaranteed. In reality, carriers can delay messages during high-traffic periods, and some carriers aggressively filter messages they suspect are spam. A “sent” status from Twilio does not mean the recipient has received the message — only “delivered” confirms that.

Practical workflow

A typical integration in a Python application:

1. Store Twilio credentials (Account SID, Auth Token) in environment variables.
2. Provision a phone number or set up a Messaging Service in the Twilio console.
3. Install the twilio Python package.
4. Create a client, build the message, and send it.
5. Optionally set up a webhook endpoint to receive delivery status updates.
6. Log all message SIDs for auditing and debugging.

For reliability, queue SMS sending through a task queue (like Celery) rather than sending synchronously in your web request handler. This prevents slow Twilio API calls from blocking your user-facing responses.

The one thing to remember: Twilio converts a simple API call into carrier-grade SMS delivery — but production reliability requires understanding delivery states, carrier registration, and message segmentation costs.