> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/getting-started/project-prep/4.-intro-to-support.md).

# 4. Intro to Support

Knowing where to turn for help — and how that changes as you move from implementation to going live — keeps your team unblocked at every stage.

**During implementation**

While you're building, your **Implementation Team** is your primary point of contact. They run your project, answer configuration questions, and guide you through your requirements and timeline. Lean on them for anything project-specific as you stand up your catalog, journeys, and integrations.

**After you go live**

Once your implementation is complete and you're live on the platform, we formally transition you from the Implementation Team to our **Support Team**. You'll be introduced to the people who become your primary contact for day-to-day questions and ongoing help with product features and functionality as new needs arise.

**Getting help in the app**

Day to day, the fastest way to reach us is **in-app Support**, available right inside PeakCommerce. Use it to ask a question or report an issue without leaving your work — your message reaches our support team, and you can pick the conversation back up from the same place.

**Who and when:** your admin is invited to our Support community around the time your project kicks off. Register promptly — the invitation link expires, and registering early means your team has the channel ready the moment a question comes up.

**Gotcha:** don't wait until you're stuck to set up access. Confirm your admin has accepted the Support invite during kickoff so nothing is blocked later.

That completes Project Prep. From here, move into [Setting Up Your Platform](/product/getting-started/setup.md) to begin configuring — connecting your billing system, building your catalog, and launching your first storefront.


---

# 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.peakcommerce.com/product/getting-started/project-prep/4.-intro-to-support.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.