Home›AI Agency Academy›Lesson 20
Module 05 · Lesson 20

Handle difficult conversations

Design for uncertainty, complaints, sensitive requests, and emergencies before launch.

Last updated August 5, 2026•15–25 minutes•Free AI agent course
What you will learn

Build the escalation playbook

You will be able to write a practical escalation policy that protects customers, staff, and the business when an agent reaches a boundary.

Why this matters

Good agent work is useful before it is impressive.

The right response to a difficult conversation is often not a better answer. It is a calm acknowledgement, an approved safety or service step, a human handoff, and a record that lets the owner understand what happened.

Core concepts

The language that keeps the work clear.

Sensitive requestA request involving personal, medical, legal, financial, safety, or other client-defined high-impact matters.
ComplaintA signal that the customer’s experience or expectation needs human attention, not an argument from the agent.
Emergency pathClient-approved instructions for immediate risks that must not rely on an agent’s judgement.
Escalation recordThe facts, stated concern, time, original context, and owner needed for responsible follow-up.
The practical method

How to build the escalation playbook

Define categories with the client

Use the client’s own policies and expert owners to list sensitive, urgent, abusive, and out-of-scope categories.

Write a short response

Acknowledge the issue, avoid unsupported advice or promises, and tell the person the safe next step.

Route by severity

Specify who receives the case, how quickly, and what extra context is required.

Review patterns

Inspect difficult cases for policy gaps, recurring frustration, and improvements to the normal journey.

Worked example

Worked case: handle difficult conversations

A utility-services company’s agent receives a message about a possible gas leak. The agent does not troubleshoot or ask a long series of qualification questions.

It presents the client-approved urgent guidance, instructs the person to contact the relevant emergency service, and flags the conversation for the on-call team according to policy. The activity is logged with the exact message and timestamp.

A separate complaint path acknowledges the concern, captures the relevant account detail securely, and creates an owned case without debating the customer.

Build it in practice

Complete the working artifact

Category: [type]. Do not do: [prohibited response/action]. Approved message: [short text]. Immediate route: [owner/channel]. Required record: [fields]. Review owner: [role].
Practice

Before you move on

  • Create three difficult-conversation scenarios for the client’s reality.
  • Have the policy owner approve the first response and route.
  • Test that the agent can stop rather than continue collecting detail.
  • High-impact categories are defined by the client’s policy owners.
  • The agent does not give expert advice beyond its authority.
  • Urgent cases have a clear immediate route.
  • Every escalation leaves a reviewable record.

Lesson progress

Finished this lesson?

Save your place on this device so it is easy to pick up where you left off.

Not marked complete yet.