See what customers need and where service slows.
Find the questions that keep coming, and the buyers left waiting.
Conversation topics
Current customer demand
Returns · conversation
“Can I exchange the size if I ordered through WhatsApp?”
Keep every action clear and accountable.
Conversation reporting shows how many messages arrived, where they came from, how long customers waited for a first reply, what they asked about, and how they rated the result. Use those measures to find repeated questions and service gaps.
Message volume by channel and direction
Average first response time over thirty days
Satisfaction scores and conversation quality trends
Inbound volume by weekday and hour
What keeps the work controlled
Volume and response
The basic questions first: how much is arriving, where from, and how long people wait before somebody answers.
- Messages by channel and direction
- Conversations opened per channel
- Average first response time over the last thirty days
- Open conversations that still have unread inbound messages
Satisfaction and quality
Survey answers and model scoring are reported together, so coverage does not depend on how many customers filled something in.
- Satisfaction trend over time
- Resolution, responsiveness, sentiment and quality scores
- Topic classification across conversations
More capabilities
Work the inbox
Reporting is computed from the conversations and messages already in your business. There is no tagging exercise required before numbers appear.
Rollups run on a schedule
Metrics are recomputed for whole time buckets on a short cycle, so a rerun corrects itself instead of double counting.
Read the cuts
Volume by channel and direction, conversations opened, first response time, satisfaction, quality scores, topics and an inbound heatmap.
Act in the same place
A number points at a queue you can filter, a segment you can build or a knowledge gap you can fill, without exporting anything.
Timing and staffing
An inbound heatmap by weekday and hour shows when messages actually arrive, which is the input to a shift pattern.
- Volume by weekday and hour
- Channel mix over time
- Trends over time, cut by channel and campaign
Campaign results
Broadcast counters update as a send progresses, so a campaign in flight can be watched as it goes.
- Delivered, read, clicked and replied counters per broadcast
- Results per variant when you ran a test
- Failure reasons on the recipients that did not receive
Agent and reviewer reporting, Soon
See how much of the conversation volume agents resolved and where review was needed.
- Volume and response time by owner
- Automation share of resolved conversations
- Delivery state breakdowns across channels
Good to know
- Reporting cuts by channel, topic, time and campaign. There is no per person breakdown.
- There is no report of delivered against read against failed.
- There is no revenue attribution report. That needs connected order and payment data.
Questions buyers ask
Is reporting real-time?
The inbox is live. Reporting is recomputed on a short schedule, and broadcast counters update as a send progresses.
Where do the numbers come from?
From your own conversations, messages, scores and events. Nothing is estimated or benchmarked against other businesses.
Can I break results down by agent?
The cuts are by channel, topic, time and campaign. Individual members are not broken out.
How far back does it go?
Rollups are stored by hour and by day, and a daily reconciliation pass rebuilds recent history so corrections show up.
More questions
- Can I export the data?
- Contacts export to CSV. Reporting is read in the business, and outbound webhooks can stream events to your own systems.
- Do broadcast results appear here?
- Broadcast counters live with the campaign so you can watch a send. Volume and conversation metrics live in reporting.
- Is delivery state reported?
- Delivery state is tracked on every message and shown on the campaign that sent it.
- Does reporting cross businesses?
- No. Every number you see is your own business's, and no other business can see it.
- Why are message counts and delivery counts different?
- A message is counted when it is recorded. Delivery state arrives later from the provider and can change, so the two are reported separately.
- Can I compare channels fairly?
- Volume and conversations opened are split by channel, so you can see where customers are contacting you. Response time is measured the same way on every channel.
Answer every customer from one inbox.
Ready to put this to work?
Start with one customer journey and build from there.
7-day free trial. Nothing is charged when you start. Cancel before it ends and pay nothing.