> 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/support/getting-help-from-mango.md).

# Getting Help from Mango

Help is never more than a click away in PeakCommerce. **Mango** — our resident mongoose and AI assistant — is the fastest first stop, and she's available both **inside the app** and **right here on the docs site**. When you need a human, our customer success team is behind her every step of the way. Here are all the ways to get help, from quickest to most personal.

## Ask Mango inside the app

Administrators see a **floating Mango bubble** on every page of the admin app. Open it and ask your question however you prefer — **type in chat, or just talk**: Mango holds a natural voice conversation as easily as a typed one.

What sets the in-app Mango apart is that she answers from **your own tenant's live configuration**, not just general documentation:

* **Your product catalog and pricing** — products, plans, charges, and what each plan costs.
* **Your journeys** — the steps, routing, and commerce actions of every journey you've configured, so she can explain *why* a flow behaves the way it does.
* **Live journey activity** — recent journey-session activity in aggregate. Customer identity and captured form data are deliberately kept out of Mango's view; for individual-customer questions she'll direct you to the session view in the app.
* **Retention analytics** — cancellation reasons and save rates, computed from the same source as the app's Retention analytics tab, so her figures always match your dashboards.

Mango's in-app knowledge is **strictly read-only**: she can explain and diagnose, but she can never change your catalog, journeys, or settings. And every conversation is tied to your organization and user, so if you escalate to our support team afterwards, they have the context.

## Ask Mango on this docs site

Right here in the help center, use the **Ask Mango** button (or the search box) to ask anything in plain language — she answers from the documentation and links you to the relevant pages.

<a href="https://docs.peakcommerce.com/?ask=" class="button primary">Ask Mango</a>

## Open this help center from the app

In the admin app, open the **user menu** (your name, bottom-left) and click **Support** — it opens this help center in a new tab, so the full documentation, troubleshooting guides, and known-issues list are always one click from wherever you're working.

## Contact support

When you need a person, the best way to get day-to-day support is to email our customer success team — it lets us track progress and keep a single thread, so nothing is overlooked.

* **Email** — <support@peakcommerce.com>. Note that emailed tickets aren't assigned a priority and may not be prioritized accordingly.
* **Slack** — most customers have a direct Slack channel our customer success team oversees for near-real-time collaboration. Use it if your organization has one.
* **Telephone (emergencies)** — we're available for technical emergencies 24×7×365 by phone. For an Urgent (P0) or High (P1) issue outside business hours, call **US: +1 858-261-7778**.

See [Contact Support](/support/support-processes/contact-support.md) for the full details on priorities and response expectations.

## Related

* [Contact Support](/support/support-processes/contact-support.md)
* [Troubleshooting](/support/troubleshooting/unable-to-login-to-peakcommerce.md)
* [Known Issues](/support/known-issues/known-issues.md)


---

# 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.peakcommerce.com/support/getting-help-from-mango.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.
