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

# Leads & Test Drives

> Capture shopper interest and manage test drive requests (Pro)

# Leads & Test Drives

On **AutoFire Pro**, shoppers can submit interest and test drive requests from your public dealer site. Your team works both queues in the dashboard—with email notifications when new requests arrive.

## In this guide

* Lead capture, statuses, and inbox views
* Test drive request flow and status queue
* Team workflow tips

<Note>
  Lead capture, test drive scheduling, and the related dashboard pages require an active Pro subscription (or trial). Free Kickstart sites still show phone and email contact options on vehicle pages.
</Note>

## Lead capture

### Where leads come from

* Shoppers submit the **lead form** on vehicle detail pages when you are on a paid plan.
* Submissions are tied to the vehicle they were viewing when possible.
* Built-in rate limiting and spam-conscious defaults help reduce junk submissions.

### Lead inbox

Open **Dashboard → Leads** to see inbound interest.

<CardGroup cols={2}>
  <Card title="List and Kanban views" icon="columns">
    Switch between a sortable list and a kanban board organized by status.
  </Card>

  <Card title="Vehicle context" icon="car">
    See which vehicle the shopper was interested in from the lead record.
  </Card>

  <Card title="Email notifications" icon="envelope">
    Team members are notified when new leads arrive.
  </Card>

  <Card title="Notes and detail" icon="note-sticky">
    Open a lead for full contact info, message, and follow-up history.
  </Card>
</CardGroup>

### Lead statuses

Move leads through your sales process using these statuses:

| Status        | Typical meaning                  |
| ------------- | -------------------------------- |
| **New**       | Just arrived—needs first contact |
| **Contacted** | Team reached out                 |
| **Qualified** | Good fit, active conversation    |
| **Converted** | Became a sale or appointment     |
| **Lost**      | Did not proceed                  |

<Tip>
  Use kanban view to drag leads between columns as your team follows up across shifts.
</Tip>

## Test drive requests

### Public request flow

On Pro, vehicle detail pages include a **test drive request** button alongside the lead form. Shoppers pick a preferred date and time slots; requests land in your dashboard queue.

### Test drive inbox

Open **Dashboard → Test drives** to manage requests.

Views include:

* **Agenda** — day-grouped schedule (default)
* **Week** — calendar-style week view
* **List** — sortable table with filters

### Test drive statuses

| Status        | Typical meaning                   |
| ------------- | --------------------------------- |
| **Requested** | New request awaiting confirmation |
| **Confirmed** | Appointment set with the shopper  |
| **Completed** | Test drive happened               |
| **Cancelled** | Shoppers or staff cancelled       |
| **No-show**   | Shopper did not arrive            |

<Steps>
  <Step title="Review new requests">
    Open Test drives and check the agenda for today's and upcoming requests.
  </Step>

  <Step title="Confirm the appointment">
    For **Requested** items, use **Confirm** to move to **Confirmed**. Shoppers may receive a confirmation email when notifications are configured.
  </Step>

  <Step title="Reschedule if needed">
    Update the requested date from the request detail when plans change.
  </Step>

  <Step title="Close the loop">
    Mark **Completed** after the drive, or **Cancelled** / **No-show** when appropriate.
  </Step>
</Steps>

<Note>
  AutoFire centers on request capture and status tracking. Use your dealership's calendar process alongside the dashboard queue for staff scheduling.
</Note>

## Team workflow tips

<AccordionGroup>
  <Accordion title="Speed to lead">
    Leads and test drives are high-intent moments. Assign follow-up quickly—especially on mobile where notifications arrive in email.
  </Accordion>

  <Accordion title="Shared visibility">
    Invite sales staff with [team roles](/dealer-guide/team-management) so everyone sees the same queues instead of scattered texts.
  </Accordion>

  <Accordion title="Inventory stays linked">
    Because requests connect to specific vehicles, your team always knows which car the shopper cared about.
  </Accordion>
</AccordionGroup>

## Next steps

<Steps>
  <Step title="Invite staff">
    [Team management](/dealer-guide/team-management) — shared visibility on leads and test drives.
  </Step>

  <Step title="Review packaging">
    [Plans & billing](/subscriptions) — Pro requirements and cancellation behavior.
  </Step>
</Steps>

<CardGroup cols={2}>
  <Card title="Team" icon="users" href="/dealer-guide/team-management">
    Roles and invites for your sales staff
  </Card>

  <Card title="Inventory" icon="car" href="/dealer-guide/inventory">
    Vehicle context on every lead and request
  </Card>

  <Card title="Website" icon="globe" href="/dealer-guide/website">
    Where forms appear on vehicle pages
  </Card>

  <Card title="Features" icon="star" href="/features">
    Growth features in the reference catalog
  </Card>
</CardGroup>