> 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/ai/hybrid-answering.md).

# Hybrid: AI plus live

Hybrid answering combines AI and live agents in one call handling model. The AI handles routine interactions, and live agents step in based on the rules you set.

### Why hybrid

* **Use both models intentionally.** Match the call path to the type of interaction.
* **Automate routine work.** Let the assistant handle common, repeatable calls.
* **Bring in live support when needed.** Route calls that need judgment, empathy, or escalation to an agent.
* **Maintain 24/7 coverage.** Support callers across after-hours, overflow, and business-hour workflows.

### How handoff works

You decide when the assistant should bring in a person. Common triggers include a caller asking for a representative, an urgent or sensitive matter, or a call type you always want a live agent to handle. When a trigger is met, the assistant routes the call to a live agent using your escalation rules.

{% hint style="info" %}
Your routing and escalation rules are configured with your implementation specialist, so hybrid behavior matches how your business actually runs.
{% endhint %}

### Choosing your mode

* **AI** for high-volume, structured call handling.
* **Live** when every caller should reach a trained agent from the start.
* **Hybrid** when you want automation for routine calls and live support for exceptions.

### Where hybrid fits best

Hybrid is a strong fit when your business handles a mix of routine and high-touch conversations.

Common fits include:

* after-hours coverage with live escalation for urgent calls
* overflow support during peak periods
* intake workflows that start with structured questions, then move to a person when needed
* service models that want both efficiency and human support

For a side-by-side of all three models, see [Choosing the right answering model](/docs/ai/choosing-the-right-answering-model.md).


---

# 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/ai/hybrid-answering.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.