> 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 lives **inside the admin app**. This help center has its own documentation search, and when you need a human, our customer success team is behind both. Here are all the ways to get help, from quickest to most personal. ## Ask Mango inside the app In the admin app, open the **user menu** (your name, bottom-left) and click **Support**. The Support dialog knows what page you're on and suggests relevant questions — pick one, type your own, or start a **voice session**: Mango holds a natural voice conversation as easily as a typed one. Your question opens the conversation directly, already sent. While you talk, the conversation lives in the bottom-right corner. Collapse it and a small **Mango chip** stays put so you can return to the conversation; close it and the corner is yours again — Mango only appears when you ask for her. If Mango can't hold a conversation right now, the Support dialog says so plainly, keeps the routes to this help center and to support, and re-checks on its own so the assistant returns without a reload. 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. ## Search this help center Mango is not on this site — the search box at the top is GitBook's documentation search. Type a question and pick **AI Answer** to get a written answer assembled from these published pages, with links to the pages it drew on. It answers from the documentation only; it has no view of your tenant's catalog, journeys, or analytics. For anything about *your* setup, ask Mango in the app. ## Open this help center from the app The Support dialog's footer carries a **Docs** link that opens this help center in a new tab, so the full documentation, troubleshooting guides, and known-issues list stay one click from wherever you're working — right next to **Email support**. ## 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. * **Check platform status first** — if the problem looks platform-wide rather than specific to your account, [status.peakcommerce.com](https://status.peakcommerce.com) shows current availability per service (Production and Sandbox are tracked separately) plus any active incident. * **Email** — . 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. See [Contact Support](/support/support-processes/contact-support.md) for the full details on priorities and response expectations. ## Related * [Working with Mango](https://docs.peakcommerce.com/guides/guide-working-with-mango) * [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) * [PeakCommerce Status Page](https://status.peakcommerce.com) --- # 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=&goal= ``` `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.