> ## Documentation Index > Fetch the complete documentation index at: https://docs.deepblocker.ai/llms.txt > Use this file to discover all available pages before exploring further. # Read your results > What the results table on a campaign page shows for each person called, and how the Passed, Failed and Reported verdicts are decided. Results appear on the campaign page, under **Results**, as each call finishes. There is one row per person called. If a person was retried, the row shows their final outcome. A multi-call sequence shows every call instead, one row per call. > [!NOTE] > > Names are hidden by default. The table shows each person's team and a masked number instead. See [Fair testing rules](https://docs.deepblocker.ai/vishing/fair-testing.md) for the **Show names in reports** setting. ## Before you start * A campaign that has placed at least one call. See [Authorise and launch](https://docs.deepblocker.ai/vishing/campaigns/authorise.md). * Access to the workspace the campaign belongs to. See [Invite your team and roles](https://docs.deepblocker.ai/account/team.md). ## The four numbers at the top | Tile | What it counts | | - | - | | **Failed the test** | People who gave the caller what was asked for. | | **Passed the test** | People who refused, plus people who reported the call. | | **Reported the call** | People who used your report link during or after the call. Shown only when at least one person did. | | **Not reached** | No answer, voicemail, or the call could not be completed. | Click a tile to filter the table to that group. Click it again to clear the filter. Under the tiles, a bar shows the split, with a line such as **4 of 10 employees reached**. ## Attack and defence on the same calls This block appears once at least one person answered. It puts your people's result next to our detector's result on the same calls. | Number | What it means | | - | - | | **Staff who gave something away** | People who failed the test. | | **Calls our detector would have blocked** | Failed calls where DeepBlocker's deepfake detector would have flagged the cloned voice. The count in brackets is how many calls were scored. | | **Residual: failed and not blocked** | The worst case: the person failed and the detector missed it. You want this at 0. | One sentence above the numbers sums it up, ready to paste into a report. ## Breakdown tables Three more tables appear when the calls carry the data for them: one per attack level, one per pressure tactic, and one comparing calls with and without a warm-up notice. Each has the same columns: | Column | What it means | | - | - | | **Reached** | The call connected and the person engaged. | | **Staff failed** | The person did the unsafe thing the caller asked. Lower is better. | | **Detector caught** | Our detector flagged the synthetic voice, out of the calls it scored. Higher is better. | | **Got through** | The person failed and the detector missed it. | ## The table Filter chips above the table: **All**, **Failed**, **Passed**, **Not reached**. Failed rows sort first. | Column | What it shows | | - | - | | **Employee / number** (or **Team** when names are hidden) | The number called and, when names are shown, the person's name. | | **Employee** | The verdict badge, **Risk N/100**, the pressure tactics used, how the person sounded, the warm-up notice they had, and a **Coached** badge when coaching ran. | | **Detector** | **Caught**, **Missed** or **Not scored**, and the background sound used on the call. Hover for the score. | | **Version** | Which version of the campaign made the call. Shown only when the campaign has been edited since launch. | | **Why** | One line on why the person passed or failed. | | **Duration** | Length of the call. | | **When** | Date and time the call started. | | **Details** | Opens the call. See [One call in detail](https://docs.deepblocker.ai/vishing/results/call-detail.md). | ## How the verdict is decided The verdict comes from the analysis of the call after it ends. A **Reported** verdict comes from your report link instead. | Verdict | Given when | Counted as | | - | - | - | | **Failed** | The person disclosed sensitive information or complied with the caller. | Failed | | **Passed** | The person recognised the attack and refused to comply. | Passed | | **Reported** | The person reported the call to security through your report link. The **Why** column says how many minutes after the call started. If they had given something away first, it says so. | Passed | | **Voicemail** | The call reached voicemail. No live conversation took place. | Not reached | | **No answer** | The person did not answer. | Not reached | | **Call failed** | The call could not be completed. | Not reached | | **In progress** | The call is still active. | Pending | The **Why** column uses the analysis summary when there is one. Without it, a failed row lists what was disclosed and a passed row lists what the person did right. **Risk N/100** is the analysis's risk score for that person. Higher means more risk. It is not shown for people who were not reached. The **Detector** badge reads **Caught** when the fake score reached the threshold, **Missed** when it did not, and **Not scored** when the call has not been scored. The threshold is 80% unless the detector reports another. Hover the badge for **Scored X% fake (threshold Y%)**. ## Showing names When **Show names in reports** is off, owners, admins and the person who created the campaign see a **Show names** button above the table. Click it to reveal names for this view. Click **Hide names** to go back to teams. Other members see teams only. ## Other buttons on the results card * **Sync & analyze** pulls any missing calls and runs the analysis again. * **Evidence pack** and **Export for auditors** build a document for your board, auditor or insurer. See [Export for auditors](https://docs.deepblocker.ai/vishing/results/auditor-pack.md). * **Report**, at the top of the campaign page, opens the printable report. See [The workspace Reports page](https://docs.deepblocker.ai/vishing/results/reports-page.md). ## Problems > [accordion] It says No call results yet > > The campaign has not placed a call. Check its status and schedule. See [Campaign statuses](https://docs.deepblocker.ai/vishing/statuses.md). > [accordion] It says No one was called, and lists my testing rules > > Every person was skipped by a fair testing rule: **New joiner**, **Cooling off**, **Over the quarterly testing limit**, **Quiet hours** or **Excluded from testing**. Adjust the rules, then launch again. See [Fair testing rules](https://docs.deepblocker.ai/vishing/fair-testing.md). > [accordion] It says No call was placed, and that calls were refused before dialing > > A check stopped the call before it was dialled. The most common reason is a cloned voice with no recorded consent. Record consent, then launch again. See [Clone an executive's voice with consent](https://docs.deepblocker.ai/vishing/executive-voice-consent.md). > [accordion] The Detector column says Not scored > > The detector scores a call shortly after it ends. Wait a few minutes, then click **Sync & analyze**. A call with no usable recording stays **Not scored**. > [accordion] A person was called three times but has one row > > Retries collapse into one row with the final outcome. The line under the bar says how many calls were placed in all. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.