The IVR → ITR analogy
When a business sets up a new phone number, they face a simple choice: do you want a live person to answer every call, or an automated menu (IVR) to route callers to the right department? Most businesses choose the IVR — live answering requires constant staffing, and the menu can route by intent before a rep ever picks up.
The same choice exists for a text channel. Live answer = 1:1 text messaging. Requires staffing, monitoring, response time management. Automated menu = Interactive Text Response (ITR). Routes automatically, collects data per department, reports on every interaction — without staffing the first touch.
Live answer vs automated ITR menu
The decision framework for a text channel mirrors the phone-system decision exactly — you’re choosing the same trade-offs.
How TextingOnly’s ITR works
The Interactive Text Response menu is the core of inbound SMS automation. It works exactly like an IVR call flow — but in a text conversation. Each department branch can have its own questions, self-service options, and routing logic.
Per-branch data collection
This is what separates ITR from a basic “text us” auto-reply: every branch of the menu can have its own intake questions. Same engine, different conversations tuned to what each department actually needs to capture.
Sales branch
Vehicle interest, budget range, trade-in, financing preference, timeline. Routes to the right salesperson with full context.
Service branch
Issue type, urgency level, account info, preferred appointment window. Pre-qualifies the service ticket before the rep calls.
Support branch
Account ID, product category, issue description, priority. Triages support requests before they hit the queue.
Language branch
Spanish, French, or any supported language activated at the first reply. Full Language Funnel runs in the customer’s language.
Data and reporting
TextingOnly’s reporting separates a real ITR channel from a basic “text us” button. Every interaction is tracked and organized into actionable insights — not just completed conversations, but partial engagements, menu selections, and department-level performance.
Engagement: who entered the menu, which option they selected, how far they progressed — tracked per contact, per campaign, per department.
Partial engagement: contacts who started but didn’t complete are flagged with the data already captured — available for nudge campaigns and remarketing.
Per-department performance: reply rates by branch, completion rates per intake flow, lead quality scoring across departments.
TextingOnly creates mobile links and QR codes automatically in the dashboard. Building an ITR menu with branches, per-department intake, and routing logic takes minutes — less than configuring a typical IVR.