> 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

After requesting LinkedIn profiles for suggested logistics contacts from the Magic Map, you can track the status of these requests in the request tracking page.

### 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.shippercrm.com/request-tracking/linkedin-profiles.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 `automate deployments from our CI pipeline` 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.