Skip to main content
Version: Latest
User ManualNeed configuration, code or deployment details? In the Technical Manual: Enterprise Contact Center Report CatalogAgents, Queues, Routing, and DialerReport BuilderReportsOmnichannel CRM — leads, accounts and opportunities

Reports

Reports show what happened in your contact center over a period you choose: calls, queues, agents' time, campaigns, leads and AI conversations. Every report lives under the Reports menu, grouped by category: Executive, Operations, Queue & Routing, Agent Performance, Workforce & Payroll, Billing & Usage, CRM & Campaigns, Compliance & Audit, and Technical & IT. Reports from other modules can appear under General. The menu lists the categories in alphabetical order, and the Reports page shows the reports with no category first, without a heading.

MenuReports > category > report
PermissionsView Contact Center reports (supervisors and administrators have it by default); View Omnichannel reports for the CRM and campaign reports (administrators and supervisors have it by default)
PermissionsEach report has the permission of the module that provides it. View Contact Center reports opens the Contact Center reports (supervisors and administrators have it by default). View Omnichannel reports opens the CRM and campaign reports (administrators have it by default, and so does anyone who may manage activities). A report with its own permission, such as Run 'Phone Number Verifications' Report, needs that one. Manage report subscriptions opens Reports > Subscriptions (administrators have it by default).
FeaturesReports, for CSV export; Reports (OpenXml) adds Excel export, and Reports (PDF) adds PDF export. Contact Center reports appear when Contact Center Work Distribution is also on; the CRM reports come with Omnichannel Management and Omnichannel CRM.
Can't find it?

What you see depends on your role. If the menu, a button or a setting on this page is missing, ask your administrator to give you the permission listed above or to turn on the feature. Only administrators can turn features on and change site settings.

You only see the reports your permissions allow.

If the Reports page says No reports are available, ask your administrator to turn on a feature that adds reports, or to give you the permission.

To build your own reports with drag and drop, see Report Builder.

Run a report​

  1. Open Reports and pick a category, then a report.
  2. Set the Date range. It starts on today (from the start to the end of the day), in the site's time zone, unless the report starts on a period of its own: the AI chat and usage reports start on All Time, the AI QA Dashboard on the last 7 days, and Hours by Category on this week. Pick a preset or a custom range (see Date range choices). A Contact Center report covers up to 400 days, and a report on agents' time up to 31 days (see Agent time over long periods).
  3. Set the filters the report offers, such as Queue group, Queue, Agent, Channel, Direction, Campaign group, Campaign, Source, Status, Interaction type, Dialer profile, Queue state, Disposition, Activity ID or Reason. Each report shows only the filters it uses. In Disposition you can tick several dispositions at once.
  4. Click Show.
  5. To keep a copy, click Export CSV. When the Reports (OpenXml) or Reports (PDF) feature is on, the button becomes an Export menu with Export CSV, Export Excel (.xlsx) and Export PDF. Excel puts each section of the report on its own worksheet. PDF lays the report out as it looks on screen, with its charts, and numbers the pages; a wide table turns the pages sideways.

How the filters work:

  • A filter left on All (for example All queues) does not narrow the report.
  • Filters combine: picking a queue, an agent, the Voice channel and the Inbound direction shows only what matches all four.
  • Every number, total, percentage and average is worked out again from the filtered records, so it always matches what you picked.
  • An export uses the same date range and filters as the report on screen. It keeps the detail, subtotal and grand-total rows, in the order shown. The file is named after the report and the first and last day of the period, for example contact-center-call-insights-20260929-to-20261029.csv; an open-ended period names the day it has (-from-20260929 or -to-20261029), and All Time ends in -all-time.
  • A report can need a permission of its own to export, such as Export AI Chat Analytics for the AI chat reports. Without it, the export button is hidden, and a subscription can't attach the file.
  • A link in a table, such as the session of a conversation in the AI QA Dashboard, opens what it names. An export writes its text.
  • If a report needs a feature your site does not use (for example call transfers or recording), it shows the notice Capability not enabled, which names that feature, instead of showing zeroes. A report that still has real figures leaves out only the columns that feature would fill.

Reports of the modules above can be emailed on a schedule (see Email a report on a schedule). Reports you build yourself in the Report Builder cannot be subscribed to; to email one, use the Email Report task in a workflow (see Report Builder workflows). The reports of this page can be emailed on a schedule; see Email a report on a schedule. A report made with the Report Builder cannot be subscribed to: use the Email Report task of a workflow instead.

Any report in this list can also be emailed on a schedule, see Email a report on a schedule. Reports built with the Report Builder cannot be subscribed to; to send one by email, use a workflow with the Email Report task.

What the main numbers mean​

The cards at the top of Executive performance dashboard, Call insights and many other reports use the same definitions everywhere, so a number means the same thing in every report. Every percentage is worked out from counts, never by averaging other percentages.

NumberWhat it means
InteractionsEvery call or message in the period. A transfer, consult, conference or callback stays part of the same interaction.
Inbound offeredThe inbound interactions.
Inbound answered and the answer rateInbound interactions an agent took, and that count divided by Inbound offered. A caller the platform only answered to play the queue or to record a voicemail is not answered.
Abandoned and the abandonment rateInbound callers who hung up while waiting in a queue or while an agent was being offered the call, before anybody answered. The rate is Abandoned divided by Inbound offered. Every abandon counts, however short.
VoicemailInbound calls the platform sent to voicemail instead of connecting: the offer rang out, the queue's maximum wait passed, the entry point was closed, or the queue was full.
Callback requestedInbound callers who accepted the queue's offer of a callback instead of waiting.
FailedCalls that failed for a technical reason: the provider reported an error, or the call could not be placed or bridged. A caller who hangs up before anyone answers is an abandon, never a failure.
Avg speed of answerHow long inbound callers waited, from the moment the call was created to the moment an agent answered, averaged over answered inbound calls.
Avg handle timeThe talk, hold and wrap-up time of a handled call, averaged over answered calls. Abandoned, voicemail and failed calls are left out.
Transfer rateThe share of answered calls that were transferred at least once.
Recording coverageThe share of answered voice calls that have a recording.
Service level (per queue)Inbound calls answered within the queue's service-level threshold, divided by inbound answered plus abandoned. Voicemail, callback and failed calls are left out. A queue with no threshold shows none.
Utilization and Occupancy (per agent)Utilization is busy plus wrap-up time divided by all signed-in time. Occupancy is busy plus wrap-up time divided by the time the agent was available, reserved, busy or in wrap-up. Neither says how well an agent works.

