> For the complete documentation index, see [llms.txt](https://layerlabs.gitbook.io/phone-verification-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://layerlabs.gitbook.io/phone-verification-system/features-and-screenshots/client-features.md). # Client Features * Seamless customer experience to verify a customer's phone number * Phone number is automatically fetched from the client's profile * Client can edit the phone number in case it is incorrect * Client can start the verification process * Client can input the OTP verification code from either SMS or Voice verification * Client uses intl-tel-input input field to enter phone number (if required) * Client can see proper error messages on duplicate number used, wrong verification code, exceeding tries/attempts limit, etc. * Client can see success message on successfully verifying their phone number * Client Area Account Dropdown Link (if enabled by admin) * Multilang support * Lagom theme support --- # 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://layerlabs.gitbook.io/phone-verification-system/features-and-screenshots/client-features.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.