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

# Appointment Outcomes

> Record what happened after every appointment with one form — Spark handles the policy, sales log, pipeline, drips, and client confirmation

After any appointment or sales call, click **Record Outcome**. One form does everything: it records the result, and Spark takes care of the policy record, your sales log, the pipeline stage, follow-up drips, and the client's confirmation message — all in one submit.

You'll find **Record Outcome** in two places:

* The **dialer top bar** in the Phone tab — record the outcome right after you hang up
* The **contact profile**, next to the Policy Info section

## Recording an Outcome

<Steps>
  <Step title="Open the form">
    Click **Record Outcome** from the dialer top bar or from the contact profile. The client's name is prefilled.
  </Step>

  <Step title="Pick the outcome">
    Choose one of: **Application Approved**, **Application Submitted**, **Follow Up**, **No Show**, **Not Interested**, **Think About It**, or **Manual Follow Up**.
  </Step>

  <Step title="Set a follow-up date (optional)">
    If the client needs a callback, set a follow-up date. Spark creates a task due that date.
  </Step>

  <Step title="Enter policy details (sales only)">
    If the outcome is a sale, fill in the policy: carrier, product, policy number, insured, beneficiary, face amount, monthly/annual premium, draft date, policy reason, and notes.
  </Step>

  <Step title="Send a confirmation (optional)">
    Check **send confirmation** to text and email the client a policy confirmation using your editable Policy Confirmation templates.
  </Step>

  <Step title="Submit">
    Spark records everything in one pass — policy, sales log, pipeline, drips, confirmation, and follow-up task.
  </Step>
</Steps>

## What Happens on Submit

For every outcome, Spark automatically:

1. Creates the [policy record](/insurance/policies) on the contact (sales only)
2. Creates a [sales-log entry](/insurance/sales-log) with your [commission calculated](/insurance/commission-tracking) (sales only)
3. Moves the contact to the matching pipeline stage
4. Stops any active drip campaigns
5. Enrolls the contact in the outcome-specific follow-up drip (for example, the Application Approved sequence)
6. Texts **and** emails the client a policy confirmation, if you checked the box
7. Creates the follow-up task, if you set a date

## Outcomes at a Glance

| Outcome               | Pipeline stage        | Follow-up drip                 | Policy + sale created |
| --------------------- | --------------------- | ------------------------------ | --------------------- |
| Application Approved  | Application Approved  | Application Approved sequence  | Yes                   |
| Application Submitted | Application Submitted | Application Submitted sequence | Yes                   |
| Follow Up             | Follow Up             | Follow Up sequence             | No                    |
| No Show               | No Show               | No Show sequence               | No                    |
| Not Interested        | Not Interested        | Not Interested sequence        | No                    |
| Think About It        | Think About It        | Think About It sequence        | No                    |
| Manual Follow Up      | Manual Follow Up      | Manual Follow Up sequence      | No                    |

Only **Application Approved** and **Application Submitted** create a policy record and sales-log entry — every other outcome still moves the pipeline, swaps the drip, and creates a follow-up task if you set a date.

<Note>
  Recording an outcome stops whatever drip the contact was on before enrolling them in the new one — a client who just bought stops getting "still interested?" texts immediately.
</Note>

## Customizing the Confirmation Templates

The text and email the client receives come from your **Policy Confirmation templates**. They live in your [SMS and Email Drips](/messaging/sms-drips) as editable manual campaigns, seeded as drafts — so you can rewrite them to sound like you before the first one ever sends.

Templates support tokens that fill in automatically, including:

* The client's name
* Policy details (carrier, policy number, face amount, premium, draft date)
* Your phone number

<Tip>
  Review the confirmation templates during setup, before your first sale. Once they read the way you want, every confirmation goes out polished without another thought.
</Tip>

## FAQs

<AccordionGroup>
  <Accordion title="What if the appointment wasn't a sale?">
    Record the outcome anyway. Non-sale outcomes (Follow Up, No Show, Not Interested, Think About It, Manual Follow Up) still move the pipeline, stop the old drip, and enroll the contact in the right follow-up sequence — so no lead falls through the cracks.
  </Accordion>

  <Accordion title="Does the confirmation send by text or email?">
    Both. When you check **send confirmation**, Spark texts and emails the client using your Policy Confirmation templates.
  </Accordion>

  <Accordion title="Where does the commission number come from?">
    The sales-log entry created on submit calculates commission from your comp grids. See [Commission Tracking](/insurance/commission-tracking) for how the grids and contract levels work.
  </Accordion>

  <Accordion title="Can I record an outcome without a follow-up date?">
    Yes — the follow-up date is optional. Skip it and no task is created; everything else still happens.
  </Accordion>
</AccordionGroup>