> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/account-intelligence/customer-overview.md).

# Customer Overview

See the accounts, signals, and work that need your attention in one place

The CSM & CS Leader Overview is your home base for customer success. Open it from [Customers > Overview](https://app.usepylon.com/customers/home) to see your book of business, the accounts that need attention, and the work due today, all on one page.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FG4lSVWqnGfHYMy5f5Fzx%2Foverview-hero.png?alt=media&amp;token=78b0635d-8bd0-4cee-83a0-97d867647d4a" alt="The Customer Overview page"><figcaption></figcaption></figure>

Use it to:

* Plan your day with your meetings, projects, tasks, and issues
* Spot churn risks, upcoming renewals, and upsell opportunities with [Signals](/pylon-docs/account-intelligence/customer-overview/signals.md)
* Track revenue and account health with charts
* Give each team its own set of views with [Overview Boards](/pylon-docs/account-intelligence/customer-overview/overview-boards.md)

### Daily Overview

The panel on the left shows your meetings for today, projects and tasks due soon, and issues waiting on you. Choose **Configure** from a section's **...** menu to change its filters. Meetings require a connected [Calendar](/pylon-docs/integrations/calendar.md).

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FCbw6t7TF8cdhlZTGpuAw%2Fdaily-overview.png?alt=media&amp;token=2bb4d4ad-5f88-4f16-a30f-e3408f2c0bd7" alt="The daily overview panel" width="320"><figcaption></figcaption></figure>

### Default Views

Everyone starts with the **CSM Home** view, which shows the accounts you own with a Signal table and an Accounts table. Your workspace may also include a **CS Leader Starter Template** with revenue charts (GRR and NRR), signals, and accounts. Add it from **+ View**.

Admins can choose which views each team sees by setting up [Overview Boards](/pylon-docs/account-intelligence/customer-overview/overview-boards.md).

***

{% content-ref url="/pages/riA2qBrW8ut37hVxBFyj" %}
[Signals](/pylon-docs/account-intelligence/customer-overview/signals.md)
{% endcontent-ref %}

{% content-ref url="/pages/6TXCWcDiZlgLTHph78oB" %}
[Overview Boards](/pylon-docs/account-intelligence/customer-overview/overview-boards.md)
{% endcontent-ref %}

{% content-ref url="/pages/g7KAWSWUGTlFPbnT6RIV" %}
[Views](/pylon-docs/account-intelligence/customer-overview/views.md)
{% endcontent-ref %}

{% content-ref url="/pages/wpgLWFWejXXf1ePN2hxq" %}
[Blocks](/pylon-docs/account-intelligence/customer-overview/blocks.md)
{% endcontent-ref %}


---

# 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.usepylon.com/pylon-docs/account-intelligence/customer-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.