Voicemail and Callback requested are neither answered nor abandoned. They count toward Inbound offered but not toward the abandonment rate or the service level, and each has its own column.

Email a report on a schedule​

With Report Subscriptions on, a report can be emailed every day, week or month, such as your queue service level every Monday morning. It is a feature under Tools > Features, in the Reporting category, and it needs the Reports feature and the Email feature, which it turns on with it. Report Subscriptions adds Reports > Subscriptions, and Manage report subscriptions is the permission that opens it (administrators have it by default). A person can only choose a report they may open.

Email must be set up first. A subscription goes out through your site's email provider. Under Settings > Email, the site says No email providers are currently enabled until you enable a provider feature, such as the SMTP provider, and enter its settings (sender address, host name, port and, when the server asks for them, credentials). Until then a subscription can be saved, but each send fails, and the list tells you why.

  1. On Reports > Subscriptions, click Add subscription.
  2. Choose the Report, listed by category. Name is optional; the report's name is used when it is blank.
  3. Choose when to Send it: Every day, for the day before, Every week, for the 7 days before, or Every month, for the month before.
  4. Choose the Day of the week (for a weekly report) or the Day of the month, from 1 to 28 (for a monthly one), and the Hour, from 0 to 23, in your site's time zone.
  5. Under Email to, enter the addresses, separated by commas. Choose a file format under Attach the report as (CSV, Excel (.xlsx) or PDF) to get the report as a file too, or leave No file. The email shows the report's numbers and tables either way.
  6. Leave On ticked, and click Save, or Save and send now to send it straight away for the period before.

The list shows each subscription with its schedule, its recipients and when it goes out next, and you can search it by name. A background task checks every five minutes for subscriptions that are due and sends them. If a send fails, such as when the site's email is not set up, the row says Last run didn't go out with the reason, and the subscription's page shows when it goes out next and what happened last time. Fix the cause, and save it again with Save and send now. Untick On to pause a subscription: it stays in the list with an Off badge and is not sent. Delete removes it.

Reports you build yourself in the Report Builder cannot be subscribed to. To email one, use the Email Report task in a workflow (see Report Builder workflows).

Show a report on the dashboard​

With the Admin Dashboard feature on (under Tools > Features), any report you may view can be a widget on the admin dashboard: its figures, tables and charts for a period that moves with the clock, so the numbers are there without opening the report. The Report widget shows any report on this page. The Custom Report widget, which comes with the Report Builder, shows a report you built (see Show a report on the dashboard).

  1. Open the admin Dashboard and click Manage Dashboard, then Add Widget, and pick Report.
  2. Position, Width and Height place the tile on the dashboard, and Title is the name above it.
  3. Choose the Report. The list has every report you may view under Reports, by category.
  4. Choose the Period: Today, Yesterday, Last 7 days, Last 30 days, Last 90 days, This month, Last month, This year, Last 12 months, All time, or Custom dates, which asks for a From and a To day. Every period except custom dates moves with the clock: the last 30 days is always the 30 days up to now.
  5. Choose what to Show: Figures and tables, Figures only, Tables only, Charts only or Everything. A report that has only a table shows nothing under Figures only.
  6. Rows per table limits how many rows of each table appear (it starts at 5), and Keep for (minutes) is how long the widget keeps what it shows before it runs the report again (it starts at 30). 0 runs the report on every visit. Saving the widget starts over.
  7. Click Publish, then Close Editor.

Each tile names its report, says its period in words, says when its result was made, and has an Open the full report link that opens the report with its filters and exports.

Every tile checks the person looking at it. Someone who may open the dashboard but not the report sees You can't view the report in its place, instead of numbers, and a widget that has no report chosen says Choose the report this widget shows by editing it. If the report cannot run, the tile says so, and the details are in the log. A tile that has nothing for its period says Nothing to show for this period.

The Access the Admin Dashboard permission opens the dashboard, and Manage the Admin Dashboard opens its editor. The person also needs the permission of each report whose tile they should see.

Agent time over long periods​

The reports on agents' time read every state change of every agent in the period: all the Workforce & Payroll reports, Agent presence audit and Agent activity timeline. To keep them quick, they have these limits:

  • 31 days at a time. A longer period shows This period is too long for this report, with the longest period allowed and the number of days you picked, and no figures. Pick 31 days or fewer, for example one month at a time. An export has the same limit. Your administrator can change both limits.
  • 5,000 rows on screen. Agent presence audit lists the most recent 5,000 changes and Agent activity timeline the first 5,000 entries, with a note above the table that gives the total. Pick an agent or a shorter period to see the rest. An export of Agent presence audit lists every change; Agent activity timeline exports its first 5,000 entries. The timeline's summary at the top still counts every entry.
  • Too much to read in time. If the period still holds more than the database can read in time, the report shows This period is too large to report. Pick an agent or a shorter period and run it again.

Reports of agents' time over many days are quick because the site keeps a summary of each finished day for every agent. The figures are the same as adding up every change: the first and last day of the period, today, and any day that changed after it was summarized are always worked out from the changes themselves.

Date range choices​

