> 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/products/cc-software/operate/visitor-management-client/receptionist-functions/the-home-screen/visitors-displayed-on-the-home-screen.md).

# Visitors displayed on the Home screen

### Introduction

A time slot can be configured by your Command Centre administrator that determines which visitors are displayed on the 'Expected' and 'Departed' Home screen status tabs.

### Time slot options

The time slot is configured using one of the following options:

* show all today’s visits

OR:

* show all visits occurring ‘x’ hours before the current time and ‘y’ hours after the current time, (e.g. minus 'x' hours plus 'y' hours)

### Time zones

Where the time slot is 'show all today’s visits' the reception will show all today's visits, for the reception's time zone.

Where the time zone is 'show all visits occurring **x** hours before the current time and **y** hours after the current time' the reception will show all visits relative to the workstation's time zone.

### Time zone example

Two reception locations:

* New Zealand (UTC +13)
* South Africa (UTC +2)

New Zealand is 11 hours ahead of South Africa.

If the time slot is 'show all today's visits'

<table><thead><tr><th width="198">Workstation time zone</th><th>Receptions</th></tr></thead><tbody><tr><td rowspan="2">New Zealand Date: 02-02-09 Time: 9:00a.m.</td><td><strong>New Zealand Reception</strong> You will see all visits for the 02-02-09</td></tr><tr><td><strong>South Africa Reception</strong> You will see all visits for the 01-02-09</td></tr></tbody></table>

If the time slot is 'show all visits occurring 2 hours before the current time and 4 hours after the current time':

<table><thead><tr><th width="198">Workstation time zone</th><th>Receptions</th></tr></thead><tbody><tr><td rowspan="2">New Zealand Date: 02-02-09 Time: 9:00a.m.</td><td><strong>New Zealand Reception</strong> You will see all visits due between 7:00a.m. and 1:00p.m. on the 02-02-09 (New Zealand Time)</td></tr><tr><td><strong>South Africa Reception</strong> You will see all visits due between 7:00p.m. on the 01-02-09 and 2:00a.m. on the 02-02-09 (South African Time)</td></tr></tbody></table>


---

# 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/products/cc-software/operate/visitor-management-client/receptionist-functions/the-home-screen/visitors-displayed-on-the-home-screen.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.