When to use short codes
- Good fit
- Consider alternatives
- High-volume alerts: Time-sensitive notifications to large audiences
- Two-factor authentication: OTP delivery at scale with high deliverability
- Marketing campaigns: Promotional messages with keyword opt-in (e.g., “Text JOIN to 12345”)
- Voting and polling: Interactive SMS campaigns
- Emergency notifications: Critical alerts requiring maximum throughput
Short code vs. other sender types
| Feature | Short Code | Toll-Free | 10DLC Long Code |
|---|---|---|---|
| Throughput | Up to 1,000 MPS | 20 MPS | Varies by campaign |
| Setup time | 8-12 weeks | 1-2 weeks | Days |
| Cost | Higher (monthly lease + per-message) | Moderate | Lowest |
| Carrier trust | Highest | High | Varies by vetting score |
| MMS support | Yes | Yes | Yes |
| Two-way messaging | Yes (keyword-based) | Yes | Yes |
| Vanity numbers | Available | No | No |
Provisioning process
Request a short code
Navigate to Short Code in Mission Control and submit your request.Choose your type:
| Type | Description | Timeline |
|---|---|---|
| Random | Carrier-assigned number | 8-10 weeks |
| Vanity | Memorable number you choose (e.g., 46835 = “GOULD”) | 10-12 weeks |
Vanity codes are subject to availability. Request early — popular combinations may already be taken.
Complete your application
Provide details about your messaging program:
- Company information — Legal name, address, contact
- Use case description — What messages you’ll send
- Message content samples — Representative examples
- Volume estimates — Expected daily/monthly message volume
- Opt-in flow — How users subscribe (web form, keyword, etc.)
- Opt-out handling — STOP keyword support
- Help response — HELP keyword response content
Carrier certification
Your application is submitted to each major US carrier for review and approval:
| Carrier | Review process |
|---|---|
| AT&T | Reviews content, opt-in flow, and compliance |
| T-Mobile | Reviews content and message flow |
| Verizon | Reviews content and use case |
| US Cellular | Reviews content |
Start messaging
Once approved by all target carriers, your short code appears under your messaging profile. Send messages using the same Messaging API as any other number type.
Sending messages from a short code
Once provisioned, send messages the same way as any other sender type:Short codes use ASCII 7-bit encoding by default (same character limits as GSM-7). See Message Encoding for details.
Automated responses
Short codes must handle standard keywords to pass carrier certification. Telnyx manages these automatically.Required keywords
| Keyword | Purpose | Telnyx handling |
|---|---|---|
| STOP (and UNSUBSCRIBE, END, QUIT, CANCEL) | Opt-out | Automatic — user is blocked from receiving messages |
| HELP (and INFO) | Help/support info | Automatic — sends your configured help message |
| Campaign keyword | Campaign opt-in | Automatic — sends your configured keyword response |
Customizing responses
After carrier certification, you can customize the HELP and campaign keyword responses:Custom HELP response
Custom HELP response
Configure a custom help message that includes:
- Your business name
- What messages the user is subscribed to
- How to get support (phone number or email)
- How to opt out
Custom keyword response
Custom keyword response
When a user texts your campaign keyword (e.g., “JOIN”), they receive a confirmation message.Example:
Disabling automatic responses
Disabling automatic responses
After certification, you can disable automatic responses for HELP and campaign keywords to handle them yourself via webhook. Contact support@telnyx.com to request this change.
Use case examples
Two-factor authentication (2FA)
Two-factor authentication (2FA)
Keyword: N/A (API-triggered)
Flow: User initiates login → your app sends OTP via short code → user enters codeWhy short code: Highest deliverability, fastest delivery, trusted by carriers.
Marketing opt-in campaign
Marketing opt-in campaign
Keyword: JOIN
Flow: User texts JOIN to 12345 → receives welcome message → gets promotional messages
Emergency / mass notifications
Emergency / mass notifications
Keyword: ALERT
Flow: User opts in → receives critical alerts (weather, school closings, etc.)Why short code: Maximum throughput (1,000 MPS) for time-critical mass notifications.
Carrier certification requirements
| Requirement | Details |
|---|---|
| Opt-in mechanism | Clear, documented method for users to subscribe (web form, keyword, paper form) |
| Opt-in disclosure | Users must know what they’re subscribing to, message frequency, and that rates may apply |
| Opt-out support | Must honor STOP and similar keywords immediately |
| Help support | Must respond to HELP with business name, support contact, and opt-out instructions |
| Message frequency | Must disclose expected message frequency at opt-in |
| Content compliance | Message content must match the registered use case |
| Privacy policy | Published privacy policy covering SMS data collection |
| Terms of service | Published terms covering messaging program |