ChoiceWhat it covers
Relative daysToday, Yesterday, Last 24 Hours, Last 7 Days, Last 30 Days, Last 90 Days.
Calendar periodsThis Week, Last Week, This Month, Last Month, This Quarter, Last Quarter, This Year, Last Year.
Rolling monthsLast 3 Months, Last 6 Months, Last 12 Months.
Custom RangeA start and an end date and time that you pick. Empty, they default to today from 00:00 to 23:59.
On or beforeEverything up to a date and time, with no start. A report that starts on today reads it from today instead.
On or afterEverything from a date and time, with no end. A report that starts on today reads it up to today instead.
All TimeEvery date. Offered by the reports that start on a period of their own, such as the AI chat reports.

The button always shows the range you picked in words, for example From Jan 1, 2026 to Jan 31, 2026. Weeks start on the first day of the week for your language settings.

Statistics in 15-minute intervals​

With Contact Center Interval Statistics turned on, the site keeps the numbers of every queue and agent in 15-minute intervals: how much work was offered and answered, the service level, waits and handle time, and how long each agent was signed in and in each state. Workforce planning uses them, and you can build your own reports on them.

  1. Go to Interaction Center > Management > Interval statistics to see how far they are computed and today's totals so far. Days are UTC days.
  2. In Reports > Report Builder, add the Queue intervals or Agent intervals data set. Group by Half hour or Hour to see longer intervals.
  3. After changing a queue's service level threshold, enter a range of days under Rebuild and select Rebuild. A few days are computed again every five minutes.
New sites

When the feature is first turned on, earlier days are filled in a few at a time, starting from today. Nothing before the first call or agent sign-in is computed.

The reports by category​

The Reports page and the Reports menu group the Contact Center reports into the categories below. Each category answers a different kind of question: Executive for the whole center at a glance, Operations and Queue & Routing for how calls and queues performed, Agent Performance for people, Workforce & Payroll for the time agents spend in each state, Billing & Usage for what was used, Compliance & Audit for the records behind the totals, and Technical & IT for providers and failures. CRM & Campaigns holds the campaign and lead reports of the CRM, and the CRM's activity reports sit in Operations, Queue & Routing, Agent Performance and Compliance & Audit beside these. The CRM reports are described in Leads, Accounts and Opportunities and the Omnichannel pages.

Executive​

ReportWhat it shows
Executive performance dashboardEnterprise KPI cards and interactive charts for interaction demand, accessibility, channel mix, queue service level, agent workload, and operating efficiency.

Operations​

ReportWhat it shows
Call insightsInbound and outbound call volume, answered, abandoned, and failed calls, handle time, and a daily trend.
Call qualityHow calls rated, the agents and network paths poor calls cluster on, their likely cause, and each poor call's measurements.
Channel performanceInteraction performance grouped by voice, chat, email, SMS, and other supported channels.
Day-of-week performanceInteraction demand, outcomes, and response metrics grouped by weekday.
Dialer activity and healthWhether the dialer is dialing, idle, holding back, has nothing to call or has stalled; its last pacing cycle and call per campaign and dialer profile; calls and routing decisions per hour; and suppressed attempts by reason.
Direction performanceInbound and outbound interaction performance with consistent outcome and duration metrics.
Hour-of-day performanceInteraction demand, outcomes, and response metrics grouped by UTC hour.
Interaction lifecycle durationAverage wait, connected, wrap-up, and end-to-end duration by interaction status.
Interaction outcome summaryInteraction volume and response metrics grouped by normalized lifecycle outcome.
Interaction volume trendDaily offered, answered, abandoned, and failed interaction volume.
Interval performanceDaily interaction outcomes, answer and abandonment rates, speed of answer, and handle time.

Queue & Routing​

ReportWhat it shows
Agent availability and wait timeLive, per agent: how long each has waited for a call, today's calls, session health, stale states, and why each queue or campaign is or is not giving them work.
Dialer decision logEvery routing decision and dial suppression: the activity, queue, campaign and agents it was about, the outcome and the reason, counts by reason, and queues with work due now that routing has gone quiet on.
High-wait interaction detailInteraction-level audit of customers who waited at least 60 seconds.
Queue abandonment analysisInbound queue offered, answered, abandoned, abandonment rate, and wait before abandonment.
Queue handle time analysisTotal, average, and maximum connected plus wrap-up time by queue.
Queue performance summaryInteraction volume, outcomes, answer rate, abandonment, ASA, and AHT by queue.
Queue service levelQueue service level calculated from answered-within-threshold interactions and eligible offered interactions.
Queue transfer performanceHandled interactions, transferred interactions, transfer events, and transfer rate by queue.
Queue usagePer-queue handled, answered, and abandoned volume, handle time, and current waiting depth.
Queue wait time analysisTotal, average, and maximum customer wait time by queue.
Transfer analysisTransfer volume, completion, destination type, result, and completion time.

Agent Performance​

ReportWhat it shows
Agent handle time analysisPer-agent handled volume, connected time, wrap-up time, and total handle time.
Agent inbound performanceInbound handled volume, outcomes, transfers, recording count, and handle time by agent.
Agent interaction volumeHandled, answered, failed, transferred, recorded, and average handle time by agent.
Agent occupancyBusy plus wrap-up time divided by available, reserved, busy, and wrap-up time.
Agent outbound performanceOutbound handled volume, outcomes, transfers, recording count, and handle time by agent.
Agent outcome performanceInteraction outcomes and average handle time by agent, ordered by failed volume.
Agent productivityPer-agent handled volume, talk time, average handle time, and completed activities.
Agent transfer performanceTransfer volume and supporting interaction metrics by agent.
Agent utilizationBusy plus wrap-up time divided by total observed signed-in time.
Agent wrap-up performancePer-agent wrap-up starts, completions, completion rate, average duration, and total duration.
Talk, hold, ring and queue waitTalk time with hold taken out, hold, ring time and missed offers by agent, and the real queue wait and abandons by queue, from the calls' recorded changes.

Workforce & Payroll​

