> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talentmap.com/knowledge-base/step-1-prepare-for-action/schedule-a-meeting-with-your-consultant-or-project-manager.md).

# Schedule a Meeting with your Consultant or Project Manager

To schedule time with your Consultant or Project Manager, you can access their calendars to see availability and eliminate back and forth emails. 

1. Access the TM team member's calendar 
   * **Option A:** If visibl&#x65;**,** click on the <mark style="color:orange;">**Book My Calendar**</mark> link in the persons email signature.&#x20;
   * **Option B:** Log in to Klient and open the task associated with your meeting request. *For example, 6.1 HR Preview of Survey Results*. Click on the meeting link provided.
2. Select the meeting option that best fits your needs.&#x20;
3. IMPORTANT: Add meeting details to your request. You can also include additional guests under the Events Detail page in the booking page.
4. An email confirmation will be sent to you, at the address provided, to confirm your meeting.


---

# 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.talentmap.com/knowledge-base/step-1-prepare-for-action/schedule-a-meeting-with-your-consultant-or-project-manager.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.