> For the complete documentation index, see [llms.txt](https://docs.identomat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.identomat.com/video-kyc/end-user-side.md).

# End-user side

This page explains what end users will experience during a Video KYC session — from opening the link to completing verification.

## Requirements

Before starting, users should have the following ready:

<table data-header-hidden><thead><tr><th width="176.46484375"></th><th></th></tr></thead><tbody><tr><td>💻 <strong>Device</strong></td><td>A device with a working camera and microphone</td></tr><tr><td>🪪 <strong>Document</strong></td><td>A valid identity document — Passport, Identity Card, Residence Permit, or Driver's License</td></tr><tr><td>🌞 <strong>Lighting</strong></td><td>A well-lit environment</td></tr><tr><td>🛜 <strong>Connection</strong></td><td>A stable internet connection</td></tr></tbody></table>

## One-on-one session

### Joining the call

When the user opens their Video KYC link:

1. Identomat's verification widget launches automatically in their default browser.
2. Depending on the configuration, the user may need to complete preliminary steps — such as reviewing and agreeing to terms — before proceeding.
3. Once ready, the **video call frame** appears with a bottom panel containing:

<table><thead><tr><th width="157.7265625">Control</th><th width="452.93359375">Function</th></tr></thead><tbody><tr><td><strong>Audio</strong></td><td>Mute / unmute microphone</td></tr><tr><td><strong>Video</strong></td><td>Turn camera on / off</td></tr><tr><td><strong>Flip</strong></td><td>Mirror the camera view</td></tr><tr><td><strong>Switch</strong></td><td>Toggle between front and back camera <em>(if available)</em></td></tr><tr><td><strong>Join</strong></td><td>Connect to the operator and start the call</td></tr></tbody></table>

4. The user clicks **Join** to initiate the call. A **Connecting** screen is shown until the operator answers.

Once connected, a top panel becomes visible with:

* **Call duration** — displayed in the top-left corner
* **Device settings** — adjust camera, microphone, and speaker mid-call
* **Full screen** — toggle the video frame size

The operator's video appears in the corner of the frame, outlined in yellow to indicate an active connection.

### During the call

The operator conducts the verification interview in real time. Depending on the configured workflow, the user may be asked to:

* Present their identity document
* Complete a liveness check
* Answer additional verification questions

All steps take place within the video call frame — no separate screens or redirects.

### Ending the call

Once verification is complete, the operator will typically share the result. Either party can end the call:

1. Click **End**.
2. Confirm in the dialog that appears.

### Multi-user session

Multi-user sessions follow the same flow as one-on-one sessions, with two key differences:

* **Participants can see and hear each other**, in addition to interacting with the operator.
* **Each participant completes their own verification workflow simultaneously** — steps are independent, even within the shared call.


---

# 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://docs.identomat.com/video-kyc/end-user-side.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.
