What Credit Union Managers Should See on a Contact Centre Dashboard

Every Monday, someone in a credit union asks the same question: how did we do on the phones last week? Too often, the honest answer is a guess, pieced together from staff impressions and a call report that shows totals but not the members who gave up waiting.

A credit union's contact centre dashboard should show three views: a live view for whoever is answering calls now, a daily view for service and branch managers, and a monthly view for the board. Each view answers different questions, from "who's waiting right now?" to "are we within our service tolerances?"

TL;DR

• One dashboard for everyone ends up useful to no one. Build three views: live, daily and monthly.
• The live view is about queues and staffing now. The daily view is about missed calls and patterns. The monthly view is about outcomes and trends.
• Call reasons are the metric many credit unions lack, and the one that shows where to fix the service.
• Monthly reporting doubles as evidence for outsourcing reviews and operational resilience testing.

Who is the dashboard for?

Three groups use contact centre data, at three different speeds.

Staff and team leads answering calls need to know what's happening this minute. Service and branch managers need to know what happened yesterday and what to change today. The board and senior management need to know how the service performed over the month, against the tolerances and targets they approved.

Trying to serve all three on one screen produces a dashboard crammed with numbers that nobody reads. Separate views, built from the same data, work better.

What should be on the live wall screen?

The live view answers one question: does anyone need to act right now? Keep it to a handful of numbers, large enough to read across a room.

• Members waiting in each queue, and the longest current wait.
• Staff available, on calls and on breaks.
• Calls answered within target so far today, as a percentage.
• Callbacks requested and not yet returned.
• AI Voice Agent calls in progress, if AI is handling routine calls.

That's enough. Adding more makes the screen harder to read at a glance.

What should a service or branch manager see each morning?

The daily view explains yesterday and points to today's changes. This is where missed calls become visible.

Adrian McGeow at DigitalWell, who demonstrates DigitalWell 360 reporting to customers, describes the detail managers can get:

"Here are your missed calls. Here's [...] what extensions they went to, how long were they ringing for, when did they hang up." Adrian McGeow, DigitalWell

A good morning report shows missed and abandoned calls by hour, so a manager can see whether 9am or lunchtime is the problem. It shows which branch or team each missed call was meant for. It shows callbacks and whether they were returned the same day. And it shows the top call reasons, so the manager knows what members were ringing about.

What does the board pack need each month?

The monthly view is about outcomes and trends. Boards need fewer numbers, with context: this month, last month, and the same month last year.

It should include the share of calls answered within the target time, the abandonment rate, first-contact resolution where it's measured, and the top call reasons with their trend. If AI is handling calls, include how many were resolved without staff and how many were handed over.

For credit unions, the monthly report also supports governance. The Central Bank's operational resilience guidance expects boards to set impact tolerances for critical or important services, and the Credit Union Handbook expects regular review of outsourced service performance. Contact centre data, alongside supplier SLA reports and incident logs, is part of that evidence.

Which metrics matter, and who needs them?

The table lists the core metrics, the question each answers, who needs it and how often.

Why are call reasons the missing metric?

Because many phone systems count calls without knowing what they were about. A credit union can see that call volume jumped on a Monday without knowing whether it was loan queries, a card problem or a website outage.

Call reasons change what a manager can do. If a large share of calls are balance enquiries, that's a case for AI Voice Agents or better online access. If calls about a new loan product spike, the product information needs fixing.

DigitalWell's AI Voice Network transcribes and summarises calls and surfaces demand trends in real time, so call reasons come from the calls themselves rather than from staff tallies. The Credit Unions page covers the member calls AI Voice Agents complete end to end, such as balance queries, card blocking and loan status.

What tools produce these dashboards?

The contact centre platform provides the base data. DigitalWell 360 includes real-time and historical dashboards across queues, agent performance, SLA and service levels, fully customisable, as the Smart Workplace page sets out. KennCo Insurance, another Central Bank-regulated customer, uses DigitalWell 360's Grafana-based custom reporting module to build dashboards on SLA compliance, agent performance, queue statistics and its own KPIs.

Larger contact centres on Genesys Cloud CX get real-time and historical analytics built into the platform. After moving to Genesys with DigitalWell, Campion Insurance's management team gained real-time dashboards and historical analytics across all its offices for the first time.

How should a credit union build its dashboards?

Build them in this order, and involve the people who'll use each view.

1. Agree on the service targets first. A dashboard without targets can't tell anyone whether performance is good.
2. Build the daily view next. It's the one that changes behaviour, through missed calls and call reasons.
3. Keep the live view short. Five numbers on a wall screen beat twenty on a laptop.
4. Design the board view with the board. Agree the metrics, the comparisons and the format once, then keep them stable.
5. Add call reasons as soon as possible. Start with a short list of categories and refine it.
6. Review the dashboards quarterly. Remove numbers nobody uses and add the ones people keep asking for.

Frequently Asked Questions

What's a good service level target for a credit union?

It depends on the credit union's size, staffing and members. Many contact centres set a target such as a percentage of calls answered within a set number of seconds. Agree yours with the board and review it against abandonment rates.

Can we see missed calls to each branch?

Yes, if branch calls run on the same platform. DigitalWell 360 reporting shows missed calls by extension, how long they rang and when the caller hung up.

How do we measure first-contact resolution?

Link contacts to the member and the request, then count requests with no follow-up contact within a set window, such as seven days.

Should AI calls appear on the same dashboard?

Yes. Showing AI-resolved and handed-over calls alongside staff-handled calls gives the true picture of demand and how it's being met.

Can dashboards help with our outsourcing review?

Yes. Contact centre performance data, together with supplier SLA reports and incident logs, is part of the evidence for annual outsourcing reviews and operational resilience testing.

Key Takeaways

• Build three views from the same data: live for staff, daily for managers, monthly for the board.
• The daily view does the most work, through missed calls by hour and top call reasons.
• Many credit unions lack call reasons, and AI transcription can supply them from the calls themselves.
• Monthly reporting doubles as governance evidence for outsourcing reviews and operational resilience.
• DigitalWell 360 and Genesys Cloud CX both provide real-time and historical reporting that can be shaped to these views.

Want to see what your phone data could tell you? Ask DigitalWell's credit union team for a reporting demo built around your own call flows.