Skip to main content

​
Overview

Once a batch has launched, its detail page turns into a results dashboard. The Summary tab shows headline metrics, charts and a call-by-call table that update live as calls complete, and the Data Collection tab aggregates everything your agent captured on those calls into a filterable table you can download as a CSV. There are two ways in:
  • From the Batch Scheduler page — click a batch row to open its Batch Summary panel, then press the Batch Analytics button.
  • From the batch itself — open the batch and select the Summary tab. Before launch this tab shows “Ready for launch”; after launch it shows the full analytics view.
This page covers the Summary tab’s analytics sections, the quick Batch Summary panel, where to watch progress and the forecast, and the Data Collection export.

​
Filter by list

If the batch draws its contacts from source lists, a list dropdown sits beside the Batch Metrics heading. It opens on All lists; the other entries are the batch’s source lists in priority order, each with its coloured rank badge. Pick a list and every section of the Summary tab — Batch Metrics, Call Analysis, Call Objectives, Call Outcomes, Source Lists and All Calls — shows only that list’s calls, and each section heading gains a muted ”· list name” so a screenshot says which list it covers. The Source Lists section narrows to the selected list’s row. The choice is kept in the page address, so a reload or a shared link keeps the filter. A list with no calls yet shows the usual empty states. Choose All lists to go back to the whole batch.

​
Batch Metrics

The Batch Metrics card at the top of the Summary tab gives the headline numbers. A caption line above the figures shows Started (the batch’s start date and time), Average Duration and Total Duration (talk time across all calls that connected), plus a Not Connected count when any calls rang out, were busy or were declined. The three rate metrics render as small donuts so you can read the batch’s health at a glance.

​
Call Analysis charts

The Call Analysis section pairs two charts:
  • Call Distribution by Time — one bar per connected call, placed on a timeline of when the call happened. Bar height is the call’s duration in seconds and bar colour is its end reason (a legend above the chart maps colours to reasons). Hover over a bar to see the contact’s name, the call’s duration, its end reason and the exact time. On large batches the chart plots the latest 2,000 dialled calls and says so above the chart (“Latest 2,000 of N calls”); the headline figures still cover every call. This chart makes pacing problems visible — clusters of short orange bars, for example, are a voicemail-heavy stretch.
  • End Reason — a donut of how completed calls ended, using the same end-reason labels as the Call Log (User Hangup, AI Hangup, Voicemail, Transfer and so on), with the total call count under the title. Segments large enough to label show their percentage, and the legend below lists each reason with its count. Hover over a segment for the exact count and percentage.
End reasons and statuses are explained in full on Call Statuses & End Reasons.

​
Call Objectives

The Call Objectives section aggregates the objective results from every call in the batch. Each script the batch ran gets its own block, headed with the script name, the number of objectives it defines and the number of calls:
  • Primary objective — a gauge showing the success rate of the script’s first objective, marked with a Primary badge in the list below.
  • All objectives — a gauge combining every objective on that script.
  • Beneath the gauges, each objective is listed with its own success rate.
A toggle at the top right switches the calculation base between All calls and Answered. It opens on Answered, because unanswered calls can’t achieve objectives — that is the fairer read on how the script performed in real conversations. Where nothing was evaluated, the card reads “No objectives were evaluated on answered calls.” This is the same panel as the Objectives section on the Dashboard, so the two always agree.

​
Call Outcomes

The Call Outcomes section shows the mix of outcomes across the batch. Every analysed call is assigned exactly one outcome after it ends, so the shares always add to 100%. Each script gets a card with an Inbound or Outbound badge, a table of outcomes with an Average and Latest share, and a stacked column chart showing how the mix moved over the life of the batch. Where calls have not been analysed yet, the card notes how many are awaiting analysis. Scripts that define their own custom outcomes use those. Otherwise the standard outbound set applies — Appointment booked, Completed, Busy — callback requested, Busy — will call back, Not interested, Not interested — opt-out, Wrong number, No answer, Voicemail and Did not connect. Scheduled, queued, cancelled and in-progress calls are not counted. If a script has nothing analysed, its card reads “No analysed outcomes for this script in the selected window.”

​
Source Lists performance

