Skip to content

Bananaflow MCP is live.

Read the docs

Call Center Dashboard: Metrics to Show Daily

Jaseem Abbas, founder of Bananaflow, in glasses and a dark top against a pale background.Jaseem Abbas

Published
Cover for "Call Center Dashboard: Metrics to Show Daily": a white line diagram of a wide monitor on a stand holding a row of three tiles over one bold sparkline, with a headset panel beside it under a lit pill reading Daily view, and no numbers drawn, drawn over a soft, out-of-focus salvia in muted sky blue, its slender petals blurred into veils, with an aqua haze at one end and a dusty rose glow at the other.

A call center dashboard is one screen that shows how the floor is doing right now and against yesterday: calls, answer speed, outcomes and time spent, with each number next to the one it should be compared with. Most guides to the call center dashboard are galleries of fifty widgets. This one picks six numbers, says which belong on a live view, a daily view and a weekly view, and shows how an Indian floor manager can read them in ten minutes.

Here is the morning. Ritu Sharma runs a 120-seat inbound floor in Jaipur that handles customer care for a consumer durables brand, in Hindi and English. At 10:00 she opens one screen. Yesterday there were 6,200 calls. Of the callers who asked for a person, 91% were answered within 90 seconds, against her own target of 95%. Abandonment was 6.5%, average handling time was 5 minutes 40 seconds, and 38% of calls closed as "resolved, no follow-up". She does not scroll. Ritu, the brand and every number in this post are made up for this example.

What is a call center dashboard?

A call center dashboard is a single screen of the few numbers a floor manager needs to run the day, each shown against a comparison. It is not a report. A dashboard answers "how are we doing now?" and a report answers "what happened over the period?". The screen is only useful if you can read it in a minute and know what to do next.

Think of it as the summary of the call records. No manager can listen to every call, so the screen tells them where to listen. The words on it (AHT, FCR, abandonment, connect rate) are defined in our guide to call center metrics. This post does not repeat those definitions. It decides which of them earn a place on the screen, how often to look at each, and how to lay it out.

Which metrics belong on the main screen?

Six: calls handled, connect or answer rate, success rate by outcome, abandonment, average handling time and minutes used. This is our own short list, built from the call center metrics most floors already track. Each name links to its definition so you can check how it is worked out.

