> 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/assigning-bookings.md). # Assigning Bookings Give bookings to companies and drivers, and handle price offers, rejections and blocked bookings. Assigning a booking means choosing who carries out the ride. In CodiCo Dispatch you assign a booking to a **company** (your own company or a subcontractor) and, optionally, to one of its **drivers**. The company or driver then accepts or rejects the job. ## Assign a new booking {% stepper %} {% step %} ### Open the Unassigned tab Go to **Bookings** and open the **Unassigned** tab. It lists every booking with the status *Unconfirmed*. {% endstep %} {% step %} ### Click Assign Click **Assign** next to the booking. In the dialog, choose the **Company** and click **OK**. {% endstep %} {% step %} ### Wait for acceptance The booking moves to the **Assigned** tab with the status *Assigned*. When the company or driver accepts it, the status changes to *Confirmed* and the booking moves to **Ongoing**. {% endstep %} {% endstepper %} {% hint style="success" %} **Tip:** If you set a **Default company** in **System Settings → General**, new bookings are assigned to that company automatically. {% endhint %} ## Assign or change the driver In the bookings list, a booking that has a company but no driver shows **Assign+** in the **Driver** column. Click it to choose a driver. To change the driver or company later, use the edit icon next to the name in the list, or open the booking and change **Company** and **Driver** in the **Assignments** block. On an existing booking, **Change company** reassigns the booking to another company. You can also assign bookings visually on the [Schedule](/documentation/bookings-and-dispatch/schedule.md) by dragging them onto a driver's row. ## Price offers Instead of assigning a booking at your price, you can ask companies to send their own price. Their answers appear in the **Price offers** block of the booking with the company, the offered price and the date, and you accept the offer that suits you. The emails used for this are **Notification price request** and **Notification price offer accepted** in **Notifications → Company Notifications**. ## Rejected assignments When a company rejects a booking, the booking gets the status *Job rejected* and appears in the **Rejected** tab. The **Rejected assignments** block of the booking shows which companies rejected it and why. Assign the booking to another company or cancel it. ## Blocking a booking Block a booking when the ride was not carried out properly through the company's fault, for example a no-show. Click **Block** in the bookings list or at the bottom of the booking. In the dialog, enter the **Company penalty**: the amount deducted from the company's earnings. Blocked bookings appear in the **Blocked** tab. If a company is suspended from receiving new bookings, the **Suspended until** column in **People & Companies → Companies** shows until when. ## Watch the video {% embed url="" %} Connect Your Partner Network with CodiCo Dispatch Software {% endembed %} Read more about [driver management](https://codico.io/taxi-dispatch-software/drivers-management/) and [automated dispatch](https://codico.io/taxi-dispatch-software/automation/) 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/assigning-bookings.md?ask=&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.