> For the complete documentation index, see [llms.txt](https://answeringservicecare.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://answeringservicecare.com/docs/app/client-portal.md).

# Client Portal

Overview of client-facing workflows in the ASC Client Portal.

## User Portal

The ASC Client Portal is the customer-facing workspace for managing your service.

Use it to review messages, maintain Oncall coverage, manage users, pay bills, and monitor account activity.

<figure><img src="https://content.gitbook.com/content/4Hhj7GAvWHgdfaC9Z56e/blobs/BdMRpROnMq0C7my7pjMo/ASC%20User%20Portal.png" alt="ASC Client Portal"><figcaption><p>The ASC Client Portal gives clients direct access to messages, account activity, and self-service tools.</p></figcaption></figure>

### What you can manage

Use the portal to:

* review new and acknowledged messages
* manage account users and access
* view active scripts and call handling instructions
* maintain Oncall contacts, delivery methods, and events
* review profile settings, reports, billing, and API access

### Who this is for

The portal is built for the people on your team who need visibility and control.

That often includes business owners, office managers, dispatchers, intake coordinators, and operations leads.

### Common customer outcomes

Businesses often use the portal to:

* review after-hours calls each morning
* track urgent calls and escalations
* keep lead capture and intake scripts current
* update coverage during nights, weekends, and holidays

### In this section

* Access and dashboard
* Accounts and users
* Messages
* Scripts
* Oncall calendar
* Billing and payments
* Profile, reports, and API keys
* Customer resources

### Shared reference

* API reference
* Integrations

### Best for

* clients and account owners
* user admins managing access
* teams reviewing messages, Oncall routing, billing, and reports


---

# 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://answeringservicecare.com/docs/app/client-portal.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.