Skip to main content

Tiles and metrics

A tile is a declarative description: which metric, over which time window, broken down how, drawn as which chart, with which filters and limits. The server validates every tile against the metric catalog, so a tile that cannot work is refused with a reason instead of showing wrong numbers. The AI tile builder fills in the same description (see AI tiles).

Tile options​

OptionValues
MetricUp to four metrics per tile (one for most charts). See the tables below.
Windowlive, 15m, 1h, today, 24h, 7d.
Break down bynone, queue, channel, agent, activity, state, time, campaign, outcome.
Time bucket5 min, 15 min, 30 min, 1 hour, 1 day (for breakdowns by time).
Split byqueue or channel, for stacked bars and heatmaps over time.
Compareyesterday or last week, overlaid as a dashed grey series on time charts.
Filtersqueues and channels; dialer tiles filter by campaign instead.
Thresholdswarning, critical and optional good limits, and an alert delay. See Alert colours.
Extrassparkline, delta against the previous period, max rows, accent colour, title and subtitle.

Chart types​

ChartUse
KPIOne big number, optionally with a sparkline and a delta.
GaugeOne number on a dial.
BulletOne number against its target, with warning and critical bands. Preferred over a gauge for service level.
GoalProgress towards a daily target (set the target on the tile).
Bar, stacked barValues per queue, channel, agent or time bucket.
Line, areaValues over time.
DonutPart of a whole, per dimension.
State barAgents (or interactions) split by state, activity or channel in one bar.
HeatmapOne historical metric by time and queue or channel.
TableValues per dimension; also the queue table and the campaign table.
Agent gridOne card per agent with state and time in state.
LeaderboardAgents or queues ranked by a metric.
Waiting listThe contacts waiting right now, oldest first, with live timers.
StatusBusiness calendar open or closed, and the next change.
SummaryThe AI shift summary.
Text, clockA note, or the time (with up to four extra timezones).

Rules a tile must follow​

  • Charts that show one number (KPI, gauge, bullet, goal) need Break down by: none.
  • Line and area charts need a breakdown by time and a window other than live.
  • Donut, leaderboard and state bar charts need a dimension (queue, channel, agent, activity, state, campaign or outcome).
  • Live and historical metrics do not mix in one tile, except on a time breakdown.
  • Dialer and contact center metrics do not mix in one tile.
  • Composite tiles (queue table, agent grid, waiting list, calendar status, AI summary, campaign table) hold one metric only.
  • Channel filters work with historical metrics, active interactions and the waiting list. Other live numbers come from TaskRouter per queue and cannot be split by channel.
  • Queue metrics (offered, abandons, service level, ASA, longest wait) have no per-agent breakdown, because a queue visit has no agent.

Live metrics​

Live metrics come from TaskRouter real-time statistics, polled every 5 seconds while a board is watched, or from open tasks seen through Event Streams.

MetricMeaning
tasks_waitingTasks waiting in queue right now (pending and reserved). Also as a trend over 1h, today, 24h.
longest_waitAge of the oldest waiting task right now. Also as a trend.
tasks_assignedTasks an agent is working on right now.
tasks_wrappingTasks in wrap-up right now.
agents_availableAgents ready for a new task (available activity, not on a task). Also as a trend.
agents_on_taskAgents working on or wrapping up a task. Also as a trend.
agents_logged_inAgents not in an offline activity.
agents_by_activityLogged-in agents per TaskRouter activity, or per state (on task, wrapping, available, unavailable).
occupancy_nowAgents on task or wrapping ÷ (on task + wrapping + available), right now.
interactions_activeTasks accepted by an agent and not finished yet, by channel or queue.
queue_statusThe queue table: waiting, longest wait, available agents, handled and abandoned today, today's service level and ASA.
agent_statusAgent cards: state, time in state, handled today. Break and wrap-up limits colour a card that has been in a state too long.
waiting_listThe tasks waiting now, oldest first, with queue, channel and a live timer.
calendar_statusWhether a business calendar is open now and when that changes. Pick the calendar on the tile. See Agent Workspace.
ai_summaryA short AI-written summary of today's numbers. See AI tiles.

"On task" and "wrapping" come from open tasks rather than from the TaskRouter activity, because a Flex agent stays in an available activity while working.

Historical metrics​

Historical metrics are the reports' metrics, computed over the same facts and counted when each queue visit or agent leg starts, in the board's timezone. Windows: 15m, 1h, today, 24h, 7d.

MetricMeaning
offeredInbound contacts that entered a queue. Outbound tasks and transfer legs are excluded.
handledAgent legs completed (talk and wrap-up done).
abandonedInbound contacts that hung up in the queue after the queue's short-abandon threshold.
short_abandonedInbound contacts that hung up within the short-abandon threshold. Not counted as abandons or in service level.
abandon_rateAbandoned ÷ (answered + abandoned).
service_levelAnswered within the queue's threshold ÷ (answered + abandoned).
asaAverage speed of answer: mean queue wait of answered contacts.
ahtAverage handle time: talk + wrap-up per handled agent leg (outbound also counts ring time).
avg_talkAverage talk time per handled agent leg.
avg_wrapAverage wrap-up time per handled agent leg.
max_waitLongest queue wait to answer or hang-up.
transfersTasks created by transferring a contact.
missedReservations an agent did not take: timed out or rejected.
wait_distributionAnswered vs abandoned contacts per wait band (0–10 s up to 5 min and more), as a histogram.

Service level thresholds, targets and the short-abandon threshold are set per queue in Service level settings.

Dialer metrics​

Dialer metrics come from the outbound dialer, not from TaskRouter. They are filtered by campaign, never by queue or channel. See Outbound Dialer.

MetricWindowBreakdownsMeaning
dialer_agentslivestate, campaignLogged-in dialer agents, by state: on a call, wrapping, free, away.
dialer_agents_freelivecampaignDialer agents free for the next call.
dialer_agents_on_calllivecampaignDialer agents with a call ringing to them or talking.
dialer_calls_activelivecampaignDialer calls in flight (dialing, waiting for an agent, connected).
dialer_abandon_livelivecampaignShare of the last 100 answered calls that did not get an agent within the wait target: the pacer's own abandon number. Default limits 3 / 5 %.
dialer_leads_remaininglivecampaignLeads still to call: ready, being dialed, due and owned callbacks.
dialer_callbacks_duelivecampaignScheduled callbacks whose time has come and that are not dialed yet.
dialer_campaigns_runninglive—Campaigns running now.
dialer_campaignslive—A table of every active campaign: status, agents, calls in flight, abandon against target, today's dials, contact rate, lead progress, callbacks due and the calendar closure.
dialer_dials15m … 7dcampaign, time, outcomeCalls placed. By outcome: connected, no answer, voicemail, busy, abandoned, failed.
dialer_connects15m … 7dcampaign, time, agentCalls that reached a person and an agent.
dialer_contact_rate15m … 7dcampaign, timeConnected ÷ dials.
dialer_abandon_rate15m … 7dcampaign, timeAnswered calls that reached no agent ÷ calls answered by a person.
dialer_avg_talk15m … 7dcampaign, time, agentAverage talk time of connected calls.
dialer_connect_wait15m … 7dcampaign, timeAverage silence a person hears after answering until an agent is on the line.
dialer_messages15m … 7dcampaign, outcomeSMS and WhatsApp campaign messages sent. By outcome: delivered, read, replied, failed, opted out.

In the campaign table the abandon cell turns yellow above the campaign's target and red at more than 2 points above it. SMS and WhatsApp campaigns show messages sent instead of dials.