> For the complete documentation index, see [llms.txt](https://docs.elkyc.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elkyc.com/home/build-verification-flows/verification-steps/intro.md).
# Intro
The Intro step welcomes users, explains the verification process, and provides necessary instructions. It is always positioned at the beginning of the flow and is a vital element for guiding users through the verification journey. It is especially useful when the flow includes multiple steps, ensuring users are well-informed and prepared before they begin.
* Add `Intro Screen` step into the flow canvas at the appropriate position in the flow.
* Click on `Intro Screen` to open its configuration option
### Adding Custom Terms & Conditions and Privacy Policies Links to The Intro Screen
You can customize the Intro Screen in the flow builder by adding your own links to the **Terms & Conditions** and **Privacy Policies**. This feature allows users to review and accept these policies during the verification process without requiring you to add additional steps to the workflow.
* In the **General** tab, locate the **Confirmed Links** section.
* Add your links and `Save` changes:
* Enter the link for your **Privacy Policy** in the respective field.
* Enter the link for your **Terms & Conditions** in the respective field
**User Experience:**
* Users will see checkboxes on the Intro Screen, prompting them to confirm that they’ve read, understood, and agreed to your company’s Privacy Policy and Terms & Conditions.
* Clicking the linked text (e.g., “privacy policy” or “terms of conditions”) will open the corresponding document for review.
***
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.elkyc.com/home/build-verification-flows/verification-steps/intro.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.