Reading Agents analytics in Console

After agents are live, Console Agents is where you monitor performance beyond the company Dashboard heroes.

List tabs

At company scope (the Agents area without a single flow selected):

• Agents — inventory of web and message flows.
• Breakdown — LinkedIn outreach metrics rolled up across all message flows for the company.
• Time series — trends over time.
• Cohorts — segment comparisons.

Agent detail

Open an agent for Breakdown, Time series, and Cohorts. Message flows also expose Contacts for that flow.

LinkedIn Breakdown (company or single agent)

On Breakdown for message flows you see three stacked sections. The selected date range applies only to outbound actions; funnel counts reflect current enrollments (not the date range).

Outbound actions — selected time frame

KPI tiles count LinkedIn steps completed in the period: connects sent, connections accepted, DMs, InMails, profile views, follows, post likes, invite withdrawals, send failures, and paused runs. Use this to audit what actually happened in the window you filtered.

Planned actions — next 7 days

A table with one row per calendar day (starting today in Europe/Oslo) and columns for each planned LinkedIn step type: Connect, Message, InMail, View profile, Follow, Like, and Withdraw, plus a Total column.

• Overdue scheduled sends count on today.
• This table is independent of the date filter — it always shows the rolling next seven days.
• Timed waits that exist only as in-flight timers (without a stored schedule row) are a lower bound.

Below the table, Awaiting first action counts enrolled contacts with no outbound milestone yet and no due wake in the next seven days.

On the company Breakdown tab, outbound actions, planned actions, and funnel totals are rolled up across all message flows. A contact enrolled in two flows can appear twice, matching separate enrollments.

LinkedIn outreach totals — all time

The funnel shows target contacts, enrolled, connections sent, accepted, messages sent, and replies as current enrollment state, not limited to the date range. Conversion rates between steps help you spot drop-off in the live pipeline.

Flow Sessions and Unique Users

These two KPIs share a name across flow types, but what starts a session differs.

Web flows

Metric	Meaning
Flow Sessions	Each time someone opens or begins the flow experience (comparable to an “open”).
Unique Users	Distinct people across those sessions in the selected date range. Deduplicated for the whole period—not summed day by day.

LinkedIn message flows

Metric	Meaning
Flow Sessions	Each contact with successful LinkedIn activity in the period: profile view, connection request, DM, or InMail.
Unique Users	Distinct contacts with that outreach activity in the range (also period-deduplicated).

Enrollment alone does not create a session. Adding someone to a message flow (or parking them until a scheduled send window) is not LinkedIn activity. If enrolled is high and Flow Sessions is low, contacts are waiting or deferred—not yet viewed/connected/messaged. Check Planned actions and Awaiting first action on Breakdown for when sends are expected.

The outreach funnel on Breakdown (target, enrolled, connects, accepts, replies, and so on) is separate from Flow Sessions / Unique Users. Expect enrolled ≫ sessions until outbound actions succeed.

Interactions and other heroes

• Interactions — web: engaged sessions (meaningful participation). LinkedIn: connection accepts or replies (inbound user actions).
• Smart Leads — web captures, or qualified positive LinkedIn replies.
• Smart Clicks — promo / qualified link conversions.
• Replies Waiting — Inbox threads that need an operator.

Studio analysis

For path-level insight, open the agent in Studio Design → Analysis for heatmaps and path performance. Recommendations in Studio help operators improve flows without guessing.

Related

• Web flow vs message flow
• FAQ: Dashboard KPIs
• Reading and Analyzing the Dashboard
• Understanding the Specific Flow Statistics Dashboard