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

# Recalls

> How Kordless brings past customers back when their vehicle is due for service.

Recalls are Kordless's retention engine. When a customer completes a service that has a recall interval — like a ceramic coating that needs an annual inspection — Kordless tracks the due date and drafts a message to bring them back. You stay in control: every recall waits for your approval before it's sent.

## How recalls work

The system runs on a daily scan, fully automatic:

1. **The scan checks completed jobs.** Once a day, Kordless looks at every completed job tied to a vehicle, checking whether the service has a recall interval in your published price book.
2. **Due dates are calculated from the completion date.** A ceramic coating completed on March 1 with a 365-day interval is due the following March 1.
3. **A recall is drafted.** When a job comes due, Kordless creates a recall record with a pre-written message tailored to the customer, vehicle, and service. The message says it's been about a year (or whatever the interval is) since the service, recommends a check-up, and invites the customer to reply to book a time.
4. **The recall appears on your Today page.** It shows up in the right rail under **Recalls due** — you approve, snooze, or dismiss it.

No recall is ever sent without your approval. The agent drafts the message; you decide when it goes.

## Which services have recalls

Recall intervals are set per service in your [price book](/quoting/price-book). In the Auto Aesthetics edition:

| Service             | Recall interval | Channel |
| ------------------- | --------------- | ------- |
| **Ceramic coating** | 365 days        | Email   |
| **Tint**            | —               | —       |
| **PPF**             | —               | —       |
| **Detailing**       | —               | —       |

Only ceramic coating has a recall interval by default — it's the service with a clear manufacturer-recommended maintenance cycle. You can add recall intervals to other services in your price book if you offer maintenance packages or inspection programs.

A service with no recall interval is simply skipped by the scan. The recall engine never invents a due date — it only acts on rules you published.

## Approve recalls from Today

The fastest way to handle recalls is from the [Today](/day/today) page:

<Steps>
  <Step title="Check the Recalls due counter">
    The right rail shows how many recalls are due. Each one lists the customer name, the service, and a relative due label like "due now" or "in 5d."
  </Step>

  <Step title="Approve and send all">
    Click **Approve & send all** to queue every due recall for delivery. Each message goes out over its configured channel (email by default). The system processes them one at a time — a single failure doesn't block the rest.
  </Step>
</Steps>

Approved recalls show **sending** on the vehicle record. Once delivered, the recall is marked complete and won't reappear until the next interval.

<Accordion title="What if a recall fails to send?">
  If the email or text can't be delivered (invalid address, carrier rejection), the recall stays in the **due** state and a delivery failure appears on your [Today](/day/today) page under the action items checklist. Fix the customer's contact info in the [Garage](/day/garage) and approve the recall again.
</Accordion>

## Handle recalls individually

Sometimes the timing isn't right for a particular customer. You can handle recalls one at a time from the vehicle record:

<Steps>
  <Step title="Open the vehicle record">
    From the [Garage](/day/garage), find the customer and click **Full record** on the vehicle with a due recall.
  </Step>

  <Step title="Find the recall">
    The recall appears in the Recalls section and on the timeline, tagged with its due label.
  </Step>

  <Step title="Snooze or dismiss">
    Click **Snooze** to defer the recall by 30 days (or a custom period). Click **Dismiss** if the customer isn't coming back and you don't want to keep nudging them.
  </Step>
</Steps>

Snoozed recalls re-surface automatically when the deferral period ends — they come back to the Today page as due again. Dismissed recalls are gone for good.

<Accordion title="Can I bring back a dismissed recall?">
  No. Dismissal is permanent. If you change your mind, create a new quote for the customer from the [Quote Desk](/quoting/overview) and the normal flow takes over. If the customer completes the service again, a fresh recall will be drafted when the next interval comes due.
</Accordion>

## What the customer sees

The drafted message is warm and specific. It uses the customer's name, the vehicle, and the service:

> Hi Marcus — it's been about a year since the Ceramic coating on your 2025 Tesla Model 3. That's when we recommend a check-up to keep it looking its best. Reply and we'll find you a time. — Peak Auto Studio

The message never mentions money, warranties, or guarantees — it's a friendly nudge, not a sales pitch. When the customer replies, the agent picks up the conversation, qualifies what they need, and quotes from your price book.

## Next steps

<CardGroup cols={2}>
  <Card title="Today" icon="sun" href="/day/today">
    Where recalls surface for your approval — alongside everything else that needs you.
  </Card>

  <Card title="Garage" icon="car" href="/day/garage">
    The vehicle records where recalls live alongside jobs, films, and warranties.
  </Card>
</CardGroup>
