> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firetone.com.au/llms.txt
> Use this file to discover all available pages before exploring further.

# Recording an outcome

> What came of the call, in the form your organisation designed.

export const Unverified = ({what, detail}) => <Warning>
    <strong>Not yet verified on a live call.</strong> {what} is built and covered
    by tests, but {detail} FireTone's engineering tracker records this as an open
    check rather than a passing one. Treat what follows as the design, and expect
    rough edges the first time you run it.
  </Warning>;

On campaigns that have one, a form sits beside the customer's details while you
talk. Fill it as you go and press **Save**.

<img src="https://mintlify.s3.us-west-1.amazonaws.com/firetone/images/oncall-disposition.png" alt="The disposition form" />

## Fill it during the call, save it after

You do not have to finish before the call ends. The customer's details and the
form stay on screen for a couple of minutes after they hang up, so you can
complete a sentence and save.

Nothing blocks your next call. An unsaved form is kept and shown until it is
finished.

## What is recorded

Your answers, against that call, with your name and the time. Re-saving updates
it — correcting a mistyped date is fixing a record, not filing a second one.

<Note>
  Your outcome does **not** overwrite what the phone system recorded. The system
  keeps its own result — busy, no answer, connected — and your answers sit
  beside it. Both are wanted: "we rang four times and got voicemail twice, then
  they answered and refused" needs each half.
</Note>

## Required fields

Marked ones must be answered before it will save. They are checked when you
press Save, never while you type — a form that refused to hold a half-finished
answer mid-call would be a form that lost it.

<Unverified what="The disposition form" detail="the storage and the endpoints are built and tested; no agent has yet filled one in on a live call." />