Live Monitoring

The Live monitoring tab is the study’s dashboard while it is in the field. It opens once the study has started dialling. If the study uses sub-samples, it opens once the main launch has started dialling, and each sub-sample run has its own dashboard on its run page.

​

Refresh and modes

• While the study is calling, the dashboard refreshes every 30 seconds. The top line shows Last updated and the refresh interval. Select Refresh in the study header to update immediately.
• If a refresh fails, the cards keep showing the last loaded data with a Couldn’t refresh note.

The heading tells you which mode the dashboard is in:

​

KPI row

​

Margin of error

The strip under the KPI row shows the margin of error, for example ±5.3 percentage points at 95 percent confidence, covering every completed interview in the study.

• It is theoretical: it assumes a simple random sample, no weighting and an evenly split question, corrected for the population size.
• It needs a population size. If none was entered in step 4, select Add population size (available while the setting can still be edited).

​

Projected finish and ramp-up

Projected finish forecasts when the main launch will reach its target: an expected duration with a range (for example “About 2 days · 2 to 3 days”), the expected finish date, whether it finishes before your end date, how many calls run at once, and whether the forecast is based on this run’s own calls or on platform defaults. It is shown as a range because it depends on response ratios that vary from sample to sample. The forecast refreshes every two minutes. Sub-sample runs show their own progress in the cards instead. The ramp chip in the card header shows how fast the study is allowed to call, for example Ramping up · 16 of 32 lines. Hover over it for the detail. Sometimes the limit is set by something other than the ramp: the platform’s shared calling lines, or your remaining credit. The chip says so.

​

Budget

The Budget card shows what the study can still spend: The card also tells you which limit binds first and, at the current pace, roughly how many hours remain:

• If your AI credit runs out before your spend cap, calling stops when it does, and a top-up lets you resume.
• If your spend cap is reached first, the study closes and cannot be resumed.

A warning appears once the study passes the warning threshold (for example 80% of its budget). The spend cap is shared by the main launch and every sub-sample. See Costs, Credits and Limits.

​

Charts

• Progress · completes vs contacts: running totals of completes and contacts over time. Switch the time grain between Day and Hour.
• Dispositions: how every worked record has resolved so far (complete, no answer, refusal, answering machine, partial, not eligible, invalid number, and others), with the number of settled records as the base. Select Download to save the figures.
• Daypart heatmap · success by time: completes and dials by weekday and three-hour band, built in your own time zone. Use it to see when people answer and complete.
• Attempts: how many records have reached each attempt number, and their completes, so you can see how many needed a second or later attempt.

​

Sample composition · achieved vs target

For each distribution target set in step 5, the card shows achieved against target per answer, for example “176 of 300 · 59%”, counted from ingested interviews. On a sub-sample run’s dashboard, the targets are those of the whole study, not only of the run.

​

Interview quality

Signals that a run is degrading before the data shows it. Each measure shows how many calls were measured; when very few calls were measured, treat the figures as indicative only. The footnote under the dashboard shows the calling engine’s own counts for the run: records resolved (finished with) and callable (can still be called), and the last activity.

​

Related pages

• Results and Export
• Study Page and Actions
• Sub-samples