Have a Question?
The Collector &Messaging Framework
The Collector &
Messaging Framework:
How Every OTTO Flow Is Built
Every collector type in TextingOnly — from a simple list opt-in to a branching multilingual ITR — follows the same five-stage framework. Understanding the framework once means you understand every collector type. This article is the foundation for all collector-specific guides.
TextingOnly offers ten collector types — each designed for a different interaction pattern, data capture goal, and audience. All ten share the same five-stage messaging framework. Learn it once here, then go deeper in the collector-specific article for your use case.
The Ten Collector Types
Linear question sequence — OTTO asks Q1, waits, asks Q2, repeats. Free-text replies. Best for: simple lead qualification, service intake, basic data capture.
Same as Custom Questions with language detection — OTTO switches to Spanish (or other language) when detected, delivers English lead data. Best for: bilingual markets.
Custom Questions with a mandatory name-capture step built in as the first question. Best for: events, personalized follow-up, any scenario where the contact name is required.
Name capture + language detection combined. Best for: bilingual intake where contact identity is required for follow-up.
Numbered menu — contacts reply with a number to navigate branches. Text-based or MMS image menu. Best for: routing (Sales/Service/Support), structured qualification, graphical brand experiences.
ITR menus with language detection — Spanish contacts navigate a parallel Spanish menu. English lead data delivered to team. Best for: high-volume bilingual markets.
Simple opt-in — contact texts in, receives TCPA confirmation + email capture prompt. No qualification. Best for: email list building from SMS entry points.
Simple opt-in to a list. Contact receives compliance message. Added to associated list immediately. Best for: coupon programs, promotional opt-ins, outbound audience building.
Captures both list membership and email address in one flow. Best for: omnichannel list building where you want SMS + email from the same opt-in.
The Five-Stage Messaging Framework
Every collector — regardless of type — follows these five stages in sequence. The complexity and branching within each stage varies by type. The order never changes.
Stage 1 — Entry Point
The contact encounters your SmartLink or QR code on any surface — website button, social bio, email CTA, direct mail QR, signage, table tent, Google Business listing. They tap or scan.
On mobile, the native SMS app opens immediately with a pre-filled message. On desktop, a QR bridge appears so the contact can scan with their phone. No form. No app download. No account creation.
An optional interstitial page can sit between the tap and the SMS app opening — displaying your offer, language selection buttons, or intent routing options before the contact sends the first text. See the Interstitial Pages articles for setup.
Stage 2 — Pre-Filled CTA Message
The SMS app opens with a pre-configured message already in the compose field. The contact sees it and taps Send — no typing required. This single tap is the opt-in event:
Carrier-verified at the moment of send. Not self-reported. Not typed. The number that sent the text is the number on record.
Timestamp, entry point name, and phone number are recorded automatically. This is your documented consent record.
Which SmartLink or QR code triggered the opt-in is tagged to the contact record. Campaign source is captured at this moment.
City, region, and timezone are logged from the device’s carrier data at the moment the message is sent.
The pre-filled message text is configured in the collector settings. For standard collectors it’s a simple keyword or phrase (“CTA” or “GET COUPON”). For coupon or offer flows, it can reference the specific offer (“GET MY 20% OFF”). The text itself isn’t the data — the send event is.
Stage 3 — Initial Message & Menu Options
The moment the contact taps Send, OTTO responds with the first configured message. This is where the collector types diverge most significantly:
For all ITR types, the initial message can include an optional MMS header image — a branded logo or banner that appears above the text menu — without being a full graphical menu. This adds brand presence while keeping the navigation text-based.
Stage 4 — User Navigation & Path Routing
For Custom Questions collectors, Stage 4 is straightforward — the contact replies to each question in sequence. OTTO moves to the next question on each reply.
For ITR collectors, Stage 4 is where branching happens:
Typing “MENU” (case-insensitive) in any ITR conversation returns the contact to the main menu. This is a native TextingOnly ITR behavior — no configuration required. Contacts who get lost in a branch can always find their way back.
Stage 5 — Final Message
When a contact reaches the end of a flow — completes all questions, reaches a terminal ITR branch, or completes the signup — OTTO fires the configured Final Message. This is fully customizable per use case and per branch:
“[Rep name] will call from (410) 555-0100 within the hour — save the number.” Sets contact expectation for the warm callback, dramatically increasing answer rate.
The coupon image is delivered via MMS as the Final Message. No link to click. No app to open. The coupon arrives in the SMS thread immediately.
“You’re all set — your appointment is confirmed for Thursday at 2pm.” Or a reference number, a next steps summary, a link to a specific resource.
“Thanks for joining! You’ll receive updates from [Business]. Reply STOP at any time to unsubscribe.” TCPA-compliant, adds contact to list.
Simultaneously with the Final Message firing to the contact, TextingOnly sends the configured email lead alert to your team — with the contact’s phone number, name (if captured), all qualification data, conversation transcript, and entry point source.
Partial Completions — Nothing Is Lost
A contact who opts in but doesn’t complete the full flow is not a lost lead. Every stage they reach is logged:
Partial contacts appear in the Viewing Leads report segmented by engagement stage. They can be exported and added to a targeted outbound re-engagement campaign — a “nudge” send asking if they’re still interested, handled automatically by OTTO on the reply end.
Linear question sequences, name capture, free-text reply handling — the most common collector type for lead gen.
Read the Article →Numbered menus, branch routing, MENU navigation, MMS image menus, graphical brand experiences.
Read the Article →No qualification flow — opt-in, compliance message, list building, outbound audience creation.
Read the Article →