> 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/troubleshooting-and-faq.md).

# Troubleshooting & FAQ

Solutions to common setup problems and answers to frequent questions.

## Booking form

<details>

<summary>The address search does not find addresses</summary>

* Check that Google Maps is connected in [Google Maps & Services](/documentation/integrations/google-maps-and-services.md).
* Check [Map Restriction](/documentation/locations-and-rules/map-restriction.md). Only the countries selected there are searched.
* If **Full address only** is on in [Booking Limits & Rules](/documentation/system-settings/booking-limits-and-rules.md), customers must choose an address with a street and house number.

</details>

<details>

<summary>A vehicle class is missing or has no price in the booking form</summary>

* Check the [Vehicle Availability Rules](/documentation/fleet-and-pricing/vehicle-availability-rules.md) for the route.
* Check the prices of the vehicle class in [Vehicle Classes](/documentation/fleet-and-pricing/vehicle-classes.md) and [Route Pricing](/documentation/fleet-and-pricing/route-pricing.md).
* If **Zone-to-Zone Mode** is on, prices and availability are calculated by [zones](/documentation/locations-and-rules/custom-zones.md). Check that the pickup and drop-off are inside your zones.

</details>

<details>

<summary>Customers cannot book at all, or only at certain times</summary>

In [Booking Limits & Rules](/documentation/system-settings/booking-limits-and-rules.md), check:

* **Disable booking** and **Disable booking daily from / till (GMT)**. The times are in GMT.
* **Booking date term**, the minimum time between booking and pickup.

Administrators are not affected by these rules, so test as a customer.

</details>

<details>

<summary>A customer cannot change or cancel a booking</summary>

The **Booking edit deadline** and **Booking cancellation deadline** in [Booking Limits & Rules](/documentation/system-settings/booking-limits-and-rules.md) set how long before the trip customers can still make changes. Administrators can always edit bookings.

</details>

<details>

<summary>The booking form on my website does not appear</summary>

* Check that both pieces of code from [Website Booking Form](/documentation/sales-and-marketing/website-booking-form.md) are on the page: the script and the `<at-widget-booking>` tag.
* Check that the script address is your own system's address, not the demo address.

</details>

## Emails

<details>

<summary>Emails do not arrive</summary>

* Check your mail server in [SMTP (Email)](/documentation/integrations/smtp-email.md) and use **Send a test email**.
* With Gmail, use an app password. The error *535-5.7.8 Username and Password not accepted* means the password is wrong.
* Customers can switch off individual emails in their profile. See [Customers](/documentation/people-and-companies/customers.md).
* Some templates, such as **Company Invoice Request**, have an **Enabled** switch. See [Notifications](/documentation/notifications.md).

</details>

<details>

<summary>An email is missing information, such as the flight number</summary>

Open the template in [Notifications](/documentation/notifications.md) and tick the **Show …** checkbox for the block and for the field.

</details>

## Dispatch and drivers

<details>

<summary>Drivers do not receive booking offers automatically</summary>

* Check that **Auto-assign driver** is on in [Booking Limits & Rules](/documentation/system-settings/booking-limits-and-rules.md).
* Check **Auto-assign max radius (km)**. Only drivers within the radius get the offer.
* The driver must be online in the [Driver Mobile App](/documentation/people-and-companies/driver-mobile-app.md).

</details>

## Integrations

<details>

<summary>Bookings from a booking platform do not come in</summary>

* Check that the integration and **Receive bookings** / **Farm In** are switched on.
* Check that every vehicle type or product is mapped to one of your vehicle classes. Bookings for unmapped types or products are not imported.
* Click **Sync bookings now** where the integration has it.
* Check that the pickup is inside your service area.

See the page of each platform under [Integrations](/documentation/integrations.md).

</details>

<details>

<summary>The Partner Network connection does not work</summary>

Both companies must add the other's token. If you clicked **Regenerate**, send the new token to your partners. See [Partner Network](/documentation/integrations/partner-network.md).

</details>

## Other questions

<details>

<summary>Why are the settings empty in the demo?</summary>

The demo hides settings values and shows *Sorry, you are in DEMO mode*. In your own system you see and save your values.

</details>

<details>

<summary>A translated text shows ":userName" or similar</summary>

Texts can contain placeholders such as `:userName` or `:booking_id`. The system replaces them when the text is shown. If a placeholder appears as text, it was changed in [Translations](/documentation/system-settings/languages-and-translations.md). Copy it back exactly as in the English text.

</details>

## Still need help?

* Watch the [video guides](https://www.youtube.com/playlist?list=PL6fvZC7jxNLgJCVlVERayPzmFpsC6u09f).
* [Book a 30-minute onboarding session](https://codico.io/30-minute-onboarding-session/) with the CodiCo team.
* [Book a 15-minute call](https://codico.io/book-15-minute-meeting/) or [send a request](https://codico.io/get-free-quote/).


---

# 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/troubleshooting-and-faq.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.
