Skip to main content

Opening Results

Open a survey and click Results in the Setup | Results switch in the workspace header. Results has six tabs: Overview, Questions, Outcomes, Routes, Responses and Export. This page covers the first four; see Responses and export for the other two. Results refresh on their own every 30 seconds while the page is open. A Live pill shows Updated (time ago) and (n) sessions in range.

Sessions and calls

Results are built from sessions. A session is one respondent’s interview: it starts when a call gets past the Gatekeeper into the questionnaire and records every answer from then on. A call that never reaches the first question — no answer, voicemail, a screener, or a respondent who declined or asked for a callback at the greeting — files no session. Those calls are counted only in the Contact funnel, which is built from call records. Each session has a status — its lifecycle — and an outcome code — the business result: See Closing and outcomes for how outcome codes map to statuses.

Filters

The filter bar applies to every Results tab: Reset appears once you change any filter.

Overview

Metric cards

Sessions over time

A daily chart of Started against Terminal (finished) sessions across the range — at most the last 30 days, and the last 14 days for All time. “The most recent bucket is still open — treat today as partial.”

Terminal statuses

How sessions split between in progress, completed, screened out, terminated, abandoned and failed, each as a share of started sessions. The card notes “Lifecycle status and business outcome are separate dimensions” — use the Outcomes tab for outcome codes.

Contact funnel

The funnel counts calls, not sessions, from the call records — so it includes the calls that ended at the gatekeeper. Its stages are Dialled, Connected, Entered survey and Completed. The test-session switch does not apply here. Below the stages, two lists break down where calls fell away:
  • Not connected — dials that were never answered.
  • Connected, did not enter — answered calls that ended before the first question.
Each lists calls by their recorded call outcome, such as No answer, Voicemail, Not interested, Callback requested, Wrong number or Caller hung up. See Call Statuses for what each call outcome means.

Largest drop-offs

The questions where the most interviews ended, shown as (key) — trace ends here. A question high on this list may be confusing, too long, or sensitive.

Data quality

“Diagnostics — nothing is cleaned up silently.” The card flags:
  • “(n) answers recognised below 0.6 confidence.”
  • “(n) superseded answers retained — only final answers are counted.”
  • “(n) terminal sessions carry no stored answers.”
  • “(n) answers reference a question outside this version.”
  • “(n) sessions have been in progress for over 24 hours.”
With nothing to report: “No data-quality issues detected in this cohort.”

Questions

One card per question (Display questions are left out), headed Question (n) · (key), with the prompt, how many answered, and the top 12 answers with their counts and percentages. Only final answers are counted — an answer the respondent corrected is replaced by the correction. For a battery, each rated item is counted as its own answer.

Outcomes

The Outcome codes table lists each code with Outcome, Sessions and Share of coded, followed by “(n) of (m) sessions carry no outcome code.” — usually interviews still in progress or dropped part-way through.

Routes

Route and drop-off — “Sessions reaching each ordered section, inferred from stored answers.” Each section shows how many sessions reached it and what share that is, and how many ended there. Use it to see where routing rules send respondents and where they stop.