Send personalized bulk SMS to thousands using dynamic keywords. When someone replies, OTTO fires — qualifying, routing, and collecting structured data without a single human managing the inbox.
Every mass texting platform pushes a message to a list. Only TextingOnly catches what comes back. Your outbound campaign doesn’t end at the send — it converts at the reply.
Create a new list manually. Create the list first, then add contacts.
Create up to 100 lists at once by uploading a CSV.
| List Name ⇅ | Description ⇅ | Last Activity | Actions |
|---|---|---|---|
| Sample List | Just to test. | 11/9/22 12:38 am | Actions ▾ |
The outbound send is phase one. Dynamic keywords make every message feel individual. Segmentation ensures each list gets the right message. 10DLC (10-digit long code) registration ensures it arrives.
On most mass texting platforms, a reply lands in an inbox and waits for a human. On TextingOnly, every reply is an inbound event — identical in structure to a prospect scanning a QR code. OTTO fires. The conversation begins. The contact qualifies themselves.
The key insight: you don’t need two separate campaigns — one outbound for reach and one inbound for qualification. TextingOnly’s outbound send and OTTO‘s inbound automation are the same campaign, two phases. The send finds interested contacts. Their reply starts the qualification. See the full Outbound with Reply Automations use case →
When a reply triggers an OTTO flow, you choose which type runs based on what information you need and how contacts should be routed. Both paths can be chained together.
Sequential intake questions — one field per message. Captures name, address, service type, timeline. Best when the reply signals clear intent and you need structured data to act on it.
Numbered or keyword menu that routes by intent. Best when replies may have different purposes — service type, location, urgency — and you need to segment before qualifying.
Any campaign that expects replies benefits from having OTTO handle them instead of a human inbox. Here’s how each vertical structures the flow.
Every platform sends. The difference is what happens when the contact responds.
| What happens when… | Standard Mass Texting | TextingOnly + OTTO |
|---|---|---|
| A contact replies “YES” | Reply sits in shared inbox. Human reads and responds — eventually. | ✓ OTTO fires Data Collector. Qualification begins in seconds. |
| 200 contacts reply at once | 200 inbox items. Team triages manually. Some never get responses. | ✓ 200 simultaneous OTTO flows. All qualified. All routed. Zero missed. |
| Reply arrives at 9pm | Sits until morning. Lead intent has cooled significantly. | ✓ OTTO engages. Lead record ready for rep at 9am. |
| Contacts have different intents | All go to same inbox. Manual triage required. | ✓ ITR menu routes each contact to the correct path. |
| Data from the reply conversation | Freeform chat log. Manual CRM entry required. | ✓ Structured CRM record at flow completion. Zero manual entry. |
| Attribution for the lead | “Outbound campaign.” No further context. | ✓ Campaign source · reply keyword · ITR path · all Data Collector fields — on the record. |
The outbound send and OTTO’s inbound automation are the same campaign, two phases. Configure the reply flow once — it runs on every send to that campaign.
YES fires the Data Collector. INFO fires an ITR menu. CALL fires a human handoff. Multiple reply keywords route to different OTTO paths from the same bulk send — no manual triage.
A contact who replies but stops mid-conversation still has their reply captured and attributed. Inbound automations handle partial journey recovery.
A reply is the trigger — OTTO fires a Conversational Data Collector or ITR flow configured for that campaign. Sequential questions capture what your workflow needs — name, service type, timeline, address — one field at a time. The completed record feeds directly into your existing process. No manual entry. No inbox.
The most common questions about how outbound bulk SMS works with OTTO’s inbound reply layer.
It converts at the reply. See a chained ITR + Data Collector flow built for your next bulk send — live, in the demo.
Watch a full outbound → reply → OTTO qualification flow run in your native Messages app. Under 60 seconds, no email required.
Try it live →Tell us your list size, vertical, and campaign type. We’ll quote bulk SMS with OTTO reply flows configured for your specific workflow.
Get a quote →We’ll build a chained ITR + Data Collector flow for your next outbound campaign during the demo — mapped to your vertical and use case.
Schedule a call →