> 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/operator-side.md).

# Operator side

What happens after operator receives the call

## Requirements

To conduct Video KYC sessions, operators must have:

<table data-header-hidden><thead><tr><th width="151.78515625"></th><th width="410.5390625"></th></tr></thead><tbody><tr><td>💻 <strong>Device</strong></td><td>A device with a working camera and microphone</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>

### Receiveing the call

Operators create or schedule sessions through the Manage interface. Once a session is set up, it can be coordinated with the applicant for a specific time or left open for them to join when ready.

When the applicant opens their link and clicks **Join**, the operator receives the incoming call and answers to begin the Video KYC process.

## One-on-one session

### **Video call frame**

Once connected, the operator sees a video call frame displaying both parties. The frame has two control panels.

**Top panel**

<table><thead><tr><th width="200.8671875">Control</th><th width="428.1953125">Function</th></tr></thead><tbody><tr><td><strong>Call duration</strong></td><td>Shows elapsed call time</td></tr><tr><td><strong>Virtual backgrounds</strong></td><td>Apply or adjust a custom background during the call</td></tr><tr><td><strong>Device settings</strong></td><td>Adjust camera, microphone, and speaker</td></tr><tr><td><strong>Full screen</strong></td><td>Expand or minimize the video call frame</td></tr></tbody></table>

> Virtual backgrounds are configured by the company administrator in **Company settings**.

**Bottom panel**

<table><thead><tr><th width="127.8125">Control</th><th>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>Capture</strong></td><td>Take a live screenshot of the applicant — saved automatically to the session</td></tr><tr><td><strong>Steps</strong></td><td>Select which verification steps the applicant should complete</td></tr><tr><td><strong>Start</strong></td><td>Initiate the selected step on the applicant's screen</td></tr></tbody></table>

Operators can repeat steps as needed. Steps can also be re-initiated if a result needs to be retaken.

### **Completing the session**

Once all steps are finished:

1. Review the applicant's information and verification results.
2. Make a decision to **Approve** or **Reject** the session.

> Decisions should follow your company's verification protocols. The system provides recommendations based on completed checks — including document scans, liveness detection, and any additional steps in the workflow.

***

### Multi-user session

Multi-user sessions follow the same flow as one-on-one sessions, with the following additions:

* Up to **10 participants** can join a single session, depending on your business process configuration.
* The operator sees all participants simultaneously in the video call frame.
* Verification steps can be initiated **per participant individually** — each participant completes their own workflow within the shared call.
* At the end, the operator approves or rejects the consolidated **parent session**, following company protocol.


---

# 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/operator-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.