ReportWhat it shows
Agent break and away analysisBreak count, total time, average duration, and longest duration by agent.
Agent time summaryObserved signed-in, available, busy, wrap-up, break, and other not-ready time by agent.
Campaign signed-in hoursObserved signed-in agent time attributed to campaign memberships.
Daily agent timecardDaily observed on-duty, productive presence, working, and break time by agent.
Payroll timecard inputsObserved on-duty, productive presence, break, meeting, training, and other not-ready time for payroll review; pay rates and schedules are not applied.
Presence reason breakdownObserved presence duration and interval count by status and reason.
Presence status durationTotal observed duration and share of signed-in time for every presence status.
Queue signed-in hoursObserved signed-in agent time attributed to queue memberships.
Ready versus not-ready timeReady, actively working, and not-ready time by agent.
Reconciled payroll timecardPer agent per day, signed-in time beside the time in each state to the second, with a check that flags every day that does not add up.

Billing & Usage​

ReportWhat it shows
Agent usage for billingInteraction counts and measured service time by agent for staffing, payroll, and chargeback support.
Channel usage for billingInteraction counts and measured service time by channel for service allocation and chargeback.
Daily usage for billingDaily interaction counts and measured service time for invoice period reconciliation.
Provider usage for billingInteraction counts and measured service time by communications provider for vendor invoice reconciliation.
Queue usage for billingInteraction counts, connected time, wrap-up, queue wait, transfers, and recordings by queue for invoice support.

Compliance & Audit​

ReportWhat it shows
Abandoned interaction detailInteraction-level audit of inbound customers who left before answer.
Agent activity timelineEvery agent state, offer, connection and call change in order, with start, end, duration and who made each change.
Agent presence auditDetailed auditable presence transitions with status, reason, and membership counts.
Agent recording coverageRecorded interaction volume and supporting performance metrics by agent.
Interaction detailOne row per interaction with routing, agent, provider, timing, and transfer details.
Long interaction detailInteraction-level audit of connected sessions lasting at least 15 minutes.
Recording coverageAnswered voice interaction recording coverage grouped by provider.

Technical & IT​

ReportWhat it shows
Call leg performanceProvider call-leg volume, answer state, status, and average duration for technical operations.
Failed interaction detailInteraction-level audit of failed communications.
Provider performanceInteraction outcomes and duration metrics grouped by executing communications provider.

CRM & Campaigns​

ReportWhat it shows
Campaign summaryPer-campaign completed-versus-pending progress across the activity inventory, with the pending records split by what the dialer can do with them right now.
Dialer queue inventoryWhat each campaign queue holds right now, by the dialer profile its items are stamped with, and why the records that are not being dialed are held back.
Subject inventoryPer-subject completed-versus-pending progress across the activity inventory.

Which report answers which question​

QuestionReport
How many calls came in and out, and how many were answered or abandoned?Call insights
Are calls sounding bad, for whom, and why?Call quality
How long do agents talk, hold and ring, and how long do callers wait?Talk, hold, ring and queue wait
What did each agent handle, and what is their average handle time?Agent productivity
How busy is each queue right now and over the period?Queue usage
How far along is each campaign or subject, and how many numbers were not in service?Campaign summary (see below), Subject inventory
How many of a campaign's pending records can be dialed right now, and why can the rest not?Campaign summary (see below)
What did an agent do, minute by minute?Agent activity timeline
Why is an available agent not getting calls, and how long has each agent waited?Agent availability and wait time (see below)
How much paid time did each agent spend in each state?Reconciled payroll timecard and the other Workforce & Payroll reports
Which dispositions are agents choosing?Disposition breakdown
Which numbers did the dialer call, and how did each call end?Dialer call detail (see below)
Is the dialer dialing, waiting for agents, out of work, or stuck?Dialer activity and health (see below)
What is waiting in each campaign queue right now, and why is it not being dialed?Dialer queue inventory (see below)
Why was a record not called, or why did an agent not get a call? Has routing stopped looking at a queue?Dialer decision log (see below)
How often did the AI hand a conversation to a person?AI handoff & containment
How many leads converted, from which source and list, and what is in the sales pipeline?Lead funnel, Lead conversion by source and list, Opportunity pipeline (see Leads, Accounts and Opportunities)
What did the store sell, and what did it keep after refunds? What is an average order worth? Which products, categories and countries sold most? How much tax did orders charge, and what did promotion codes take off?Sales, Sales by product, Sales by category, Sales by country, Tax on orders, Discounts on orders, Refunds under Commerce (see Carts and orders)
Who buys, how many come back, and how many checkouts end in a sale?Customers, Checkouts under Commerce
Which paid orders still have to ship, how fast does the store ship, and what is running out of stock?Orders to ship, Shipping times, Stock on hand, Stock movements under Commerce
Are buyers downloading what they bought, and what do they think of it?Downloads, Product reviews under Commerce

Agent availability and wait time​

Agent availability and wait time, under Queue & Routing, answers "why is this agent not getting calls?". It shows each agent as they are right now: how long they have waited for a call, the calls they took today, whether their workspace is really connected, anything stuck on them, and, for every queue and campaign they can work, whether they can be given work and why not. Use it when an agent says they are free but nothing comes through, when the live dashboard and the time reports disagree, or before you move people between queues.

The report is live: it ignores the Date range and reads everything as of the moment you click Show. "Today" starts at midnight in the site's time zone. Pick an Agent to look at one person.

Who is listed​

  • If you oversee queues or campaigns (they are on your own agent entitlement record), the report lists every agent who is entitled to, or signed in to, one of them. That includes agents the live dashboard leaves out, such as an agent who shows as Available but is signed in to nothing, or only to a queue you do not oversee.
  • If you oversee nothing, the report lists every agent.
  • If you pick an Agent, the report shows that agent, whoever oversees them.

Agents​