If the batch draws its contacts from source lists, a Source Lists section compares them side by side: each list’s priority rank, name, the script it ran (or “Batch default” if it uses the batch’s script), an A/B badge where the list is an A/B variant, and two bar metrics — Completion and Primary objective — each shown as a percentage with its count. This is where an A/B script test is read: the same completion and primary-objective figures as the rest of the page, broken out per list so you can compare variants directly. See Source Lists, Allocation & A/B Testing for how the variants are set up.

​
All Calls table

The All Calls section lists every call in the batch. Click any column heading to sort, and click a row to open the full call details panel — summary, objectives, transcript and analysis, exactly as on the Call Log (see Call Details). Two follow-up actions are available on each row:
  • Re-dial — opens the Reschedule Call dialog (“Select a new date and time to reschedule the call with {contact}”). Pick a future date and time and press Reschedule; a toast confirms “Call rescheduled successfully”.
  • Send Email — opens your mail client with a follow-up email addressed to the contact.
The table holds every call in the batch, not just the first page. Scroll and more load automatically; a Load more button at the bottom (Loading… while it works) pulls in the next set on demand. If nothing matches, the table reads No calls found. The whole Summary tab is live: as batch calls complete, the metrics, charts and table update without a refresh.

​
The Batch Summary panel

On the Batch Scheduler page, clicking a batch row opens a compact Batch Summary panel beside the table — useful for a quick check without leaving the list. It shows the batch’s Call Script, List, Status, Start Date/Time, Total Calls, Remaining Calls, Calls Completed (as a count and percentage), Total Time and Average Time, followed by a sortable calls table. The Batch Analytics button at the top opens the full Summary tab described above, and the Actions dropdown offers Add New Calls (see Adding Contacts to a Batch) and Cancel Batch.

​
Forecast and schedule progress

Analytics tells you how calls went; the forecast tells you how many are still to come and roughly when. For a running batch:
  • The Settings tab’s Schedule section shows when the current queue is estimated to clear and the estimated screening yield. Its chart plots each day’s ceiling (the most calls the batch may start that day) against the forecast’s estimate of calls that will actually start, and the summary underneath reads, for example, “Daily ceilings: 4,200 calls across 21 business days · 3,150 estimated (75% of ceilings)”. Daily caps, ramp profiles and the forecast are covered on Batch Scheduling & Pacing.
  • The Queue tab shows every contact’s individual state, including the estimated day each pending contact should be called, holds and screening blocks — see Batch Queue Management.

​
Data Collection export

The Data Collection tab appears on the batch once it has run (before launch it reads “No data collection yet”). It aggregates the structured data your agent captured on each call into one table — the fields come from the script’s Data Collection setup (see Data Collection). The table lists completed calls only — a contact appears once a call to them has finished, so contacts still waiting in the queue, or whose calls rang out or failed, are not shown. It loads 100 calls at a time: a footer reads “N of M completed calls loaded” and a Load more button fetches the next page, so search, filters, sorting and the CSV export cover the rows loaded so far. Each row has a Contact column, a Phone column, and one column per Data Collection field, in the order the fields are defined on the script. If a contact was called more than once (retries, re-dials), the row shows the attempt that actually captured data, preferring the most recent. Values are formatted for reading: yes/no fields show Yes or No, multi-select answers are joined with commas, numbers include their unit, and dates use day-month-year order. Empty cells mean the agent didn’t capture that field on the call.

​
Script tabs, search, filters and sorting

If the batch’s source lists ran different scripts, a tab row splits the table: All shows every contact with a Script column and one field column per script, and each script’s own tab shows just that script’s contacts and fields. The header gives you the standard table controls:
  • Search — matches against the contact’s name, phone, script and every field value.
  • Filters — add conditions on any column (Contact, Phone, Script, or any Data Collection field) using operators like contains, starts with, is, is not, empty and not empty. Rows must match every condition.
  • Sorts — order the table by one or more columns.
If your conditions exclude everything, the table reads “No rows match the current filters.”

​
Downloading the CSV

The download button in the table header exports the current view — the rows that survive your search and filters, with a header row of Contact, Phone, Script (on the All tab only) and each field’s label. The file is named after the batch and the active tab, for example spring-campaign-data-collection-all-scripts.csv, and a toast confirms “CSV downloaded”. Filter first, then download: the export is exactly what you see, so a filtered view gives you a ready-made follow-up list.

​
Next Steps