> 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/customer-success-portal/customer-success-portal-overview.md).

# Customer Success Portal Overview

The customer success portal is the workspace for **CSRs** (and customer-success / account-executive roles) to manage customer accounts on a customer's behalf — looking up accounts, reviewing subscriptions, running changes, and handling support cases.

## What CSRs can do

* **Find and view accounts** — search the accounts they're responsible for and open a customer's details and subscriptions. Accounts are reachable from the **global header search** anywhere in the app or from the filterable **Your Accounts** list — see [Finding Accounts](https://docs.peakcommerce.com/product/customer-success-portal/finding-accounts.md).
* **Work a single account** — the account detail page collects the customer's identity (including a link to their record in your CRM), key metrics, subscriptions, billing history, payment methods, and any journey work in flight — see [Working with an Account](https://docs.peakcommerce.com/product/customer-success-portal/working-with-an-account.md).
* **See the whole history** — the account's **Timeline** merges lifecycle events, plan changes, billing activity, retention flows, and staff notes into one staff-only feed, with notes that can also be logged to your CRM — see [The Account Timeline](https://docs.peakcommerce.com/product/customer-success-portal/account-timeline.md).
* **Navigate account hierarchies** — a **Subaccounts** subtab lists the account's children straight from the billing system's own hierarchy, with one-click navigation into each — see [Working with an Account](https://docs.peakcommerce.com/product/customer-success-portal/working-with-an-account.md).
* **Act on a customer's behalf** — run plan changes, cancellations, and other tasks via **CSR Self-Service** [journeys](https://docs.peakcommerce.com/product/journeys-and-pages/journey-basics/journeys-overview.md).
* **Handle cases** — view and manage support cases pulled from your connected support system.

A CSR's reach is scoped by their [role and profile](https://docs.peakcommerce.com/product/using-peakcommerce/users-and-user-roles/user-roles.md) — record access can be limited to, say, only the accounts assigned to them. Admins can view a CSR's workspace by impersonating them from the **user menu** (your name, bottom-left) → **Settings → Users**.


---

# 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/customer-success-portal/customer-success-portal-overview.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.
