Accessing & Understanding Reports:
Measure Your
Messaging Performance
TextingOnly’s reports show where leads come from, where they drop off, which campaigns drove replies, and which entry points convert best. This is where you prove ROI — and find what to optimize next.
Reports are where the platform’s activity becomes business data. Every SmartLink tap, QR scan, OTTO conversation, and campaign send generates reportable events — organized by report type so you can answer specific questions quickly.
Report Types
Shows each contact who entered a collector — how many started, how many completed each step, how many qualified. Where people drop off reveals friction in your OTTO flow.
Delivery rate, reply rate, opt-out rate per campaign. Which contacts replied YES, which replied STOP, which never responded. Used to build re-engagement segments.
Step-by-step funnel visualization — how many entered Step 1, how many reached Step 2, where drop-off happens. Shows exactly where to simplify your collector flow.
Per-SmartLink and per-QR code breakdown — which placements drive the most opt-ins and highest-quality leads. Informs where to invest more vs. less.
Accessing Reports
Agency Reporting
For agency accounts, reports are scoped to the active subgroup. Switch subgroups to view each client’s data separately. Use the CSV export to build client-facing reports — delivery rates, lead volume, qualified lead count, and entry point attribution all available per subgroup.
Reports answer the only question clients actually care about: “How many leads did this generate, where did they come from, and what did they cost?”
How QR-to-SMS attribution closes the gap between offline spend and reportable lead data — what you can’t see in GA4 that TextingOnly shows you.
Read the Insight →The step-by-step funnel view — where contacts drop off, what to simplify, and how to raise your collector completion rate.
Read the KB Article →How agencies use TextingOnly to manage SMS marketing across multiple client accounts — separate subgroups, isolated reporting, and per-client billing.
Read the Use Case →