Every mass text platform handles outbound sends. The difference is what happens when someone replies. On a standard platform, a reply lands in an inbox — someone on your team has to read it, figure out the intent, and respond manually. At scale, across hundreds of replies from a single campaign, that’s a significant human capital cost with inconsistent results.
TextingOnly treats the reply differently. When a contact responds to your outbound send, that reply is treated as an inbound event — identical in structure to a prospect scanning a QR code or tapping a SmartLink. OTTO fires. The conversation begins. The contact self-qualifies without a human typing a single word.
The key insight: you don’t need two separate campaigns — one for outbound reach and one for inbound 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.
When a reply triggers an OTTO flow, you choose which type of automation fires based on what information you need from the contact and how they should be routed. Two core paths are available, and both can be chained.
Conversational Data Collector
Sequential intake questions — one field per message. Collects specific data points needed to qualify the lead or fulfil the offer. Best when the reply signals clear intent and you need structured information to act on it.
ITR Text Attendant
Numbered or keyword menu that routes the contact based on their choice. Best when replies may have different intents and you need to segment before qualifying — service type, location, interest level, or customer status.
The most powerful configuration chains the two paths: an ITR menu routes the contact by intent first, then a Data Collector picks up the right intake questions for that specific route. The contact gets a conversation that feels tailored to exactly what they said — because it is.
Dynamic Bulk Message
Personalised by first name and last vehicle. Reply CTA triggers OTTO on response.
Route by Intent
ITR menu routes contact to New Vehicle, Service, or Trade-In path.
Collect for That Route
Data Collector asks the right questions for the chosen path — different fields per route.
Rep Notified
Correct sales rep receives structured lead with route, name, interest, and timeline.
The reply-triggered automation pattern applies across verticals — any campaign that expects replies benefits from having OTTO handle them instead of a human inbox. Here’s how each vertical typically structures the flow.
Re-engagement Campaign
Send: “Hi {{first_name}}, your annual {{service_type}} check is due. Reply YES to schedule or CALL to speak with someone.”
Service Reminder + Upsell
Send: “Hi {{first_name}}, your {{vehicle_year}} {{vehicle_model}} is due for service. Reply S to schedule, U to see upgrade offers, or I to get insurance quote.”
Listing Alert + Lead Capture
Send: “New listing in {{neighbourhood}} — {{bedrooms}} bed, {{price}}. Interested? Reply YES for details or TOUR to book a showing.”
Client Campaign — Any Vertical
Build once, deploy across clients. Design the ITR + Data Collector chain for a vertical once. Clone it across agency clients in the same vertical. Each client gets their own sub-account, phone numbers, and OTTO configuration — you manage from one dashboard.
Build Your OTTO Flow Before the Send
Choose your automation path — Data Collector, ITR, or chained. Define every message, every field collected, and every handoff trigger. The OTTO flow design happens before the outbound campaign is written, not after.
Craft the Outbound Message With a Reply CTA
Write your bulk send using dynamic keywords. Include a clear reply instruction that matches your OTTO flow — “Reply YES,” “Reply 1, 2, or 3,” or “Reply with your zip code.” The reply CTA should feel natural, not mechanical. The contact should know exactly what to do and why it benefits them.
Attach the OTTO Flow as the Reply Handler
In TextingOnly, connect the OTTO automation to the outbound campaign. Configure which reply keywords trigger which flow. “YES” fires the Data Collector. “CALL” fires a human handoff notification. Any other reply can fire a default flow or a clarification prompt. Multiple triggers can route to different paths from the same campaign.
Configure Rep Notifications and CRM Routing
Set the conditions that trigger a human — flow completion, high-value keyword, explicit request. Map OTTO’s collected fields to your CRM fields so every completed flow creates a structured lead record automatically. Configure which rep or team receives each type of lead based on the routing logic in your ITR or Data Collector.
Track Reply Rate, Flow Completion, and Lead Quality
Monitor reply rate as a leading indicator of send relevance. Track OTTO flow completion rate to identify where contacts drop off. Compare lead quality from reply-triggered flows against your cold inbound leads — reply contacts have already engaged with your brand, making them warmer at the point of qualification.
| What Happens When… | Standard Mass Texting Platform | TextingOnly + OTTO |
|---|---|---|
| A contact replies “YES” | Reply sits in shared inbox. Human reads and responds — eventually. | OTTO fires Data Collector immediately. 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 immediately. Lead record ready for rep at 9am. |
| Contact replies with a question | Human reads, interprets, responds. Variable quality and speed. | Keyword routing sends to appropriate OTTO path or escalates to human. |
| Different contacts have different intents | All go to same inbox. Manual triage required. | ITR menu routes each contact to the correct path automatically. |
| Data from the reply conversation | Freeform chat log. Manual CRM entry required. | Structured CRM record created at flow completion. Zero manual entry. |
| Attribution for the lead | Source is “outbound campaign.” No further context. | Campaign source, reply keyword, ITR path, Data Collector fields — all on the record. |
Your Bulk Send Just Got an Inbound Layer
Every mass texting platform can push a message to a list. Only TextingOnly catches what comes back. The reply is the moment of highest intent — the contact just told you they’re interested. Leaving that moment to a human inbox is the most expensive thing most SMS campaigns do.
OTTO handles every reply, at any volume, at any hour — routing by intent, collecting the right data for each path, and delivering a structured lead record to the right person before the moment cools. Your outbound campaign doesn’t end at the send. It converts at the reply.
Book a demo and we’ll build a chained ITR + Data Collector flow for your next outbound campaign live.