> 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/platform-basics/portal-navigation.md). # Portal navigation Understand what ASC handles for you and what you manage in the ASC Client Portal. ASC handles the live answering work for you behind the scenes. Most customers only need the ASC Client Portal. Use it to review results, manage access, and keep your instructions current. ### What ASC handles for you ASC agents and internal teams handle the live work tied to your service. That can include: * answering calls and capturing messages * following your script and intake flow * escalating urgent calls * routing leads, support requests, and after-hours inquiries * delivering messages based on your instructions ### What you manage in the ASC Client Portal The portal is where your team stays aligned with ASC. Use it to: * review messages and activity * manage users and access * review scripts * maintain on-call contacts and escalation paths * view reports, billing, and integrations where enabled ### Typical customer users The portal is usually used by: * business owners * office managers * dispatch coordinators * intake teams * operations leads ### Start in the right area If you are new to the portal, start here: * Access and dashboard * Accounts and users * Messages * Scripts * Oncall calendar {% hint style="info" %} If you are not sure where to begin, use Introduction. {% endhint %} --- # 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/platform-basics/portal-navigation.md?ask=&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.