ColumnWhat it shows
PresenceThe agent's state now, with its reason, for example Break (Lunch). Busy means on a call.
Available since (UTC) and Idle timeFor an Available agent, when they last became free and how long ago that was. Routing offers work first to the agent who has been free the longest, by this time.
Last call assigned (UTC)When routing last gave the agent work.
Last call ended (UTC)When the agent's last call ended.
Calls todayHow many times the agent went on a call today.
Longest wait between callsThe longest stretch today the agent was ready for a call (Available, or being offered one) without getting one, including the stretch still running now.
Signed in toThe queues and campaigns the agent is signed in to, or Nothing.
Live sessionYes when the agent's workspace is connected and has checked in recently (within 90 seconds, unless your administrator changed it). No: offline, disconnected or no recent heartbeat means the workspace was closed, lost its connection or stopped checking in. No session means the agent has not opened their workspace. Routing only offers work to an agent with a live session.
Heartbeat ageHow long ago the agent's workspace last checked in.
On live dashboardWhether your live dashboard shows the agent, and if not, why: not signed in to any queue or campaign, or not signed in to a queue or campaign you oversee.
Stale-state flagsAnything stuck on the agent (see Stale-state flags). Shown in red.
History checkA note when the agent's state now and their recorded history disagree (see History check). Shown in red.

Why each queue or campaign is or is not giving work​

One row for every queue and campaign the agent is entitled to or signed in to.

ColumnWhat it shows
Queue or campaign and TypeThe queue or campaign, and which one it is.
EntitledWhether a manager has allowed the agent to work it.
Signed inWhether the agent is signed in to it now.
WaitingHow many items are waiting in it.
Eligible nowYes when the agent can be given work from it right now.
Why not eligibleEvery reason the agent cannot be given work from it, or, when they can, why they still may not be getting any. Shown in red when the agent is not eligible.
Routing detailWhen work is waiting and the agent passes the checks above, what routing itself says about the agent for the next waiting item, in its own words: for example a missing skill, their place in the longest-idle line, or that they already had the call.

The reasons in Why not eligible are the checks routing makes, in the same order:

ReasonWhat it means and what to do
The queue no longer exists, The queue is turned off, Closed by its business hoursNobody gets work from this queue now. Check the queue's settings or its business hours.
Not entitled to this queue (or campaign)A manager has not allowed the agent to work it. Change the agent's entitlements.
Not signed in to this queue (or campaign)The agent is allowed to work it but did not sign in to it. Ask them to sign in to it from their workspace.
No live sessionThe agent's workspace is closed, disconnected or has stopped checking in. Ask them to reopen or reload it.
The live session is not signed in to itThe workspace the agent has open is not signed in to this queue. Ask them to sign in again.
Not Available (presence is ...)The agent is on a break, on a call, in wrap-up or in another state that does not take work.
At capacity (x/y active interactions)The agent is already handling as many interactions as they are allowed at once.
Routing passes this agent over for the next waiting itemThe agent passes every check, but routing chose not to offer them the next item; the Routing detail says why, for example a missing required skill, or that they declined the call or transferred it away, so it goes to someone who has not had it first.
None: next in line for the waiting workRouting will offer the agent the next waiting item.
None: eligible, but another agent is ahead in lineThe agent can take work, but someone else gets the next item first.
None, but no work is waitingThe agent can take work; there is simply nothing waiting.
None, but no waiting item can be worked nowItems are waiting, but none can be offered yet, for example campaign records scheduled for later.

An agent with no queue or campaign at all shows one row: Not entitled to or signed in to any queue or campaign.

Stale-state flags​

A flag means something is holding the agent in a state that nothing real is behind. For an agent the live dashboard shows, Free agent in the More menu of their card releases it.

FlagWhat it means
Available with no live sessionThe agent is marked Available but their workspace is not connected, so routing passes them over. The time reports still count them as Available.
Unresolved soft-phone call recordA call is still open on the agent's soft phone although the phone service no longer has it, cannot find it, or the browser that placed it is gone. This is how an agent can show On a call with nobody on the line.
Open interaction although the provider reports the call endedA Contact Center call is still open although the phone service says it ended.
Busy with no live interaction and Reserved with no live interactionThe agent's state says they are on a call or being offered one, but there is no call or offer behind it.
Held reservation that no offer or call backsThe agent is still holding an offer that is no longer ringing.
Work assigned with no offer or call behind itWork is still assigned to the agent although no offer or call is in progress.
Holds reservation ...An offer may be ringing for the agent right now. Not a problem on its own; it turns into a held-reservation flag if it stays.
Stale work not checkedStuck calls and states are found by the Contact Center Supervision & Live Dashboard feature, which is off. Ask your administrator to turn it on.

History check​

The Workforce & Payroll reports, such as Agent time summary, count an agent's time from the state changes the system recorded, up to now when no later change is recorded. The History check column says when that record and the agent's state now disagree:

  • No sign-out is recorded after the change to ... so the time summary counts this agent as ... up to now, but the agent has no live session. The agent left without signing out (for example they closed the browser), so the time reports keep counting them, for example as Available for many hours, although nobody is there.
  • The profile says ..., but the last recorded change is to ... The agent's state now is not the one the record ends with.
  • No state change is recorded for this agent. The time reports show no time for an agent who is signed in now.

Find out why an agent is not getting calls​

  1. Open Reports > Queue & Routing > Agent availability and wait time, pick the Agent and click Show.
  2. In Agents, check Presence, Live session and Stale-state flags. A red flag usually is the answer: use Free agent on the live dashboard, or ask the agent to reload their workspace.
  3. In Why each queue or campaign is or is not giving work, find the queue or campaign that has work Waiting and read Why not eligible and Routing detail.
  4. If On live dashboard says No, the row says why the board does not show the agent.

Dialer call detail​

Dialer call detail, under CRM & Campaigns, lists the phone numbers the dialer called, one row per call attempt, with how each one ended. Use it when you want the numbers behind a count: every number that ended as No answer today, or everything a campaign dialed this week.

