# Scanning Tickets

## Step-by-step Instructions

{% hint style="warning" %}
If you have not already imported the verifier policy, please follow [this guide](/documentation/for-verifiers/how-to-guides/verifier-app/importing-a-policy.md).
{% endhint %}

### Scanning

1. Scan the **tokenproof Event Ticket** on your guest’s screen with the **tokenproof Verifier App**.

<figure><img src="/files/OpIAEQcChyFPy4sltU6V" alt=""><figcaption></figcaption></figure>

2. Once the tokenproof **Event Ticket** has been scanned, the tokenproof Verifier will either display a “**tokenproof Approved**” or “**tokenproof Denied**” message.

{% hint style="info" %}
To better asses an issue or reason for rejection, refer to the [Verifier Tools](/documentation/for-verifiers/how-to-guides/verifier-app/verifier-tools.md) guide.
{% endhint %}

<figure><img src="/files/pIdNtMCy7cRWPEnBpvuL" alt=""><figcaption></figcaption></figure>

### Check-in Manually

1. If the user’s ticket QR code is not scanning, try “**Manual Check-in**” found at the bottom of the Verifier app’s scanning screen.\
   \
   On your guest’s app, click ‘View details’ below their QR code. At the bottom of their screen, you will see a '**Ticket ID**'. Input this into your Verifier app.

<figure><img src="/files/OjPpMUNC5qAqBh1oOdKQ" alt=""><figcaption></figcaption></figure>

### Verifier Analytics

1. As guests enter an event, **Verifiers can keep track of unique guests and total scans**. We break down total guests by specific ticket types for ticketed events. This can be found via the ‘**Analytics**’ icon on the upper left corner of the tokenproof Verifier app.

<figure><img src="/files/f13E631QfMSoubhOKIfl" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tokenproof.xyz/documentation/for-verifiers/how-to-guides/verifier-app/scanning-tickets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.