> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/kenai-user-guide/visitor-management/assisted-check-in.md).

# Assisted check-in

When a visitor can't use the kiosk, reception checks them in from the dashboard: search for the visitor and complete the check-in manually. A dashboard sign-in is recorded on the visitor log with the **Dashboard** sign-in method.

## Check a visitor in from the dashboard

{% stepper %}
{% step %}

### Find the visitor

Search for the visitor on the dashboard.
{% endstep %}

{% step %}

### Check them in

Complete the check-in manually. The sign-in is recorded on the visitor log with the **Dashboard** sign-in method.
{% endstep %}
{% endstepper %}

## How visitors check themselves in

Most visitors check themselves in at the onsite kiosk on arrival. Assisted check-in from the dashboard is the fallback for when that path can't be used.

{% content-ref url="/pages/0Aq74SeJuZLdkygLYC7U" %}
[Check in at the kiosk](/knowledge-hub/kenai-user-guide/visitor-management/kiosk-check-in.md)
{% endcontent-ref %}


---

# 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.security.gallagher.com/knowledge-hub/kenai-user-guide/visitor-management/assisted-check-in.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.