> For the complete documentation index, see [llms.txt](https://docs.brokvix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brokvix.com/crm-admin/broker-teams/find-client-record.md).

# Find a client record

**For:** Sales, Support, Finance, Risk, Compliance, and administrators with client-list access.

Use this guide to locate an existing client before reviewing their information or starting a follow-up task.

1. Open **Clients → Clients**. If your menu provides a direct **Clients** shortcut, that may open the same list.
2. Check the list heading and selected view. Views and columns may differ by role or organization.
3. Use the list's available search or filters to narrow the results. Confirm the client using more than one permitted identifier before opening a record.
4. Open the matching record and check the page heading and account details before acting.

If the record is absent, first check whether you are viewing **Leads**, **Applicants**, or **Clients**. Then ask your administrator or record owner to verify assignment and permissions. Do not create a second client record just because the original is not visible.

Handle client information only through approved channels and according to your organization's privacy policy.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.brokvix.com/crm-admin/broker-teams/find-client-record.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 `build a script that syncs our docs to a CMS` 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.