Set up the Aircall Dashboard by opening Analytics > Overview, fixing the date range, timezone and numbers, then reading call volume on General Performance and missed calls by reason on Inbound. Agent activity depends on your plan: Essentials gives a per-user call table, Professional adds User Activity, and the Analytics+ add-on adds User Activity+.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowTwo counting rules change how you read every chart. A missed inbound call belongs to the number or team, not to one agent, because several people usually ring at once. And a call the AI Voice Agent fully handles is not counted as missed, while one it tried to transfer to a person who never picked up still is.
Which Aircall dashboards does your plan include?
Every Aircall plan includes Overview, Call History, Network Diagnostics and the AI Agents dashboard, and Professional adds Inbound, Outbound, Unanswered Calls and User Activity. The Analytics+ add-on replaces those with “+” versions that add drill-downs, heatmaps and unlimited history. Aircall’s analytics features by plan page sets the limits, and they decide what “agent activity” can mean for you.
| What you want to see | Essentials | Professional | With Analytics+ |
|---|---|---|---|
| Call volume and missed-call share | Overview | Overview and Inbound | Overview+ and Inbound+ |
| Missed calls by reason | Overview, Inbound tab | Unanswered Calls dashboard | Unanswered Calls+, with a weekday-by-hour view |
| Agent activity | Calls by last participant table in Overview | User Activity dashboard | User Activity+, with status time and ringing attempts |
| Whether missed callers were reached later | Your own check from a Call History export | Your own check from a Call History export | Built-in KPI for missed calls without a later connected call |
| History in analytics | Up to 6 months | Up to 6 months | Unlimited |
On the pricing page at the time of writing, Essentials costs $30 and Professional $50 per licence per month on annual billing, both with a three-licence minimum, and Analytics+ is listed at $15 per seat per month. Aircall’s add-on billing page says add-ons are charged on every standard user licence, so Analytics+ on a three-licence account adds $45 a month. You can start a free Analytics+ trial from Discover Analytics+ in the Analytics menu; if you are not the account owner, the owner gets an approval request.
So for the title’s three jobs: call volume and missed calls are covered on every plan; per-agent dashboards need Professional; and the two questions owners ask most, who let the phone ring and which missed callers nobody reached, have built-in answers only with Analytics+. On Essentials you answer them with an export and a spreadsheet, shown further down. For how numbers, seats and call flows fit together, see the tutorial on Aircall numbers, seats and call flows.
How do you set a reproducible reporting window in Aircall Overview?
Sign in as an Admin or Supervisor, open Analytics > Overview and pick a finished period, with the same timezone and numbers ticked every time, so one week's figures can be compared with the next.
- Sign in as an Admin or Supervisor. Overview is limited to those roles, and number or team permissions can hide some lines from you.
- Go to Analytics > Overview. General Performance holds total, inbound and outbound calls; the Inbound tab holds the missed-call share, service level, waiting time and the missed-reason chart.
- Pick a finished period, such as last Monday to Sunday, and compare it with the week before rather than with a part-week.
- Set the timezone your team works in and write it on the report. Every chart and KPI uses it.
- Choose the Date Breakdown (daily, weekly or monthly) and tick every customer-facing number. Deleted numbers can still appear in the filter list, so check what you have ticked.
- Note any extra filter you use on General Performance or Inbound: IVR Branch (the last menu option the caller chose), Call routed to team, SLA (in sec) or Only calls with AI Voice Agent.
Aircall’s Overview documentation also says the dashboard is not real time and points to Live Monitoring for live insight. Treat Overview as the weekly look back and Live Monitoring as the screen for today’s queue. Hover over the ℹ icon beside any KPI before copying it into a spreadsheet: waiting time and service level, for example, measure different intervals.
A bookkeeping practice with an enquiries line and a client-support line shows how reports drift apart. The owner sees 46 missed calls in a week; the coordinator sees 18. Before anyone questions staff, they compare filters: the owner ticked both lines, the coordinator only enquiries. Same data, different question. They agree one filter line and paste it at the top of every weekly report: “Mon to Sun; both customer lines; team timezone; daily breakdown; no team or IVR filter”.
Keep that line inside the report, not in a file name. A PDF export describes the applied filters in text, but a CSV or XLSX export does not explain itself, so whoever opens the spreadsheet next month needs the line to reproduce your numbers.
What does each Aircall missed-call reason tell you to fix?
Each missed-call reason on Aircall's Inbound tab points to a different fix, which is why the single missed-call percentage is the least useful number on the page. The Inbound tab splits missed calls by reason, using the labels in Aircall’s missed, unanswered and abandoned call classifications.
| Reason label | What happened | First thing to check |
|---|---|---|
| Outside of business hours | The call reached the At any other time branch of a Time Rule | Opening hours, the closed message and whether after-hours callers need an AI Voice Agent |
| All agents were not available | Nobody on the route was free: busy, offline or unavailable | Phone cover in that hour and who was logged in |
| Users did not answer | Available agents were rung for more than 10 seconds and nobody picked up, or they rejected it | Ring time, app notifications on each device and coaching |
| Abandoned in IVR | The caller hung up during the menu or its message | Menu length and wording |
| Abandoned before 10 sec | The caller hung up within 10 seconds | The trend over several weeks, not each call |
| Abandoned | The caller hung up during a plain welcome message, before any other step | Welcome message length |
| Callback request | The caller pressed * to ask for a callback instead of waiting (Professional and above) | Whether someone made the callback |
| Handled by AI Voice Agent | The AI dealt with the call fully | Not a miss; check the quality of the answer instead |
Here is the main worked example, with illustrative figures. A print shop’s finished week shows 240 inbound calls: 180 answered by staff, 20 fully handled by the AI Voice Agent and 40 missed, so the missed share is 40 ÷ 240 = 16.7%. Counting the 20 AI-handled calls as missed would give 60 ÷ 240 = 25% and send the owner looking for a problem that is not there. The 40 misses break down as 18 Outside of business hours, 9 Users did not answer, 5 All agents were not available, 6 Abandoned in IVR and 2 Abandoned before 10 sec.
That breakdown is four separate jobs, not one. The 18 after-hours calls are a decision about opening hours or after-hours answering. The 9 unanswered rings mean people who were available let the phone ring for more than ten seconds, so find out which hours they fell in before talking to anyone. The 5 calls with nobody available are a cover gap. The 6 menu abandons say the menu is too long or unclear. The 2 short abandons need no action unless the number grows.
On Professional, the Unanswered Calls dashboard answers “which hours?” directly: set Date breakdown to hourly and filter Unanswered call reason to Users did not answer. With Analytics+, Unanswered Calls+ shows the same misses on a weekday-by-hour heatmap. On Essentials, open Conversations > Call History, filter Call Type to inbound unanswered calls and read the Started at times; Call History refreshes every 15 minutes.
Before changing the rota, open five calls from each large category in Call History and listen where your policy allows. If calls are landing on the wrong menu branch, fix routing with the Aircall opening-hours and IVR setup tutorial instead of adding people to the wrong queue.
Turn missed calls into owned callbacks
A chart tells you what happened last week; it does not tell anyone to ring a customer back today. Aircall’s email notifications live in Aircall Workspace under the user icon (bottom left) > Settings > Notifications. Every role can switch on Voicemails (one email per voicemail on numbers they are associated with, including a link to the recording), Call assignments and Daily follow-up, a summary of missed calls and voicemails nobody has dealt with, sent at 8:00 am UTC. None of the documented options emails you for each missed call, so the daily summary is a safety net, not an alert.
Owners, Admins and Supervisors can change these settings for other people from Dashboard > Users and teams > Users, then the person’s Notifications. In the Workspace mobile app, the Missed calls filter in the Call section lists each miss with its reason in the call details, which is the quickest place for the duty person to work from during the day.
A wedding planner shows the routine in practice. The business sets an internal target of a callback within 30 minutes during staffed hours. At 10:10 am the coordinator opens the missed-calls list, finds three unanswered enquiries, rings the oldest first and adds a note to the call with the outcome. At 10:25 am the manager checks one thing only: is any miss from before 9:55 am still without a note? If so, it gets a named owner straight away. The next morning’s Daily follow-up email should then be short.
If you want a task created for every miss, the tutorial on creating a task for each Aircall missed call covers that build. Give the automation a duplicate rule (one open task per caller, not per attempt), an owner and a done condition, or it becomes one more inbox to watch.
Test the chain once before relying on it: miss one call on purpose, leave a voicemail on another, then check what appeared in the app, who received an email and who claimed the callback. Repeat while the usual owner is off. The test passes only when the backup finds both items without borrowing anyone’s login.
How do Aircall's call volume and unique callers differ?
Aircall's total calls count calls, not customers: a customer who rings three times is three calls and one unique caller. Aircall’s analytics terms define a unique caller as all inbound calls from one phone number in the period. A call transferred between colleagues is still one call, credited to the last person on it. When inbound volume jumps, check how much of the rise is repeat attempts; people ringing back can mean the first call failed.
Outbound needs the same care. The Outbound tab’s Connected rate counts calls that were answered or reached voicemail, so it is not a “people reached” figure. Take an IT support firm that makes 90 outbound attempts: 54 connect, 18 of those reach voicemail and 36 reach people. The connected rate is 54 ÷ 90 = 60%, while the human-contact share is 36 ÷ 90 = 40%. Both are useful, and neither tells you whether the fault was fixed.
On Professional, the User Activity dashboard has a Min Outbound In Call Time (sec) filter. Setting it to 30 seconds, for example, leaves out the shortest connections, which brings the outbound count closer to real conversations. Pick one threshold and keep it, or week-to-week comparisons break.
Tags turn volume into purpose. Ask staff to tag calls with three or four plain labels such as Quote, Order update and Supplier. Overview’s General Performance tab shows the share of calls with no tag, so you know whether the tags can be trusted, and Professional’s User Activity and Inbound dashboards can filter by tag. A person handling 15 long fault calls may be working harder than a colleague making 40 two-minute confirmations; tags make that visible.
Annotate unusual weeks. A print shop that sends a proof-approval reminder might receive 65 inbound calls on a weekday that normally brings 40. Write the cause beside the number and check whether those calls were answered. The question is whether you covered a predictable surge, not whether volume went back to normal.
How do you read Aircall agent activity without blaming people for team misses?
What you can see in Aircall agent activity depends on the plan: Essentials has a Calls by last participant table, Professional adds the User Activity dashboard and the Analytics+ add-on adds User Activity+. On Essentials, General Performance has a Calls by last participant table listing total, inbound and outbound calls finalised per user, where the last participant is whoever ended the call. Professional’s User Activity dashboard adds answered inbound calls, connected outbound calls, average in-call time each way and a sortable leaderboard you can filter by user, team, number, tag and IVR branch. User Activity+ adds the share of connected time each person spent Available, Busy and Not available, average after-call work time and a Ringing attempts chart.
Keep unanswered inbound calls at team or number level. Aircall’s guide to missed calls by user, team and number explains why: a missed call usually rings several agents at once, so a Call History export filtered to four agents can show no misses at all while the team view shows plenty. Both are correct. When you filter by team, choose Calls routed to team rather than the default Users belonging to team, which leaves missed calls out. The last leg also decides: a call that rang Team 1, went unanswered and was then answered by Team 2 counts only for Team 2.
For individual pick-up behaviour, Aircall points Analytics+ customers to Ringing attempts in User Activity+. One missed call that rang four people counts as one ringing attempt for each of them, so twelve team misses on a four-person simultaneous ring can show 48 attempts. Use the chart to compare people, never to reconcile with the team’s missed-call total.
Now an illustrative comparison. Two staff at a small practice completed 80 and 48 calls in a week. The first had 40 hours of phone cover on the rota and the second 24, so both handled two calls per cover hour. The raw counts suggested a gap; the rota removed it. Check call purpose with tags before going further, because the second person may also have taken the longer calls.
With User Activity+, add status time to the same conversation. If a person shows 70% Not available across their phone shift, ask what pulled them away; that is usually a rota question rather than a performance one. A person who is Available 90% of the time with many ringing attempts and few answers is the case for a coaching chat. Use these numbers to plan cover and coaching, not to rank effort.
How do you build a weekly Aircall report from a reconciled call sample?
A weekly Aircall report fits on one page, mixing dashboard numbers with two follow-up measures, and each row names its source so nobody mistakes one for the other. The print shop's report below shows how; all figures are illustrative.
| Measure | Illustrative result | Where it comes from |
|---|---|---|
| Inbound calls | 240 | Overview, Inbound tab |
| Answered by staff | 180 | Overview, Inbound tab |
| Fully handled by AI Voice Agent | 20 | Overview, Inbound tab |
| Missed calls | 40 (16.7%) | Overview, Inbound tab |
| Unique callers with a missed call | 26 | Unanswered Calls+, or your Call History export |
| Missed calls with no connected call within 24 hours | 7 of 40 | Unanswered Calls+, or your Call History export |
Unanswered Calls+ reports the last two rows directly as Unique callers with unanswered calls and Unanswered inbound calls without a subsequent call, where a subsequent call means the same caller was connected within 24 hours, by calling back in, by a callback or by any connected outbound call. Without Analytics+, build them from Call History: filter the week, click Export to download a CSV, and open it in Excel with Data > From Text/CSV and a comma delimiter, as Aircall’s guide suggests. The export carries one datetime (tz offset incl.) column that spreadsheets normally read as a date and time.
In the layout below, column A holds that datetime, column B the call’s direction and outcome written as Aircall’s Call Type labels (if your export gives direction and outcome in separate columns, join them into one label first), and column C the customer’s number. Column D flags whether each missed caller was reached within 24 hours; column E counts each missed caller once.
D2 (fill down; read it on rows where B2 = "Inbound unanswered")
=COUNTIFS($C:$C,C2,$B:$B,"Outbound connected",$A:$A,">"&A2,$A:$A,"<="&A2+1)
+COUNTIFS($C:$C,C2,$B:$B,"Inbound answered",$A:$A,">"&A2,$A:$A,"<="&A2+1)
E2 (fill down; sum column E for unique callers with a missed call)
=IF(AND(B2="Inbound unanswered",COUNTIFS($C$2:C2,C2,$B$2:B2,"Inbound unanswered")=1),1,0)
A zero in column D on an unanswered row marks a missed call nobody followed up within 24 hours; filter for those and they become the first agenda item. Because the rule mirrors Aircall’s own definition of a subsequent call, your numbers and Unanswered Calls+ should be close if you buy the add-on later. A quick sum helps that decision: if the export routine takes 20 minutes a week, that is about 87 minutes a month, against $45 a month for Analytics+ on three licences. Buy it when the manual check keeps slipping, or when you need the hourly heatmap or more than six months of history.
The dashboard rows come from Export in the top right of Overview. Aircall offers PDF, CSV and XLSX, exports only the tab you are on and delivers the files compressed. CSV and XLSX exports leave out single-value tiles, while the PDF includes every tile shown, so pick PDF when you want the headline KPIs and CSV when you want the charts’ data.
For an automatic reminder, an Admin can switch on Activity summary in Workspace notifications: a daily, weekly or monthly email at 8:00 am UTC with inbound, outbound and total calls and the missed-call percentage. Use it as the prompt to open the report, not as the report. Before sending the report round, reconcile five calls against your totals; where a transferred call appears differently in two views, note that one counts whole calls and the other ringing attempts or last participants.
Turn each finding into a decision line someone can check: “Menu abandons: six. Owner: routing coordinator. Change: cut the menu message to one sentence and retest both options. Check: same filters next week.” That beats “improve missed calls”, because next week’s report shows whether it happened.
If the spreadsheet side of the weekly report is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.
What should you check when an Aircall number turns red?
When an Aircall number worsens, check in a fixed order: reporting period, numbers ticked, timezone and permissions first, then five affected calls, then the rota and routing. Only after that decide whether the problem needs more staff time, a menu change or automated answering.
An illustrative failure: weekly inbound calls fall from 200 to 140 and the owner assumes demand has collapsed. The coordinator finds that a line added the month before was never ticked in the weekly filter. Ticking it brings the total back to 205. The lasting fix is a rule: review the number list in the filter after every phone-system change.
Another: after adding a 25-second greeting, service level holds steady and everyone relaxes. Aircall’s definitions explain why that is misleading. Service level is based on time to answer, which excludes the welcome message, IVR and time with the AI Voice Agent, while Average waiting duration includes the welcome message and IVR. Every caller now waits about 25 seconds longer, and only the waiting-time figure shows it. Ring the line from an outside phone after any greeting change.
Change one thing at a time where you can. If opening hours, menu wording and team ringing rules all change in the same week, next week’s improvement or decline has no clear cause. A two-column change log (date and change, expected effect) is enough.
Do not buy Analytics+ only to reproduce a weekly count you can already read. Buy it for a question the current views cannot answer, such as ringing attempts per person, the weekday-by-hour heatmap, callback follow-through or more than six months of history, and use the free trial on a real week to check that it answers that question.
If you want help deciding whether a red number needs more staff, a menu change or automated answering, I offer one-to-one AI consultations for small businesses.
A 20-minute weekly review the team can run without you
Book the same slot each week, for example Monday at 9:30 am, and keep to four steps of about five minutes each:
- Open Overview with the saved filter line and record inbound calls, answered, AI-handled and missed.
- Read the missed-reason chart and write one decision line for each reason above five calls.
- Check follow-up: the zeros in column D of your export, or the Unanswered inbound calls without a subsequent call KPI in Unanswered Calls+.
- Look at agent activity next to the rota, using whichever view your plan has, and note any cover or coaching action.
Then hand the instructions to a colleague and ask them to rebuild last week’s report without help. If their numbers differ, find out why and fix the written steps. The report should survive a holiday, a rota change or a new supervisor.
Close each review by confirming three things aloud: the oldest unresolved caller has an owner, the biggest routing issue has a test booked, and next week will use the same filters. When those three hold, the dashboard is driving decisions rather than producing charts.
Further reads
- Aircall Free Trial: What to Test Before You Buy Three Licences — Test the reporting you need before purchasing.
- How to Connect Aircall to Salesforce and Sync Calls and Notes — Check activity against Salesforce records.
- Aircall Pricing Plans: Essentials or Professional for a Sales Team — Compare the plans behind the dashboards.
- Aircall AI Voice Agent: What to Automate First With 50 Minutes — Choose a narrow job for automated answering.
- How Much Does Aircall's AI Voice Agent Cost per Minute? — What Aircall's AI Voice Agent really costs at 200, 500 and 2,500 minutes a month, and where a bundle starts to beat pay as you go.
- Aircall UK Pricing: Licences, Numbers and AI Voice Agent Cost — What a UK team pays Aircall in pounds, how numbers and SMS work, what recording needs, and what the AI Voice Agent adds.
Show 3 more related tutorials
- How Much Is Aircall per Month? 3 Seats, Add-Ons, AI Minutes — A three-seat Aircall bill built line by line: licences, extra numbers, AI Assist Pro and AI Voice Agent minutes, with four worked scenarios.
- Aircall HubSpot Integration: Sync Calls, Voicemails and Tasks — Install the Aircall HubSpot integration, set ownership and outcome rules, and build missed-call and voicemail tasks with a workflow your sales team can trust.
- How to Set Up Aircall Voicemail: Greetings, Transcripts, Alerts — Set the greeting, transcription and email alerts for Aircall voicemail, control who gets each message, and turn voicemails into owned callbacks.
Browse all AI-for-business tutorials
Sources: Aircall Help Centre articles Analytics Essential: Overview dashboard; Analytics features by plan; Missed, Unanswered and Abandoned Call Classifications; Understanding missed calls in Analytics; Analytics: Terms; Analytics Pro: Unanswered Calls dashboard; Analytics Professional: User Activity dashboard; Analytics+: User Activity+ and Unanswered Calls+ dashboards; Call History in Aircall Dashboard; Call History fields reference; Aircall Workspace: Notifications settings; Purchasing add-ons in Aircall. Aircall pricing page.
