> 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/get-started/user-roles-overview/receiving-calls.md).
# Receiving calls
Call center operators can receive end-user calls and conduct the video verification process.
In Identomat's system, only users with the **Call center operator** role are responsible for receiving calls. When this role is enabled, a call toggle will appear at the top of the page. Activating this toggle allows the system to receive calls from end-users.
When an end-user initiates a call, an incoming call animation will appear, and the Call center operator will hear a ringing sound. After answering, the operator connects with the end-user and can begin the verification steps configured for that session.
If no Call Center Operator has the toggle active, incoming calls will not be received. Ensure at least one operator is available before end-users begin sessions with a video call step.
**Call center operators** may:
* Take live screenshots of the end-user.
* Fill out operator questionnaires during the session.
* Initiate KYC steps for the end-user.
For more details, see:
Video KYC
Learn how live video verification works, including the full operator and end-user flow, call controls, and compliance features.
---
# 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/get-started/user-roles-overview/receiving-calls.md?ask=&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.