> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/understand-your-business/vehicle-wait-time/vehicle-wait-time-overview.md).
# Vehicle Wait Time Overview
**Vehicle Wait Time** allows you to leverage your cameras, POS system and drive-thru sensors to monitor drive-thru data and service thresholds across all of your locations.
Vehicle Wait Time can help many different types of businesses track and use vehicle data, including:
* Quick-service restaurants
* Thrift stores (monitor vehicles dropping off/donating items)
* Banks with drive-thru service
* Oil change services (track total time vehicles spend at location)
* Mechanic garages
For quick-service restaurants especially, you can:
* See the **total amount of time** each vehicle spends at your drive-thru window.
* **Compare drive-thru performance** throughout different periods of the day (breakfast, lunch, dinner).
* Use **widgets to compare metrics** across your locations.
* Display **dashboards for employees** so that they can visualize drive-thru performance in relation to other locations.
* Pinpoint areas of improvement through POS data.
* Provide video evidence from new or existing cameras to back up assumptions.
***
## How it Works
Solink analyzes video from an outdoor camera to calculate the amount of time each vehicle spends at the drive-thru window.
Once the vehicle moves out of view of the drive-thru camera, Solink creates an event (you can review the event on the **Events** page, see [View and Filter Vehicle Wait Time Events](/docs/understand-your-business/vehicle-wait-time/filter-vehicle-wait-time-events.md) for more information).
Each event displays the total "window time" - this represents the total amount of time that the vehicle captured in the event spent at the drive-thru window.
You can review individual window time via the **event card** or within the **video player** when watching the event:
**Event Card**
**Video Player: Event Playback**
See the following topics for more information on Vehicle Wait Time:
* [Vehicle Wait Time Setup](/docs/understand-your-business/vehicle-wait-time/vehicle-wait-time-setup.md)
* [Filter Vehicle Wait Time Events](/docs/understand-your-business/vehicle-wait-time/filter-vehicle-wait-time-events.md)
* [Troubleshoot Vehicle Wait Time](/docs/understand-your-business/vehicle-wait-time/troubleshoot-vehicle-wait-time.md)
---
# 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://help.solink.com/docs/understand-your-business/vehicle-wait-time/vehicle-wait-time-overview.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.