> For the complete documentation index, see [llms.txt](https://herd-security.gitbook.io/herd-security-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://herd-security.gitbook.io/herd-security-docs/simulations/voice-simulations/campaign-results.md).

# Voice Campaign Results

Read a voice campaign's results: what each call status means, who passed, who failed, and the call history behind every person.

Open a voice campaign and switch to its **Results** tab. It fills in live: first as codes are texted out, then as calls connect and finish.

***

## Call statuses

| Status                            | Outcome     | What happened                                                                                                                                                     |
| --------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Read code back**                | **Failed**  | The person read the code out loud to the caller. This is the behavior the simulation is testing for, and it raises a **high-weight risk event** on their profile. |
| **Answered**                      | **Passed**  | The call connected and the person never read the code back. A call that goes to **voicemail** counts here too.                                                    |
| **No answer**                     | **Passed**  | Nobody picked up. Not answering an unexpected call is a perfectly good outcome, so it counts as a pass.                                                           |
| **Retry pending**                 | In progress | The call hit a technical failure. Herd retries automatically, up to **3 attempts**.                                                                               |
| **Call failed**                   | —           | The call couldn't be completed: it was declined, or the number isn't valid.                                                                                       |
| **Code texted** / **Call placed** | In progress | The simulation is still running for this person — the code has gone out, or the call is under way.                                                                |

{% hint style="info" %}
**Two very different behaviors both land on "passed."** Someone who answered and refused to give up the code, and someone who simply didn't pick up, are both a pass — but only the first one tells you the person handled a live pretext well. Reading the results next to the **Answered** count is the useful comparison.
{% endhint %}

***

## Looking at one person

Click any person in the table to open their **call history**: the sequence of what happened for them in this campaign, including any automatic retries and the final status.

***

## When nobody was called

If a scheduled launch is **refused**, the **Results** tab tells you why instead of leaving you with an empty table. The usual reasons are:

* **Consent was withdrawn** after the campaign was scheduled. See [Before You Start](/herd-security-docs/simulations/voice-simulations/before-you-start.md#an-admin-completes-the-consent-attestation).
* **The attack type isn't approved** yet. See [Approving new attack types](/herd-security-docs/simulations/voice-simulations/attack-types.md#approving-new-attack-types).

Clear the underlying reason and launch the campaign again.

***

Failures are the input to your next move: turn on [**Assign training on failure**](/herd-security-docs/simulations/voice-simulations/create-and-launch-a-campaign.md#step-4-optional-assign-training-on-failure), or see [Use Simulation Results to Decide Your Next Training](/herd-security-docs/how-to-documentation/use-simulation-results-to-decide-your-next-training.md).