> For the complete documentation index, see [llms.txt](https://docs.browsee.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.browsee.io/understand-your-users/session-search/automatic-session-tags/high-input-time.md). # High Input Time It means we will identify any form field where users are spending a lot of time before typing something. It might mean that either the field name is confusing or they do not intend to give you that information so early in the flow. You can analyze the sessions and make a conclusion basis that. **Example:** When you try to book an insurance, sometimes they ask you for phone number and email even without showing a list of policy or so. This makes a lot of users wonder and they spend a good amount of time thinking whether to give it or not. Maybe, the thing to do is to first build trust or first help before asking for personal details. Also, one time we tagged a sessions where someone wrote '**Name/Email**' in the field name and a user tried to fill the field as '**xyz/xyz\@gmail.com**' after spending quite some time. --- # 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.browsee.io/understand-your-users/session-search/automatic-session-tags/high-input-time.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.