ColumnWhat it shows
Phone numberThe number that was dialed.
ContactThe contact the number belongs to.
CampaignThe campaign the call was made for.
Last dispositionThe disposition the attempt ended with. A disposition that has since been deleted shows as (Unknown disposition); an attempt that has not ended yet shows (No disposition).
AttemptsHow many times this contact had been tried, counting this attempt.
CompletedWhen the attempt ended, in the site time zone. Empty while the attempt is still scheduled or being dialed.
AgentThe user the attempt was handed to, or (Unassigned).
StatusThe status of the attempt, such as Completed, Scheduled or Dialing.

How it works:

  • The report opens with Source set to Dialer, so it shows dialed work only. Change Source to see other work, or pick All sources.
  • The Date range covers the time an attempt ended. An attempt that has not ended yet is listed under the time it is scheduled to be dialed.
  • Filter by Campaign group, Campaign, Channel, Source, Status and Disposition. Tick several dispositions, for example No answer and Busy, to list the numbers that ended either way.
  • Rows are listed newest first, 100 to a page. The line above the table says which rows you are looking at; type a page number in Page and click Show to move to another page.
  • Export CSV (or Export Excel (.xlsx)) downloads every matching row, not only the page on screen, so the list can be worked outside the system or loaded again later.

Dialer activity and health​

Dialer activity and health, under Operations, tells you what the dialer is doing for each campaign it dials automatically, and what it did over the period you pick. It appears when the Contact Center Paced Dialing feature is on.

A dialer that places no calls can be in three very different situations, and the report keeps them apart:

StateWhat it meansWhat to do
StalledRecords are waiting but the dialer has not finished a pass over the campaign for several minutes (five, unless your administrator changed it). The report shows the warning Due work is waiting but no pacing cycle has completed for N minutes.Tell your administrator: the dialer has stopped, not run out of work.
Idle: no agent availableThe dialer keeps checking the campaign and finds records it may call, but no agent is free to take the call.Sign more agents in to the campaign, or bring agents back from a break.
Not pacing: pacing lock not acquiredRecords are waiting, but the dialer could not take the lock it needs to pace the campaign, so every pass skips itself. The report shows a warning naming the campaigns and since when.Tell your administrator: the dialer is not running, and the cause is the lock, not the data.
Nothing to call / Nothing dueThe dialer keeps checking and finds nothing it may call right now: the campaign has no records waiting, or they are scheduled for later or waiting out their retry delay.Nothing, unless you expected records to be due. Load more records if the campaign has run out.

Other states are Dialing (the last pass placed calls), Holding back (the dialer chose not to call: the compliance check refused the numbers, the abandoned-call cap was reached, or calls already ringing cover the free agents) and Starting (records arrived a moment ago).

The report has these sections:

SectionWhat it shows
Dialer right nowThe overall state, how many campaigns have records waiting, how many have a pacing lock not acquired, and how many are stalled, idle, holding back, dialing or have nothing due.
Campaign queuesOne row per campaign: its state, when the dialer's last pass started and finished, how it ended (for example Placed 2, No agents or Nothing due, with how many passes in a row ended that way), why, the Last call placed and the Last call assigned (when, which agent, which record), and how many passes, calls and routing decisions there were in the period.
Dialer profilesOne row per dialer profile: its mode, its last pass, the last call placed, and the calls placed, answered and abandoned and the attempts suppressed in the period.
Calls per hourA chart of calls placed, answered by a person and abandoned, hour by hour (day by day for a period longer than a month).
Campaign routing decisions per hourA chart of how often a record was routed to an agent and how often no agent was available.
Suppressed attempts by reasonHow many calls the compliance check refused, by reason: do not call, the national do-not-call registry, outside the calling window, number not in service, compliance check unavailable, abandonment rate cap reached, out of attempts, waiting out the retry delay and no number to dial.

The state and the Last cycle columns always describe right now, whatever date range you pick; the counts and charts cover the date range. Times are shown in the site's time zone. The same state is shown as a banner on the live dashboard.

Dialer queue inventory​

Dialer queue inventory, under CRM & Campaigns, shows what the dialer holds right now: what is waiting in each campaign's queue, which dialer profile those records are stamped with, how many can be dialed now, and why the rest are held back. Use it when a campaign has pending records and agents are available but nothing is being dialed. It answers on one screen, without reading logs.

The report always shows the present. The Date range does not change it; the times it shows are in the site's time zone. Filter it by Campaign group and Campaign.

The Right now cards at the top add up every row: Campaign queues, Waiting, Reserved, Assigned, Pending, Dialable now, Held back, Not in any queue and Not explained.

The Campaign queues by stamped dialer profile table has one row for each campaign queue and dialer profile its records are stamped with, and one row for each campaign's pending records that are not in its queue at all.

ColumnWhat it shows
CampaignThe campaign.
QueueCampaign queue for records in the campaign's queue, or Not in the campaign queue for pending records that are not in it.
Stamped dialer profileThe dialer profile the dialer uses for these records. It is chosen when the records are loaded. (None stamped) means the records carry none; (No longer exists) means the profile was deleted. A turned-off or deleted profile is shown in red.
Mode and Profile onThe stamped profile's dialing mode, and whether it is turned on.
Activity dialer profileThe dialer profiles the activities themselves carry, with how many carry each.
Waiting, Reserved, AssignedHow many of the queue's records are waiting, offered to an agent, or with an agent.
Oldest waitingWhen the record that has waited longest entered the queue.
PendingHow many of these records have not been started yet.
Source / type / channelWhere the pending records came from, whether they are worked by people or automatically, and their channel, with a count for each combination.
Dialable nowHow many pending records the dialer could dial right now.
Held back and Held back becauseHow many cannot be dialed now, and why: the dialer profile is turned off or no longer exists, scheduled for later, waiting out the retry delay, out of attempts, outside the calling window, do not call, number not in service, or another compliance reason. Not explained counts the records past the first 2,000 of a campaign, which are counted but not checked one by one.
Queue pacingWhether the system is dialing the queue. The system paces a queue by the record at the front of it, so a turned-off or deleted profile there stops the whole queue, even when the records behind it are stamped with a profile that is on.
FlagsProblems to fix, in red: records stamped with a different dialer profile than their activity carries, pending records that are in no queue, and a stamped profile that is turned off or no longer exists.
Last dialedWhen the queue last placed a call.

