Two-Way SMS & MMS Messaging
Firetell unifies conversational Two-Way SMS/MMS for human agents, autonomous mid-call text follow-ups from Voice AI Agents, and high-throughput programmatic notifications via the REST API—all routed over the same business DID phone numbers as your voice calls.
1. Provisioning & Enabling SMS-Capable Numbers
- Navigate to Console → Phone Numbers → Buy a Phone Number.
- Filter inventory by capability
SMS(andMMSfor picture/document attachments in supported countries like the US & Canada). - Activate your number and open its Phone Number Settings page:
- Assign Inbound SMS Routing to an Agent Team or shared inbox so incoming customer replies alert available agents in real time.
- Configure optional Event Webhooks (
message.received,message.delivered,message.failed) if your CRM or backend also consumes inbound messages.
Regional Carrier Registration Requirements
| Destination / Origin | Carrier Requirement | Best Practice |
|---|---|---|
United States (+1 Local DIDs) | A2P 10DLC Brand & Campaign Registration | Register your EIN/business brand and sample message templates before sending bulk or automated traffic to avoid carrier error filtering. |
US & Canada Toll-Free (+1 800/888/...) | Toll-Free Verification (TFV) | Submit opt-in workflow screenshots so toll-free SMS enjoys high throughput and zero spam blocking. |
Vietnam & APAC (+84, +65, …) | Registered Alphanumeric Brandname / Verified KYC | Complete your Workspace Regulatory Profile and adhere to local anti-spam opt-in windows. |
2. Conversational Messaging in the Agent Workspace
Support and sales reps manage live customer text threads directly inside the Agent Portal (https://{workspace_id}.{regional_domain}):
- Unified Customer Timeline: Every conversation thread links automatically to the customer's E.164 phone number and Workspace Contact profile—showing past voice calls and SMS messages side by side.
- Rich Multimedia (MMS): Send and view image or PDF attachments on MMS-enabled numbers.
- One-Click Voice Escalation: Need to resolve a complex issue faster? Click the Call icon inside the SMS header to dial the customer immediately using your team's outbound Caller ID.
3. Mid-Call SMS from Autonomous Voice AI Agents
Spoken phone calls are poorly suited for reading out long URLs, street addresses, or 12-character booking codes. Combine voice and text seamlessly using Firetell's built-in send_sms tool:
- Open Console → Voice Agents, select your agent, and scroll to Tools / Actions → Built-in System Tools.
- Click Add Tool and enable
send_sms. - Add a clear instruction in your System Instructions:
- Whenever a caller books an appointment or asks for our clinic address/payment link, invoke `send_sms` to text the confirmation details directly to their phone (`{{caller_number}}`) while confirming aloud that you just sent it.
- If the
toparameter is omitted by the model, Firetell automatically sends the text to the active caller's E.164 number and attributes the message to the Voice AI Agent in Messaging Logs.
4. Character Encoding & Segment Billing (GSM-7 vs. UCS-2)
Carrier networks split and bill SMS messages by character encoding segments rather than per API request:
| Encoding Standard | When Used | Single Segment Limit | Multi-Part Segment Size |
|---|---|---|---|
GSM-7 (Standard ASCII) | Plain English text, digits, and standard punctuation (no emojis or diacritics). | 160 characters | 153 characters per segment (7 chars reserved for concatenation header) |
UCS-2 (Unicode) | Contains Vietnamese diacritics (ă, â, đ, ê, ô, ơ, ư), CJK characters, smart quotes (“ ”), or emojis. | 70 characters | 67 characters per segment |
A 155-character plain English message costs 1 SMS segment, whereas adding a single emoji or smart curly quote switches the entire payload to UCS-2—turning it into 3 segments (155 / 67). Keep automated templates concise and avoid typographic curly quotes when GSM-7 suffices.
5. Auditing Delivery & Automating via REST API
- Delivery Diagnostics: Open Messaging Logs (SMS & MMS) under Console → Call Center → Messaging Logs to track status transitions (
queued→sending→sent→delivered/undelivered/failed), verify sender attribution, and debug carrier error codes. - Opt-Out Compliance: Always honor standard customer opt-out keywords (
STOP,UNSUBSCRIBE,CANCEL) to protect your DID sender reputation with upstream carriers. - Programmatic Dispatch: To send transactional OTPs, appointment reminders, or post-call CSAT surveys from your backend, see the Messages REST API.