> 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/platform-concepts/additional-information-requests.md).

# Additional information requests

Request additional verification steps from applicants within an existing session, without losing audit history.

### How it works

When an operator triggers an additional information request, a new verification link is generated for the applicant. The operator sends it via Manage — by SMS, email, or by copying and sharing the link manually. The session ID visible in Manage remains the same throughout all verification requests.

Upon opening the link, the applicant is presented only with **the steps defined in the new verification request.** Previously completed steps are not shown to the applicant and their data is not modified.

Decisions (automatic or manual) apply to the current verification request only. Once all steps in the request are completed, the standard decision flow runs as normal.

***

### Session status

A new session status is introduced for this feature:

<table><thead><tr><th width="302.0625">Status</th><th>Description</th></tr></thead><tbody><tr><td><code>additional_information_requested</code></td><td>The session has been returned to the applicant for further verification. Sits between a terminal state and <code>in_progress</code>.</td></tr></tbody></table>

#### **Status transitions:**

```
approved / rejected / manual_check / expired
        ↓
additional_information_requested
        ↓ (applicant opens the link)
in_progress
        ↓
approved / rejected / manual_check
```

***

### Verification history

A session can go through multiple verification requests over its lifetime. Each request generates its own set of steps based on the selected configuration. If a step type was completed in a previous request, it is generated again as a new attempt — full history is preserved and accessible for audit purposes. The latest attempt per step is used for review and decision-making.

***

### Enabling the feature

* **How to enable**: [Toggle this setting](https://docs.identomat.com/no-code-workflows/configuration-settings.md#request-additional-information) on in the **Configuration settings** tab of the configurations builder.&#x20;

```json
"sessionConfig": {
  "id": "6792031d9e97ea46872e190c",
  "name": "My Configuration",
  "additionalInformationRequest": true
}
```

When enabled, operators will see the **Request more information** button on eligible sessions in Manage.

Configurations available for selection when making a request are filtered by the operator's group membership, consistent with access control rules applied elsewhere in the platform.


---

# 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/platform-concepts/additional-information-requests.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.
