Platform
Historical reports
CONTACT.WORK historical reporting includes about thirty prebuilt reports on your queues and your people. They show what share of calls were lost, how long customers waited for an answer, how much each agent works, and how inquiries end. You can break the numbers down by hour or day, tie them to form fields, and download them as a spreadsheet. Your BI system can pull them through the API.
Received8 412callsAnswered7 90594%Missed5076%Within 20 sec81%normalReports
What the reports track
Report types
What the reports tell you
Reports are grouped by the questions managers ask: do we have enough people, how is each agent doing, how did inquiries end, how are partners handling calls, and what did customers resolve on their own.
Load and losses by queue
The group report shows how many calls entered the queue, how many were routed to agents and answered, and how many went unanswered, were transferred, or called back again. Next to that are average and maximum wait time, average talk time, and the share of fast answers. Separate reports break calls down by the number customers dialed, by call type, and by direction.
- Lost and repeat calls
- Wait time in queue
- Breakdown by number
Received1 140callsRepeat calls96called againWait0:38on averagePeak4:12at 11:20 AMEach agent's workload and results
The agent summary shows, for each person, inbound and missed calls, outbound calls answered and unanswered, transfers, average calls per hour, talk time, and total time in the system. The status log shows how long each agent was on the line, at lunch, or in training. The login report shows when they signed in and out, and another report shows when customers asked to be connected to that agent specifically.
- Calls per hour
- Time in statuses
- System logins
Anna214 in3:42Mike188 in4:15Emily97 intraining 6 hrsSteve251 inoverloadedForms, QA, and customer ratings
Agents' form answers roll up into one report, and calls without a form go into a separate list. The QA log shows the agent's entries next to the reviewer's comments. NPS surveys show how customers rate the call, and lost-deal reasons show why an inquiry didn't end in a purchase.
- Form answers
- Reviewer comments
- NPS scores
Call forms7,610 completed97%No form236 callsto reviewControl18 flagsthis weekNPS62from surveysDistribution and results at partners
If calls go to partners or branches, reports show how many each one received compared with its target share, how those calls ended, and where the customer was turned away – broken down by region. You see which partners handle the flow best and who should get more.
- Each partner's share
- Outcomes of passed calls
- Lost deals by region
North412 callstarget 40%South355 callstarget 35%Summarymeeting set61%Canceledout of stockMidwest regionWhat got resolved without agents
IVR reports show which menu options callers choose and where the call went next. Requested callbacks and their outcomes are shown separately, and for the voice assistant you see what customers ask and how each conversation ended.
- IVR option choices
- Requested callbacks
- Questions to the assistant
Option 1order status46%Option 2payment21%Callback84 ordered79 doneAssistanttop questiondelivery timesEach role sees only the reports it has access to.
How it works
How historical reporting works
Filters
How you pick the data
At the top you choose a report, then the period: day, week, month, year, or custom dates. Each report has its own filters: people, queues, direction, and call type. Results appear as a table or a chart, and it's easy to compare two periods – for example, this week and last week.
- Five period types
- Table or chart
- Compare two periods
Periodweek27.10-02.11Viewby hourselectedQueuesSales, Support2Staffall14Export
Where the numbers go
Get an Excel spreadsheet with one click, and have the reports you need emailed on a schedule – say, every Monday. If your company pulls numbers into its own BI system, it gets the data through the API, with no manual exports.
- One-click Excel
- Scheduled email
- BI integration
Exceldownload1 clickBIvia APIon requestRows14employeesPeriodOctoberdoneAccess
Who sees the reports
The role decides which reports are open: administrators see everything, supervisors see their own groups, and the QA team sees forms and call reviews. Test accounts and internal staff are excluded from the numbers.
- Reports by role
- Own groups
- No test accounts
Administratorall reports30+Supervisorown groups12QAforms and calls6Test accountsin reportsnoneLaunch
How we set up reporting
- 01GoalsTogether with your leadership, we pick the numbers to check daily and the ones that only need a monthly look.
- 02RolesWe set who can access which reports: administrators, supervisors, the QA team.
- 03StatusesWe create agent statuses – lunch, training, order processing – so time in each is counted separately.
- 04FormsWe link reports to forms so you can see inquiry topics, lost-deal reasons, and ad channels.
- 05ValidationWe check the first reports against the call log and make sure the numbers match exactly.
- 06TrainingWe show managers how to choose a report, period, and filters, and save the result to Excel.
Comparison
Manual spreadsheets vs. platform reports
| Platform reports | Manual spreadsheets | |
|---|---|---|
| Data collection | Built automatically | Exports from different systems |
| Freshness | As of the moment you open it | As of the day you built it |
| Breakdowns | Hours, queues, people, topics | As many as you had time for |
| Errors | No manual copying | Creep in during copying |
| Analyst time | Minutes to pick a filter | Hours every week |
| Form results | Together with calls | Separate from calls |
Requirements
What you'll need
- Access
- Administrator or supervisor role
- Data
- Calls and forms in the platform
- Statuses
- A list of agent statuses
- Export
- Excel or a feed to your analytics
- Where to view
- A browser, nothing to install
- Price
- Reports are free; setup is billed in hours
Preparation
What to decide up front
Q&A
Frequently asked questions
How are historical reports different from monitoring?
Monitoring shows the current minute: who's busy and which calls are waiting. Historical reports sum things up – for yesterday, a week, or a quarter.
Which reports are included?
About thirty: on queues and numbers, agents, their statuses and logins, call types, forms, QA reviews and NPS, partners and branches, callbacks, IVR transfers, and the voice assistant.
How is service level calculated?
It's the share of calls answered within the target time. In the platform's report, the target is 20 seconds, and the share is calculated per hour, per day, or for the whole period.
Can I see reports by hour?
A report can be split by hour or day, or give a single total – that's how you see when you're short on agents.
Are chats included?
For written channels, there are reports on message volume by channel, time to first reply, conversation outcomes, and customer ratings.
Is there a report for the auto dialer?
For each campaign, you see who was reached, and for each number on the list – the call outcome.
Can I export the data?
Every report can be saved to Excel, and we provide data for your BI system through the API.
Can I get reports by email?
Selected reports arrive by email on a schedule: every day, every Monday, or at the start of the month.
Can I build my own report?
We build reports for your forms and business needs as custom development.
How do I calculate revenue lost to missed calls?
Take the number of unanswered calls for the month from the report and subtract the callers who later got through on their own or were called back. Multiply what's left by your typical share of calls that end in a purchase and by your average order value – that's your lost revenue.
How much does historical reporting cost?
Reports are free – they're built into the platform. You pay only for setting them up and customizing them, billed in support hours.
Glossary
Terms on this page
- BI system
- A system that brings data from different apps together in shared reports. Learn more →
- IVR (interactive voice response)
- A phone menu: the caller hears a greeting and picks the right department. Learn more →
- API (application programming interface)
- The way programs exchange data with each other without a person in the loop. Learn more →
- Net Promoter Score (NPS)
- How willing customers are to recommend your company – based on one question rated 0 to 10. Learn more →
- Callback
- The customer doesn't wait on hold but asks for a callback – and gets one when an agent is free. Learn more →
- Supervisor
- Leads a team of agents: watches the queue and quality, helps and coaches. Learn more →
- Service level (SL)
- The share of calls answered within a set time – for example, 80% in 20 seconds. Learn more →
- Abandonment rate
- How many callers hang up before an agent answers. Learn more →
- Omnichannel customer service
- All channels in one agent workspace, with the customer's full history alongside. Learn more →
Updated: