Have a Question?
Text Menus, MMS Headers,and Graphical Image Menus
ITR Collector:
Text Menus, MMS Headers,
and Graphical Image Menus
The ITR (Interactive Text Response) collector is TextingOnly’s most versatile flow type — supporting text-based numbered menus, branded MMS header images, and fully graphical MMS image menus where the image itself is the menu. One collector type, three visual formats.
Before building an ITR collector, read The Collector & Messaging Framework to understand the five-stage architecture all collectors share. This article covers Stage 3 (Initial Message), Stage 4 (Navigation), and the visual format options specific to ITR.
The Three ITR Visual Formats
Format 1 — Text Menu
The standard ITR format. OTTO sends a plain-text message containing the numbered menu options. The contact replies with a number. Simple, universal, works on every phone.
OTTO sends:
“Welcome to [Business]! How can we help?
1 · Sales
2 · Service
3 · Support
Reply a number or type MENU anytime to return.”
Contact replies: 2
OTTO routes to the Service branch and sends the first configured Service question or content.
Text menus support up to the number of branches you configure. Best practice is 2–4 options at the main menu level. More than 4 options increases decision friction and drop-off. Sub-menus within branches can add depth without overwhelming the first prompt.
Format 2 — MMS Header + Text Menu
An optional branded image (logo, banner, product photo) appears above the text menu in the same MMS message. The contact still navigates by replying with a number — the image adds brand presence without changing the mechanic.
Use an MMS header when brand recognition matters at first contact — automotive dealerships, retail, restaurants, franchise businesses. The logo in the first message signals legitimacy before the contact reads the menu options. Keep the image under 600KB and sized around 600×400px for consistent carrier delivery.
Format 3 — MMS Image Menu
The most visually distinctive ITR format. The menu IS the image — a fully branded graphic that displays all the options, numbers, and any accompanying content (player rosters, vehicle models, event schedules, product lines). The contact reads the image and replies with a number corresponding to their selection. OTTO delivers the matching content.
A branded image showing vehicle model names and numbers: “1 · SUV 2 · Large Sedan 3 · Mid-Size SUV 4 · Hybrids…” Contact replies with a number, OTTO delivers that vehicle’s details, pricing link, or routes to a sales rep for that model type.
A branded roster image with player numbers and names. Contact replies with a player’s jersey number, OTTO delivers that player’s stats, bio, or sponsor message. The jersey number IS the navigation number — no separate numbering needed.
A branded menu image showing numbered specials or categories. Contact selects a number, OTTO delivers the item details, coupon, or routes to online ordering. The image handles the presentation — OTTO handles the response.
A branded image co-featuring the sponsor and the organization (team, venue, school). The image delivers brand exposure; the numbered reply triggers sponsor-specific content or offers. Sponsor attribution is built into the image itself.
The image contains the options and their corresponding numbers. The contact reads the image, decides their selection, and texts back the number. OTTO reads the numeric reply and delivers the corresponding configured content — just as it would for a text menu. The image is the visual presentation layer. The reply mechanic is identical to text ITR.
Stage 4 — Navigation & Branching
ITR navigation is the most configurable part of the ITR collector. Every branch can have independent content, sub-menus, questions, final messages, and email alert recipients.
Number Reply Routing
When a contact replies with a number, OTTO matches it to the configured branch and delivers that branch’s first response. If the contact replies with a number not in the menu, OTTO sends a configured error message and re-presents the menu.
MENU Keyword — Return to Main Menu
At any point in any ITR conversation — mid-branch, mid-sub-menu, anywhere — a contact can type MENU (case-insensitive) and OTTO returns them to the main menu. This is native behavior, always active, requires no configuration. It prevents contacts from getting stuck in a branch they didn’t intend to select.
Branch Depth
Branches can be flat (main menu → immediate Final Message) or deep (main menu → sub-menu → questions → Final Message). Each level is configured independently. Complex businesses — automotive groups with Sales/Finance/Service/Parts — can build multi-level ITR flows with appropriate depth per branch.
Branch-Level Email Routing
Each branch in an ITR collector can have its own notification email address. Sales branch alerts go to the sales team. Service branch alerts go to the service department. The contact’s selection does the routing — your team never touches an unqualified lead.
Stage 5 — Final Message per Branch
Each terminal branch in an ITR flow has its own configurable Final Message. A Sales branch might end with a Prepare Caller message. A Coupon branch might end with an MMS coupon image. A Support branch might end with a confirmation number and next steps. Each contact gets the Final Message appropriate to the branch they selected — not a one-size-fits-all closing.
Setting Up an ITR Collector
Why ITR outperforms IVR — visual menus, async navigation, written data record, and no hold queues. The case for moving routing to SMS.
Read the Insight →How to modify an existing ITR collector — update menu text, add branches, change Final Messages, and adjust email routing without rebuilding from scratch.
Read the KB Article →How automotive dealers use ITR menus — text and MMS image — to route buyers and service customers from a single SmartLink deployment.
Read the Playbook →