> For the complete documentation index, see [llms.txt](https://codico-dispatch.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codico-dispatch.gitbook.io/documentation/bookings-and-dispatch.md).

# Bookings & Dispatch

Take bookings, assign them to companies and drivers, and follow every ride to completion.

Bookings are the centre of CodiCo Dispatch. Every ride, whatever its source, appears in the same bookings list, where your team assigns it, follows it and closes it.

```mermaid
flowchart LR
    N["New booking<br/>Unconfirmed"] --> A["Assigned to a<br/>company or driver"]
    A -->|accepted| C["Confirmed"]
    A -->|rejected| R["Job rejected"]
    R --> A
    C --> E["En route"] --> AR["Arrived"] --> O["On board"] --> D["Completed"]
```

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Bookings List</strong></td><td>Find bookings with tabs, filters and search, and act on them.</td><td><a href="/documentation/bookings-and-dispatch/bookings-list.md">Bookings List</a></td></tr><tr><td><strong>Creating and Editing Bookings</strong></td><td>Every field of the booking form explained.</td><td><a href="/documentation/bookings-and-dispatch/creating-and-editing-bookings.md">Creating and Editing Bookings</a></td></tr><tr><td><strong>Booking and Payment Statuses</strong></td><td>What each status means and when it changes.</td><td><a href="/documentation/bookings-and-dispatch/booking-and-payment-statuses.md">Booking and Payment Statuses</a></td></tr><tr><td><strong>Assigning Bookings</strong></td><td>Give bookings to companies and drivers, handle price offers, rejections and penalties.</td><td><a href="/documentation/bookings-and-dispatch/assigning-bookings.md">Assigning Bookings</a></td></tr><tr><td><strong>Schedule</strong></td><td>Plan the coming days on a timeline per driver.</td><td><a href="/documentation/bookings-and-dispatch/schedule.md">Schedule</a></td></tr><tr><td><strong>Live Tracking</strong></td><td>Follow online drivers and their rides on the map.</td><td><a href="/documentation/bookings-and-dispatch/live-tracking.md">Live Tracking</a></td></tr></tbody></table>

Learn more about [automated dispatch](https://codico.io/taxi-dispatch-software/automation/) and [express booking entry](https://codico.io/taxi-dispatch-software/express-booking-entry/) on the CodiCo website.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://codico-dispatch.gitbook.io/documentation/bookings-and-dispatch.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.