> ## 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.

# Commitments overview

> What a Commitment records, where Kordless stops, and what Commitments is not.

A Commitment is the boundary event — the moment a customer accepts an offer and the business records that acceptance with a hold, a deposit, or an external handoff. Kordless stops cleanly here. What happens after commitment belongs to your operating systems.

## What you can do here

The Commitments page shows accepted offers with their hold, booking, and deposit status. Each row tells you:

* **Customer** — Who accepted the offer.
* **Service** — What was quoted.
* **Offer** — The accepted price or range.
* **Status** — Where the commitment stands.
* **Boundary** — The boundary mechanic in customer language.
* **Deposit** — The deposit state, or a link to send the deposit.
* **Version** — The book version the accepted offer came from.
* **Action** — When the commitment is held, a **Release hold** action appears.

## How this fits together

A commitment moves through a simple boundary:

```text theme={null}
Accepted offer
  → Held (provisional)
  → Confirmed (deposit paid or external handoff)
  → Or released (hold expired or owner released)
```

One commitment exists per quote. Creating a commitment from the same quote twice returns the existing record — it cannot produce duplicates.

## Commitment statuses

| Status       | What it means                                                 |
| ------------ | ------------------------------------------------------------- |
| Pending      | Accepted offer; nothing secured yet                           |
| Held         | A provisional hold exists, not yet confirmed or paid          |
| Booked       | The boundary was crossed via an external handoff reference    |
| Deposit paid | A deposit has been taken                                      |
| Completed    | The work is done — read from the quote, a post-boundary fact  |
| Released     | The commitment did not stick — expired, released, or refunded |

<Note>
  A held commitment is a provisional hold. It never reads as a firm booking. The boundary summary on the work list shows "Hold until \[date]" when a deadline is set, or "Held (no deadline)" when no auto-expiry is configured.
</Note>

## What Commitments is not

Commitments is not:

* A job board or work order system.
* A production calendar or scheduling tool.
* An invoice ledger or accounting product.
* A fulfillment tracker.
* A customer database.

Kordless completes the offer and commitment path, then hands the result to your operating systems. Scheduling, dispatch, invoicing, and fulfillment happen downstream.

## Creating a commitment

When a quote is in the **quoted** state and the customer accepts, the owner creates a commitment from the Quotes work list. The **Create commitment** action appears on quoted quotes.

Creating a commitment records:

* The accepted offer and its book version pins.
* An optional deposit amount — a Stripe checkout link is generated for the customer.
* An optional hold duration in hours — the hold expires automatically after this period if not confirmed.

The commitment starts in the **held** state. If a deposit was requested, the deposit link appears on the Commitments page while the commitment is held.

## Start here

<CardGroup cols={2}>
  <Card title="Holds, booking, and deposits" icon="credit-card" href="/product/commitments/holds-booking-and-deposits">
    How deposits, holds, and booking work at commitment.
  </Card>

  <Card title="Expiry, release, and handoff" icon="arrow-right-left" href="/product/commitments/expiry-release-and-handoff">
    What happens when a commitment expires, is released, or is handed off.
  </Card>
</CardGroup>
