> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/partner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/partner/messaging/utility-messages/automation-human-handoff-and-quick-replies.md).

# Automation, Human Handoff and Quick Replies

### Deciding when to use automation vs. human handoff

To determine when to automate interactions and when to involve human agents, organizations should categorize customer service scenarios by complexity and emotional sensitivity.

Simple tasks such as status updates and basic confirmations are ideal for full automation. Frequently asked questions can be handled by a chatbot, with the option for human escalation.

Complex inquiries should receive automated acknowledgment followed by a handoff to a human agent. Emotional or sensitive issues, as well as high-value customer interactions, should be directed to human agents with adequate context.

For problem resolution, an automated triage system should first assess the issue before routing it to the appropriate human team. To support effective handoff decisions, companies should implement clear triggers that detect when automation is insufficient.

#### Scenarios best for full automation:

\-  Simple status updates

\-  Basic confirmations

#### Scenarios requiring human escalation:

\-  Frequently asked questions → Chatbot with human escalation

\-  Complex inquiries → Automated acknowledgment, then human agent

\-  Emotional or sensitive issues → Human agent with context from an automated system

\-  High-value customer interactions → Priority routing to specialized human agents

\-  Problem resolution → Automated triage, then appropriate human team

#### Handoff triggers to implement:

\-  Specific customer keywords

\-  Multiple clarification requests

\-  Complex question detection

\-  High customer value indicators

\-  Sentiment analysis results

\-  Request for human assistance

### Best practices for effective quick replies:

1\.   Keep options binary or limited: 2-3 clear choices maximum

2\.   Use parallel structure: Consistent grammatical format

3\.   Be specific and actionable: A Clear outcome for each option

4\.   Design full conversation flows: Map all possible paths

5\.   Test thoroughly: Verify button display across devices

7\.   Create response libraries: Standardized answers to common replies

Example utility message with quick replies: "Your order #12345 has been delivered to the front desk at 123 Main St. Did you receive your package?" \[Yes, received] \[Not received].

\ <br>


---

# 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:

```
GET https://docs.360dialog.com/partner/messaging/utility-messages/automation-human-handoff-and-quick-replies.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.