Human approval for AI customer support: read the reply before your customer does

Human approval for AI customer support in Hay.chat holds an agent's replies until someone on your team approves, edits or blocks them. Refunds and other actions follow your playbook rules instead.

Hay.chat
Online
Hi, it's been 9 days. Where's order 5521?
Looking up order #5521 in Shopify
Shopify
Checking your shipping policy
Sorry for the wait. Order 5521 shipped on Tuesday and the courier has it in Lyon now. I'll send you the tracking link so you can follow it.
Drafted for your approval Approve Reject
The lookups ran on their own. The reply waits for someone on your team to approve, edit or block it.

Published

Human-in-the-loop

What does human-in-the-loop mean in customer support?

Human-in-the-loop (HITL) means a person sits at a checkpoint in an AI workflow and can stop or change what the AI does before it counts. In support, the checkpoint that matters is the reply, and that's the one Hay.chat holds.

Even a good AI is wrong sometimes, ours included. A refund window that's 14 days in your policy and 30 in the reply gets caught by a teammate in seconds. More in our safe AI patterns guide.

Which AI replies need approval, and how does it look?

Speech bubbles sliding down a forked slide: most ride the long branch straight out, one waits in a tray under a yellow lamp
1

You pick the agents

Approval is off by default and on every plan. Switch on Require Approval for one agent, or for the whole workspace in Settings, then General.

Human-in-the-loop in customer support: blue speech bubbles circling a looped track, one paused under a navy arch with a small yellow lamp
2

The reply waits

The agent runs its lookups and writes the reply as usual, but it lands in the conversation as "Pending" instead of going out.

A blank speech bubble waiting on a pedestal with a small yellow lamp, a green chip, a red chip and a pencil laid out in front of it
3

Your team decides

Approve it, edit it first or block it. Nothing reaches the customer until you do. If a draft is beyond an edit, take over the conversation.

Our take: turn it on for any new agent and move it to Auto-Send once you've stopped editing its drafts. The settings are in the agents guide.

A clipboard on a post beside a lever sets railway points: small parcels roll down the main track while one is switched onto a side track toward an open door

What about actions like refunds?

Approval mode doesn't hold actions, and we'd rather you hear that now than in week one. Refunds and order changes follow your playbooks, so the limit goes there:

  • "Refund damaged items up to €50 within 30 days of delivery. Anything over €50, pass it to the team."
  • "For refund requests outside the policy, collect the order number and the reason, then escalate."

One Shopify catch: cancelling an order doesn't refund it on its own. The actions list shows what each integration can do.

A tall card-catalogue cabinet with one drawer pulled out, packed with blue cards, one speech-bubble card lifted out and glowing yellow

What record do you get of what the AI did?

Every conversation keeps its full thread, timestamped, including anything your team sends after taking over. Export it as a PDF or CSV, or self-host to keep it all on your own servers.

Account activity is logged separately under My Profile, from logins and password changes to API keys created or revoked.

Should every AI reply need approval, or should the agent send on its own?

Most teams run both, split by agent. Approval costs your team's time. Autonomy costs you the occasional bad reply.

Swipe the table sideways to see every column.

Three ways to run an AI agent in Hay.chat, reviewing every reply, reviewing by confidence or fully autonomous, compared by setting, your team's time, risk and fit.
Start here Review every reply Review by confidence Fully autonomous
Setting Require Approval on the agentAuto-Send, with Human Escalation onAuto-Send, with Human Escalation off
Your team's time Someone reads every reply, and chats that come in at night wait for the morningOnly the conversations the agent isn't sure aboutNone, until something goes wrong
Risk Lowest. A bad draft only gets out if the reviewer misses itMedium. A confident wrong answer still goes outHighest. Low-scoring replies are sent as they are
Fits New agents, refunds and complaints, your first weeksOrder status, shipping and policy questions, once your documents are solidHardly anyone

Time and risk are our judgement from running support teams, not measured data.

Switch on approval for one agent and read what it would have sent

Turn on Require Approval, put your refund limits in a playbook, and read its drafts until you trust them. Free for 30 days, no credit card.

  • 30-day free trial
  • No credit card required
  • Set up in under 10 minutes
  • Hosted in Europe

Frequently asked questions

HITL stands for human-in-the-loop: a person reviews or corrects an AI system's output at a set point instead of letting it run unchecked. In customer support that usually means approving AI replies before they're sent, or taking over conversations the AI isn't sure about. Hay.chat supports both.

Written by Damien Mulhall. Last reviewed against Hay.chat's agents and conversations documentation.