The Campaign summary report splits the same pending records the same way (see below), so the two reports agree. This report's Held back counts every record that cannot be dialed now; the Campaign summary shows scheduled, not-in-a-queue and assigned records in columns of their own, so its Held back is what is left.

The Why records are held back table lists each reason again, with the Count of records and, for records that wait by themselves (scheduled for later, retry delay), when the first becomes due.

What to do about a flag:

  • The stamped dialer profile is turned off: turn the profile on (see Dialer Profiles), or load the records again under a profile that is on (see Dialer loads).
  • The stamped dialer profile no longer exists: load the records again under a profile that exists.
  • Pending activities in no queue: load the records into the campaign again so they are queued.
  • Stamped differently from their activity: the dialer uses the stamped profile. Load the records again if they should be dialed under the activity's own profile.

Campaign summary​

Campaign summary, under CRM & Campaigns, shows how far along each campaign is: how many of the records created in the date range are completed, pending, in progress, failed or cancelled, and how many numbers were not in service. Its pending records are also split by what the dialer can do with them right now, so you can see per campaign how many can be dialed and why the rest cannot.

Filter it by Campaign group, Campaign, Channel, Source, Status, Interaction type (Manual or Automated), Dialer profile and Queue state.

  • Dialer profile keeps the records whose activity carries the profile and the records whose queue item is stamped with it, because the dialer dials a record under the profile stamped on it. Turned-off profiles are listed too, marked (turned off).
  • Queue state keeps only the pending records in one state: Dialable now, Held back, Scheduled for later, Not in any queue or Assigned to a user. Records that are not pending have no queue state, so they drop out.

The Campaigns table has these columns beside the progress columns (Total, Completed, Pending, In progress, Failed, Cancelled, Not in service, Attempts, Completion):

ColumnWhat it shows
Dialable nowPending records the dialer could dial right now.
Held back and Held back becausePending records that cannot be dialed now for any other reason, with the reasons: the dialer profile is turned off or no longer exists, waiting out the retry delay, out of attempts, outside the calling window, do not call, number not in service and the other compliance reasons.
Scheduled for laterPending records that wait for a time set on them, such as a follow-up after Try again.
Not in any queuePending records that are in no queue, so nothing will dial them until they are loaded again.
Assigned to a userPending records a user works from their own list.
Not explainedQueued records past the first 2,000 of a campaign, which are counted but not checked one by one.
Attempts distributionHow many of the campaign's records have been tried 0, 1, 2, 3, 4, or 5 or more times.
Last attemptWhen a call was last placed for one of the campaign's records.
Next dueWhen the first record that waits for a time becomes due.
Stamped dialer profileThe dialer profiles stamped on the campaign's queued pending records, with how many carry each.

Dialable now, Held back, Scheduled for later, Not in any queue, Assigned to a user and Not explained always add up to Pending. Pending records that belong to no campaign are not split. The split shows where the records the date range covers stand now, whatever the date range; with a date range that covers every record, it matches the Dialer queue inventory report.

The Why pending records are not dialing table lists every reason a campaign's pending records cannot be dialed now, with the number of records and, for records that wait for a time, when the first becomes due.

Dialer decision log​

Dialer decision log, under Queue & Routing, lists every decision routing and the dialer made about queued work: each time routing looked for an agent for a record, and each time the dialer refused to call a record. Use it to answer "why was this record not called?" or "why did this agent not get that call?" without asking for the system logs.

MenuReports > Queue & Routing > Dialer decision log
PermissionView Contact Center reports
FeatureContact Center Work Distribution and Reports. Suppressions are listed when the Contact Center Outbound Dialer is on.
Can't find it?

What you see depends on your role. If the menu, a button or a setting on this page is missing, ask your administrator to give you the permission listed above or to turn on the feature. Only administrators can turn features on and change site settings.

See the decisions made about one record or one agent​

  1. Open Reports > Queue & Routing > Dialer decision log.
  2. Set the Date range.
  3. To see one record, type its activity ID in Activity ID. You find the ID in the address of the activity's page.
  4. To see one agent, pick them in Agent. The report then lists every routing decision that considered or chose the agent, and every dialer refusal of a call that was reserved for them.
  5. Click Show. The Decisions table lists the newest decisions first, with the reason for each.

You can also narrow the report by Campaign, Queue and Reason. Filters combine.

What the report shows​

Summary counts the decisions in the period: all of them, the routing decisions, how many assigned work and how many did not, the dialer's suppressions, and how many activities they were about.

Decisions by reason counts the decisions of each kind (Routing or Suppression) by reason, the most frequent first, with when each reason was last seen.

Queues with work due now lists each queue and campaign that has work waiting that could be handed out now, with when routing last made a decision for it. Routing looks at a queue about once a minute, so a queue whose Status says No routing decision in the last 15 minutes (or the time your administrator set) is not being looked at, and its work is stuck. This section describes the queues as they are now, whatever date range you picked. It is shown when no Agent, Activity ID or Reason is picked.

Decisions has one row per decision:

ColumnWhat it shows
Last made (UTC)When the decision was last made.
First made (UTC)When it was first made.
TimesHow many times in a row routing made exactly this decision. While a queue has work and nobody can take it, routing makes the same decision every minute; the report shows those as one row with the count, instead of one row per minute.
KindRouting (routing looked for an agent) or Suppression (the dialer refused to call).
QueueThe queue, or Campaign: name for a campaign's own queue.
CampaignThe campaign the record belongs to.
ActivityThe ID of the activity (the record) the decision was about.
OutcomeAssigned, Not assigned or Suppressed.
ReasonWhy: for example No agents available, No available agent matched the routing policy, Do not call or Outside the calling window.
AgentThe agent routing chose, or the agent the suppressed call was reserved for.
CandidatesFor routing: every agent routing considered, and for each one that could not take the work, why not (for example At capacity or a missing skill).
DestinationFor a suppression: the number that would have been dialed.
DetailsFor a suppression: the dialer's explanation.

