Home Analytics and coaching

Analytics and coaching

Read your numbers, set targets, and listen to live calls.
By Swades Admin
• 3 articles

Reading your analytics

Analytics is one screen with a filter bar and a set of tabs. The filter bar sets the time range, the lists, the agents, the timezone and the conversation threshold; every tab respects it. The conversation threshold This is the most important setting on the page and the one people miss. A conversation is a connected call that lasted longer than the threshold. Options are 30 seconds, 1 minute, 2 minutes (default), 3 minutes. Your choice is saved to your account. Change it and every conversation number on the screen changes with it. Pick one that matches your sale — a 30-second threshold for a quick qualification call, two or three minutes for a consultative one — and then leave it alone, because a moving threshold makes week-on-week comparison meaningless. The summary bar Connects, Conversations, Meetings across the selected range. Agent analytics A table of every rep, with column definitions the app spells out: | Column | Definition | | --- | --- | | Dials | Total number of calls in the selected range. | | Dials per day | Dials divided by calendar days in the range. | | Connects | Calls that successfully connected. | | Connect rate | Connects ÷ Dials. | | Conversations | Connected calls that exceeded the conversation threshold. | | Conversation rate | Conversations ÷ Connects. | | Meetings | Calls dispositioned as Meeting Booked. | | Meeting rate | Meetings ÷ Connects. | | Dial Time | Time spent dialing and waiting for connection. | | Talk Time | Time spent in conversation. | | Total Time | Time on the system — call plus wait plus wrap. | | Payable Time | Billable time, from actual call duration. | | Avg wait | Average wait time between calls. | | Avg wrap | Average post-call work time. | | Avg duration | Average call duration. | | Availability % | Share of time the agent was available for calls, excluding wait and wrap. | | Talk % of Payable | Share of payable time spent on calls. | Columns are selectable, and the table exports to CSV. Connect rates Grouped two ways: - By number — grouped by the caller ID the call was placed from. This is how you spot a burned number. - By area code — grouped by the area code of the number dialed, so where the prospect is. The state the caller ID is homed in is shown too. Connect % is connects divided by dials. Conversation % is calls that reached the conversation threshold divided by connects — the same definition as the Agents tab. Set Min dials and Min connects to stop tiny samples dominating the table. Exports to CSV. Dispositions The distribution of outcomes. Read it against what each disposition means — a pile of Gatekeeper is a different problem from a pile of No Answer. Call volumes and the heatmap Call Volumes is dials over time. The Call Performance Heatmap is day-by-hour, in a timezone you select. Use it to find the hours that actually connect, then move your sessions there. Most teams discover their best hour is not the one they dial most. List performance Per list: Total Calls, Connected, Connect Rate, Conversations, Conv. Rate and Avg. Duration. This is how you decide which source of leads to buy more of. Speed to lead How long between a lead being created and first dialed. Shows the total first dialed, the average, and a median — half of leads were first dialed faster, half slower — plus a distribution you can click to filter the lead list underneath. Median is the honest number here; a handful of leads dialed three weeks late will wreck the average and tell you nothing. Conversion funnel Total Calls → Connected → Conversation → Interested → Qualified. The step with the biggest drop is your week's work. User trends One metric over time per agent — conversations, connect rate or conversation rate — with a best day per agent, in a timezone you pick. Voicemails How many drops you left. Read alongside the callback rate; if nobody ever calls back, the script is wrong. See Create a voicemail drop. Beta version Use New Analytics (Beta) switches to the newer analytics implementation. Numbers can differ between versions; compare like with like.

Last updated on Sep 29, 2026

Coaching insights and KPI targets

Coaching insights The Coaching Insights tab analyses your call data and produces: - Key Insights — what the calls show. - Areas for Improvement. - Recommendations. - Common Objections — a table of the objection, how often it came up, and its category. If it says "No coaching insights available — insights will appear here once more call data is collected", there is not enough recorded conversation yet. Recording must be on for this to work; see Call recording and consent. Regenerate re-runs the analysis against the current filter range. Using it honestly The objections table is the most immediately useful part: it tells you what your market actually says no to, ranked. Take the top objection, write a response into the list script, and look again in two weeks. Treat the insights as a prompt for a conversation with a rep, not as a verdict on one. It is reading transcripts, not sitting in the room. KPI targets Targets lets you set per-agent goals, in a timezone you choose. 1. Select an agent, or use Set targets for the editor. 2. Enter the targets. 3. Also apply to other agents copies the same targets across the team, which is the quick way to set a common baseline. Targets then show up against actuals so a rep can see where they stand without asking anyone. Setting numbers that mean something Derive them from your own funnel rather than from a benchmark: - Look at List performance for your realistic connect rate. - Look at the conversion funnel for how many connects become conversations, and how many conversations become meetings. - Work backwards from the meetings you need. A target that requires a connect rate your numbers have never hit is not a target, it is an excuse for a difficult conversation later. If the maths says the dials are impossible, the problem is upstream — data quality, number health or calling hours. See Phone health.

Last updated on Sep 29, 2026

Sales floor — monitoring live calls

Salefloor is the manager's view: real-time call monitoring across your organization. What is on the screen Live Calls Dashboard — every call in progress, with: - Session ID - Detection — whether the system classified the answer as human or machine - Duration - Transcript Preview — live text from the call - Actions — listen in Active Reps — who is working right now, with call duration and the list they are assigned to. Call Statistics (Last 24h) — Total Calls, Completed, Accepted, No Answer and Conversion %, per user and overall. Listening to a call Use the listen action on a live call. You can join muted — the normal case, where neither party hears you — or unmuted. The rep sees a prompt: "An admin is requesting to monitor this call. Accept to listen in." Monitoring is not silent and not automatic; the rep accepts it. Some messages you may hit: | Message | Meaning | | --- | --- | | Call is still connecting — listening available shortly | The call has not been answered yet. | | SIP client not registered - refreshing page may help | Your own audio client did not register. Reload. | | Monitor not available | Monitoring is not available for this call. | | Live dashboard is unavailable: backend URL is not configured | A configuration problem — contact support. | Using it well Listen to whole calls, not fragments. Dropping into the last thirty seconds of a call tells you how it ended and nothing about why. Tell the team you do it, and why. Monitoring that arrives as a surprise reads as surveillance. Monitoring that is part of a stated coaching routine reads as support — and the rep has to accept the request anyway. Do not coach live. Note it, then talk afterwards. A rep hearing a manager in one ear while a prospect talks in the other will lose both. Pair it with the recording. Logs has the recording and the notes; the live view is for catching things as they happen, not for review.

Last updated on Sep 29, 2026