Dashboard & Reporting
Chats become operating intelligence.
Every visitor is a signal. Names, channels, topics, sentiment scored to the decimal. The machine does the boring work so the people can do the closing.
Live
Updated as chats happen
Per channel
Website, WhatsApp, email
Arabic + English
Counted in one view
Export
Any view, any period
Read the room at scale
Mood moves before revenue does
Customer sentiment is a leading indicator. Revenue is a lagging one. When the line dips on a Tuesday, something broke on Monday, and you see it in time to ask what. Not in next quarter's churn report.
The scoreboard
The share of conversations that end well
One number for how the week actually went, with the negative slice broken out and clickable. Every unhappy conversation is one you can open, read, and answer, rather than a percentage you argue about.
Accountability, not vibes
Which jobs Chatbot.OM nails, and which it does not
If you cannot measure it, you cannot fix it. See where the chatbot answered cleanly, where it handed over, and where it should have. Most businesses guess at this. You get to operate on it.
What you get without asking for it
Six reports that answer the questions you actually have.
Conversation volume
By day, hour, and channel, so you can see the evening peak nobody was staffing.
What people ask about
The topics that come up most, ranked, with the exact wording customers used.
Ticket ages and closures
How long issues stay open, how many missed their promised time, and why.
Lead and pipeline health
New leads, owners, stage movement, and which ones have not been touched in days.
Handover rate
How often the chatbot passed to a human, and whether that number is going the right way.
Exports and scheduled emails
Any view as a file, or a weekly summary that lands in your inbox on Sunday morning.
Everything on the board, nothing in a spreadsheet.
- Live view of conversations across every channel
- Sentiment scored per conversation, trended over time
- Topic clustering built from what customers actually wrote
- Ticket volumes, ages, and on-time closure rates
- Lead counts, owners, stage movement, and aging
- Handover rate and the reasons behind it
- Peak-hour view so you can staff the evenings properly
- Arabic and English conversations counted together
- Per-agent view of who is closing and who is stuck
- Scheduled summaries by email
- Exports for any view and any period
- All reporting data stored inside Oman
Your reporting is your customer data.
Stored and processed inside OmanFAQ
The questions Omani teams ask us most often.
Do we need someone technical to use this?
No. It opens on a summary that answers the three questions most owners have: how many people talked to us, how did they feel, and what is still open. Everything else is one click deeper, and nothing needs to be built first.
How is sentiment measured?
Each conversation is scored on how it actually ended, not on individual words. A customer who starts annoyed and leaves satisfied counts as a good conversation, which is the only reading that is useful to you.
Can we see the actual conversations?
Yes. Every number in the dashboard is clickable down to the conversations behind it, with the full transcript in the language the customer used. No metric is a dead end.
Does Arabic get counted properly?
Yes. Arabic and English conversations are analysed with the same depth and reported in the same view, so your totals are not quietly missing half your customers.
Where is the reporting data held?
Inside Oman, on the same infrastructure as the conversations themselves, in line with the Personal Data Protection Law (Royal Decree 6/2022). Analytics is not shipped to a third-party service abroad.
Your website is quiet. Fix that.
Give us your website and we will have Chatbot.OM reading it today. Your customer data stays inside Oman.
Oman Personal Data Protection Law compliant · Data never leaves the Sultanate