The screen lists the 500 most recent decisions; Export CSV and Export Excel (.xlsx) list up to 10,000.

Tips:

  • A queue that shows No routing decision while it has work due is the first place to look when nothing is dialing. Check that agents are signed in to it on the Live dashboard.
  • A campaign that uses predictive over-dialing places some calls without asking routing first, so it can show as quiet while those calls are in progress.

Omnichannel reports​

The omnichannel reports read your CRM activities (the calls to make, texts to send and follow-ups), the campaigns and dispositions they carry, and your leads and opportunities. Each one needs View Omnichannel reports, which administrators and supervisors have by default, and so does anyone who may manage activities. They come with Omnichannel Management; the three lead and opportunity reports also need Omnichannel CRM. They sit in the categories below, and most are under CRM & Campaigns.

The filters they share​

The activity reports offer Date range, Campaign group, Campaign, Channel (Phone or SMS), Source (Automatic, Callback, Dialer, Inbound or Manual), Status and Disposition, and you can tick several dispositions at once. Dialer call detail opens on the Dialer source and adds a page picker. Lead funnel, Lead conversion by source and list and Opportunity pipeline use the Date range only.

An activity belongs to the period in which it was created, except where a report says otherwise: Disposition breakdown and AI handoff & containment place an activity by when it was completed, and Dialer call detail by its completion time, or by its scheduled time while it is open. Activity backlog and Activity aging ignore the start of the range and list all work still open that was created by its end. Daily user productivity groups by the day an activity was completed in the site time zone. A row of Not set means the activity has no value for the grouping, such as no assigned user or no recorded creator.

The rows show the source as stored, so a dialer activity appears as PreviewDial, PowerDial, ProgressiveDial or PredictiveDial while the Source filter offers Dialer for all four.

Volume and completion​

ReportCategoryWhat it answers
Activity summaryOperationsHow many activities were created, how many are completed, pending, in progress, failed or cancelled, the completion rate, and the daily trend. Bars break the same activities down by source, channel and status.
Campaign performanceCRM & CampaignsThe same counts for each campaign, and again for each campaign group.
Disposition breakdownCompliance & AuditHow the activities completed in the period were dispositioned, and each disposition's share.

Backlog and age​

ReportCategoryWhat it answers
Activity backlogQueue & RoutingHow much work is still open: the open, unassigned, overdue and reserved counts, and the open work by status.
Activity agingQueue & RoutingHow old the open work is, in bands from under an hour to over seven days, with the unassigned and overdue count of each band.
Overdue workload by userAgent PerformanceWho holds the overdue work: the count per person, how much is unassigned, and the average and maximum age.

Workload by group​

These reports share one table, with the total, the completed, in progress, pending, failed and cancelled counts, the completion rate and the average attempts of each group. Only the grouping changes.

ReportCategoryGrouped by
Activity source performanceOperationsWhere the work came from: manual, automatic (an AI profile), a callback, an inbound call or a dialer mode.
CRM channel performanceOperationsChannel: Phone or SMS.
Activity kind performanceOperationsKind of work, such as a call or a text.
Contact type workloadCRM & CampaignsThe type of record the activity is about, such as a Lead or a Contact.
Activity assignment performanceQueue & RoutingAssignment status, such as Assigned, Available or Released.
Activity urgency performanceQueue & RoutingUrgency.
Activity attempt analysisOperationsThe number of attempts: how many activities needed one, two, three or more, and how many of those completed or failed.
Scheduled completion performanceOperationsWhether an activity was completed by its scheduled time or late, with the average difference.

People​

ReportCategoryWhat it answers
Assigned user performanceAgent PerformanceEach person's activities, outcomes, completion rate and attempts.
User completion timeAgent PerformanceHow long finished work took from creation: the average, median and maximum for each person.
Daily user productivityAgent PerformanceThe same for each person and each day, with the attempts.
Activity creation by userCompliance & AuditWho or what created the work and how it ended, for audits.

Campaigns, customers and addresses​

ReportCategoryWhat it answers
Campaign source mixCRM & CampaignsFor each campaign, the activities, completed, failed and completion rate by source.
Campaign channel mixCRM & CampaignsThe same by channel.
Campaign disposition mixCRM & CampaignsThe same by disposition.
Campaign attempt performanceCRM & CampaignsThe same by number of attempts.
Customer workloadCRM & CampaignsOne row per customer: how many activities they received, how they ended, and the attempts.
Address usageTechnical & ITThe same for each address that handled the work, such as a sales line or a text line.

Dialer and AI​

ReportCategoryWhat it answers
Dialer call detailCRM & CampaignsWhich numbers the dialer worked: one row per number with its contact, campaign, last disposition, attempts, completion time, agent and status. It shows 100 rows a page, and an export includes every row.
AI handoff & containmentCRM & CampaignsOf the automated conversations completed in the period, how many the AI contained and how many it passed to a live agent, the containment and escalation rates, the average time to escalate, and the reasons.

Leads and deals​

ReportCategoryWhat it answers
Lead funnelCRM & CampaignsThe leads created in the period by the status they have now, the share of each, and how many converted.
Lead conversion by source and listCRM & CampaignsFor each lead source and each list, the leads, how many converted, the rate and the average time to convert.
Opportunity pipelineCRM & CampaignsThe open opportunities by stage with their amount and weighted amount (the amount times the stage's probability), and for deals closed in the period the win rate and the amount won.

Build your own from the same data​

The Report Builder reads the same records. The Omnichannel data source offers Activities, Dispositions, Campaigns, Campaign groups and Activity batches; contacts, leads, accounts and opportunities are content items, under Content items. The Messaging data source offers Conversations and Messages, including each outbound text's delivery status but never its text. Related data sets are joined for you.

The report catalog in the Technical Manual lists every Contact Center and CRM report with its filters, columns and exact formulas.