> 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/operational-workflows.md).

# Operational workflows

ASC supports several customer workflows that businesses rely on every day.

Use this page to understand how those workflows usually work in practice.

### After-hours support

ASC answers calls when your office is closed or your team is unavailable.

Your team reviews the resulting messages, updates on-call contacts, and adjusts instructions when needed.

### Lead capture and sales response

ASC can capture lead details and new inquiries when your internal team cannot answer immediately.

This helps sales-driven businesses keep response times fast and reduce missed opportunities.

### Urgent call escalation

ASC can escalate time-sensitive calls based on your contact order, delivery method, and wait time rules.

This is useful when calls must reach the right person fast.

### Daily message follow-up

Your team can review messages in the portal, acknowledge them, and track related activity.

This creates a clear record of what ASC captured and what your team handled next.

### Script and instruction updates

Your business can review the active script and confirm the intake flow still fits your needs.

This matters when your services, availability, locations, or escalation rules change.

### Business examples

#### Law firms

Use ASC for intake calls, urgent legal matters, and message routing to attorneys or intake staff.

#### Plumbers and field service teams

Use ASC for after-hours dispatch, emergency escalation, and routine message taking.

#### Doctors and healthcare-adjacent offices

Use ASC for after-hours coverage, on-call routing, and structured message delivery.

#### Real estate and property teams

Use ASC for new leads, tenant issues, showing requests, and maintenance escalation.


---

# 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://answeringservicecare.com/docs/platform-basics/operational-workflows.md?ask=<question>&goal=<endgoal>
```

`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.