Use analytics and reporting to understand customer activity, campaign and playbook results, team workload, and revenue attributed to Hellotext.
This section helps you answer:
- How did a campaign, playbook, or route perform?
- Which actions followed a message, and which customer needs went unmet?
- How were conversations resolved and work distributed?
- Which revenue was attributed to Hellotext?
- Why is data missing or do two reports show different results?
Start with the Dashboard
The Dashboard summarizes the last 14 days, tracked actions, and scheduled or delivered campaigns. Use it to spot a change, then open the detailed report to investigate its source.
Keep reading: Dashboard guide.
Revenue report
The Revenue report shows purchases completed during the selected period, including total revenue and the portion attributed to eligible Hellotext activity.
Use it when you need to compare revenue attributed to AI or classified as team-managed, inspect credited Campaigns and Playbooks, or reconcile individual attributed purchases.
Keep reading: Revenue report guide.
Performance report
The Performance report groups interactions by when they started and shows later recorded conversions and AI escalations.
Use it to review conversion rate, average time to conversion without an AI escalation, escalation rate, and the distribution of interactions with or without an AI escalation.
Keep reading: Performance report guide.
Demand insights
Demand insights summarizes certain ended interactions without a recorded conversion. It shows a count, revenue estimate, and rate; its Affected SKUs card counts distinct associated recommending Playbooks, not products.
Use it to investigate changes in that count and its rate. If you need to review recorded conversions, check the source records separately; for inventory, catalog, or availability problems, inspect product data and conversations.
Keep reading: Demand insights guide.
Campaign reports
Campaign reports help you review delivery, engagement, clicks, conversions, replies, and attributed revenue for a one-time send.
Use campaign reporting when you need to evaluate a campaign, compare message performance, or decide what to improve before the next campaign.
Keep reading: Campaign reporting.
Playbook and route reports
Playbook reporting helps you review always-on workflows, AI agents, and journey routes after they start receiving real customer activity.
Use playbook reporting when you need to compare attributed revenue, conversion behavior, time to conversion, escalation rate, and the handoff quality behind the numbers.
Keep reading: Playbook reporting.
Service quality report
The Service quality report compares AI and team resolution, SLA compliance, unresolved conversations, response-time distribution, and agent performance.
Use it when you need to understand how conversations are being resolved and whether a service problem is concentrated in a channel, team, teammate, AI agent, or resolution path.
Keep reading: Service quality report guide.
Workload & capacity report
The Workload & capacity report compares active load, handled and resolved work, concurrency, assignments, transfers, capacity pressure, session efficiency, and the current operational queue.
Use it when you need to understand how Inbox work is distributed during a period and what needs attention right now.
Keep reading: Workload & capacity report guide.
Attribution
Attribution explains when Hellotext receives credit for a sale and when it does not.
Use attribution guidance when you need to understand source precedence, eligible evidence, attribution windows, team participation, and supported order changes.
Keep reading: Sales attribution.
Tracking data
Reports are stronger when Hellotext receives useful customer activity from your store, site, integrations, or API as signals.
If your store is connected through a supported integration, many events may be tracked automatically. If you have a custom setup, use Hellotext.js or the API to send events.
Keep reading:
Before comparing results
When reviewing performance, check:
- The audience and channel used.
- Whether links and tracking were configured correctly.
- Whether the report is measuring clicks, replies, conversions, or attributed revenue.
- Whether the order contains a recognized external source that takes precedence.
- Whether checkout ownership or path-specific team participation affected the decision.
Before comparing reports, check which date and population each metric uses. In a campaign’s detail report, attributed purchases count on their purchase date; the funnel’s Engaged stage requires both delivery and a tracked link click within the selected period. Recent results can also change while late events arrive or an attribution window remains open. If the numbers do not match, follow Data completeness and reporting gaps before changing tracking.
If you are reviewing your first launch, start with Measure success in your first 7 days.
Related guides
- Measure success in your first 7 days
- Dashboard guide
- Data completeness and reporting gaps
- Revenue report guide
- Performance report guide
- Demand insights guide
- Service quality report guide
- Workload & capacity report guide
- Playbook reporting
- Create a campaign
- Pricing, billing, and plans overview
- Developers and API overview
- Audience and segmentation overview