> 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/linkedin-profiles.md).

# LinkedIn Profiles

### Overview

Submitting a request for LinkedIn profiles for logistics contacts near a particular facility will kickoff a research process to find relevant contacts.

This process can take up to 48 hours and can be tracked easily from the `Requests for LinkedIn profiles` tab in the Requests Tracking Page.

### Tracking your LinkedIn profile requests

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 LinkedIn profiles` tab above the table. This tab is typically selected by default, but if it isn't, go ahead and click it.
3. The table data will update to show all the LinkedIn profile requests that you have submitted and the status for each request.
4. For any completed LinkedIn profile requests, you can click on the result and it will take you to the [Shipper Profile](/magic-map/shipper-profiles.md) on the Magic Map, where you can add it to the CRM for further use.


---

# 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/linkedin-profiles.md?ask=<question>&goal=<endgoal>
```

`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.