The six-number screen: calls, connect rate, success, abandoned, average handling time and minutes, each tile with a small arrow and a thin line under it labelled against yesterday.
  • On the screen: Calls handled

    What it tells you
    Volume against yesterday and the same weekday last week
    Where it is defined
    Count of finished calls
  • On the screen: Connect rate (outbound) or answer rate within a target time (inbound)

    What it tells you
    Whether callers or customers are reached, and how fast
    Where it is defined
    [Connect rate](/blog/call-center-metrics/#what-is-connect-rate)
  • On the screen: Success rate by outcome

    What it tells you
    How many calls ended the way you wanted
    Where it is defined
    [Call disposition codes](/blog/call-disposition-codes/)
  • On the screen: Abandonment

    What it tells you
    How many callers gave up before an answer
    Where it is defined
    [Abandonment rate](/blog/call-center-metrics/#what-is-abandonment-rate)
  • On the screen: Average handling time

    What it tells you
    How long a call takes, and so staffing
    Where it is defined
    [AHT](/blog/aht-in-call-center/)
  • On the screen: Minutes used

    What it tells you
    How much time the floor, or the AI agent, spent on calls
    Where it is defined
    Total call minutes

Two choices are deliberate. First, success rate by outcome stands in for resolution. A single outcome code per call, taken from a short list, is easier to count every morning than a repeat-contact window. First call resolution still matters, and the FCR glossary entry shows how it is worked out, but it needs days of waiting, so it lives on the weekly tab.

Second, money per call stays off the main screen. Cost per call depends on what finance counts as cost, and a number nobody agrees on starts arguments instead of actions. Agree the definition first, using our guide to cost per call in India, and then add it to the second tab.

What should be live, daily and weekly?

Queue and agents free are live, the six numbers are daily against the prior day, and trends, outcome mix and busiest hours are weekly. Mixing the speeds is the usual dashboard mistake. A live number that moves every second and a weekly trend on the same tile teach nobody anything.

Three layers seen from the side: Live (queue and agents free) on top, Daily (the six numbers) in the middle and Weekly (trends, outcomes and busiest hours) at the bottom.
  • Live: calls waiting, the longest wait and how many agents are free. Your phone system or automatic call distribution setup usually supplies these. They answer "do I move someone onto the phones now?". For how many seats a target needs, see Erlang C staffing.
  • Daily: the six numbers, each against yesterday and against the same weekday last week. The same weekday matters because a Monday is not a Sunday.
  • Weekly: the trend of each number, the outcome mix and the busiest hours. Weekly is for coaching and staffing, not for firefighting.

Every number needs two things beside it: the period it is compared with, and a name of the person who acts on it. If no one acts on a number for a month, take it off the screen.

Is there an Indian benchmark for answer speed?

Yes, for telecom operators: TRAI's 2024 quality of service rules want 95% of calls that ask for a person answered within 90 seconds. They are the Standards of Quality of Service of Access (Wireline and Wireless) and Broadband (Wireline and Wireless) Service Regulations, 2024, dated 2 August 2024. They bind telecom service providers' own customer care centres, so for any other business they are a public yardstick and not a rule.

Two benchmarks matter here, as the regulation text on the TRAI website reads (read on 15 November 2026):

  • Accessibility of the call centre or customer care: at least 95%, measured quarterly from 1 October 2024. Regulation 7.1.4 says accessibility "basically means percentage of calls got connected and answered by the call centre agent or Interactive Voice Response system as applicable".
  • Calls answered by operators (voice to voice) within ninety seconds: at least 95%, measured monthly from 1 April 2025. Regulation 7.1.5(i) counts the 90 seconds "from the time the customer has keyed the relevant number in the IVR option menu or direct operator access".

The second line is the useful one for a dashboard. It says to start the clock when the caller asks for a person, not when the call first rings, so a long menu does not eat into your own number. TRAI also publishes later files on the regulation's page, so check there for the current figures before you copy a target.

Ritu borrows the 95% and 90 seconds as her own target. That is a choice she makes, not a rule that applies to her floor.

What goes in daily and weekly call center reports?

The same six numbers against the prior period, the outcome mix, the busiest hours and a short list of calls to listen to. Call center reports are the record of a period, so they add what a screen cannot hold: the spread across days and the reasons behind a change.

A simple pattern that works for most floors:

  1. Daily report, sent before the morning huddle. The six numbers against yesterday and last week, plus the three calls with the worst outcome to listen to.
  2. Weekly report, sent for the coaching session. Trend lines for each number, the outcome mix by call reason, and the busiest hours as a grid.
  3. Monthly report, for the staffing plan. Volume by hour and day, AHT by queue and the language mix.

Keep the outcome mix honest by reading it with the outcome list. If "other" grows past a few percent of calls, the list needs a new code. Our guide to call disposition codes has a starting list.

Read each report by language and queue, not only as a floor total. A good average can hide a failing Tamil queue next to a strong Hindi one.

How do you stop a dashboard from being gamed?

Pair every speed number with a quality number, and listen to a sample of calls behind every big change. Any number with a bonus attached will be pushed, and pushed in the cheapest way: AHT drops because agents hang up early, and abandonment drops because the queue message gets shorter.

  • Show pairs side by side: AHT with success rate, answer speed with abandonment.
  • Listen to the calls behind a jump. A 20% fall in AHT overnight is a reason to open ten calls, not to celebrate.
  • Change one target at a time, and mark the date on the chart when a definition changes.

Our guide to call center metrics lists the habits in full, and the guide to call audit in BPO shows how to sample calls for review.

How do AI voice agent calls show up on the dashboard?

As calls with an outcome code, a transcript, a recording and the minutes used, so they can sit on the same screen as human calls, split by channel. The split matters. If an AI voice agent starts taking the simple calls, the human queue gets harder calls, and AHT on the human side rises even though nothing got worse. Reading each channel on its own stops that being mistaken for a drop in performance.

Each AI call ends with one outcome code taken from a list you wrote, so the success rate is a count and not a judgment. The same list works for human agents, which lets you compare the two on equal terms. For how to write that list, see call disposition codes. The analytics page shows what the reports for AI calls contain.

A worked morning review

Ritu's 10:00 review takes about ten minutes. The numbers are made up, and so is the floor.

  • Number: Calls handled

    Yesterday
    6,200
    Reading
    In line with the same weekday last week
  • Number: Answered within 90 seconds of choosing a person

    Yesterday
    91%
    Reading
    Below her own 95% target
  • Number: Abandonment

    Yesterday
    6.5%
    Reading
    Higher in the late morning
  • Number: Average handling time

    Yesterday
    5 min 40 s
    Reading
    Steady
  • Number: Closed as "resolved, no follow-up"

    Yesterday
    38%
    Reading
    Steady

She follows three steps. First, she checks the pair: answer speed missed, but handling time and the share resolved did not move, so the problem is queueing and not call quality. Second, she opens the busiest-hours view for the week. It shows the miss sits between 11:00 and 13:00 on most days. Third, she acts: she moves two tea breaks out of that window and asks two team leads to listen to six calls from that stretch. The target and the changes are Ritu's decisions. The screen only tells her where to look.

How Bananaflow fits

Bananaflow is an AI voice agent platform for inbound and outbound calls, in English and 10 Indian languages. For the calls an AI agent takes, Reports shows the calls, the success rate, the connect rate and the minutes used, each against the prior period. It adds trends, outcomes, a heatmap of the busiest hours and a CSV export of the calls.

You can filter the same view by date, agent, campaign and channel, so a campaign's numbers or one agent's calls sit on their own. Every call keeps one outcome code from the agent's own list, which can be mapped to your dialer or CRM codes, along with a transcript, a recording, the minutes used and the fields the agent collected. A QA step can score a call and return tags, sentiment and a summary, as the call QA page describes. Webhooks send each call's result to your own systems after it ends, and call events can be exported to BigQuery. To see one campaign's calls on their own, read about campaigns.

See the analytics page for what Reports shows.

What should you remember about a call center dashboard?

  • Six numbers on one screen, each against the period it should be compared with.
  • Three speeds: live for the queue, daily for the six numbers, weekly for trends and busiest hours.
  • Pair speed with quality, and listen to calls behind every big change.
  • Use TRAI's 95% in 90 seconds as a yardstick, knowing it binds telecom operators' own call centres only.
  • Split AI and human calls by channel so a change in mix does not look like a change in performance.

Start this week with one sheet: write the six numbers, put yesterday beside each, name an owner for each, and read it at the same time every morning.

FAQ

Frequently asked questions

  • What should a call center dashboard show?

    Six numbers: calls handled, connect or answer rate, success rate by outcome, abandonment, average handling time and minutes used, each against the prior period. This is our own short list. Everything else belongs on a second tab, so the main screen can be read in a minute.

  • What is a good answer rate for a call center in India?

    There is one public yardstick: TRAI's 2024 quality of service rules for telecom operators ask for at least 95% of calls that request a person to be answered within 90 seconds, counted from the key press. It binds telecom operators' own call centres only. Any other business sets its own target.

  • How often should call center reports be reviewed?

    At three speeds. Look at the queue and free agents live, the six main numbers every morning against yesterday and the same weekday last week, and trends, outcome mix and busiest hours once a week. Use the weekly view for coaching and staffing, not for firefighting.

  • What is the difference between a dashboard and a report?

    A dashboard is a screen that shows how the floor is doing now and against yesterday. A report is the record of a period, such as a day, week or month, with the outcome mix, busiest hours and calls to listen to. The dashboard tells you where to look, and the report shows what happened.

  • Can AI voice agent calls be tracked on the same dashboard?

    Yes. An AI voice agent call leaves an outcome code, a transcript, a recording and the minutes used, so it can sit on the same screen as human calls, split by channel. The split stops a change in call mix from looking like a change in performance.

  • Which call center metrics are vanity numbers?

    Any speed number shown without a quality number next to it. A falling handling time looks good until the share of resolved calls falls too. Pair each speed number with a quality number, and listen to calls behind every large change.

Written by

  • Jaseem Abbas, founder of Bananaflow, in glasses and a dark top against a pale background.

    Jaseem Abbas

    Founder, Bananaflow

    Jaseem founded Bananaflow to build voice AI that understands how people in India really speak, including the switch between languages in the middle of a call.

Similar articles

Bring us one process. We'll pilot it on your real calls, with your team as the fallback.

Plan a pilot