> For the complete documentation index, see [llms.txt](https://docs.shippercrm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shippercrm.com/request-tracking/contact-enrichment.md).
# Contact Enrichment
### Overview
When you submit a contact enrichment request in Shipper CRM, it goes to a team of humans that source and validate the phone number and / or email for the contact.
This process typically takes 1-3 business days, and is easily trackable from the `Requests for Contact Enrichment` tab in the Requests tracking page.
### Tracking your contact enrichment request
1. Hover over the left sidebar in Shipper CRM to expand it and then click on the `Requests` option in the expanded sidebar. This will take you to the Requests Page.
2. Once you're on the Requests Page, click on the `Requests for Contact Enrichment` tab above the table.
3. The table data will update to show all the contact enrichment requests that you have submitted and the status for each request.
4. For any completed enrichment requests, you can click on the result and it will take you to the CRM where you can view the emails and phones that were found and [manage the relationship](/relationship-manager/overview.md) further.
Pending and completed requests for contact enrichment will appear here
---
# 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.shippercrm.com/request-tracking/contact-enrichment.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.