Skip to content
Start Free

Keep your support AI from promising refunds, with guardrails

Artur PilchNov 18th, 2026

Your team answers tickets about mail, DNS and unpaid invoices, and an AI drafts the replies. The drafts are good, so nobody reads every line now. The reply you worry about is the one that promises a customer a free month nobody approved. With AI support guardrails, a reply with that sentence is never sent on its own.

Instructions tell Konrado how to answer. A guardrail is the rule where breaking it means the reply does not go out on its own, however confident Konrado is about it. Write those rules before anything else. Konrado has them in front of it while it works out what to say and while it writes the draft. Before a reply can go out on its own, the finished text is checked against them once more.

Which rule catches a credit depends on who mentions it, as the diagram below shows.

A decision: who mentions a credit? The customer leads to Always hand to a person, and the draft leads to a guardrail.
This article follows the green path, a credit offered in a draft when the customer did not ask for one.

Day one: the sentences that would cost you money

A sentence belongs in a guardrail when sending it once would cost the company money or bind it to a promise. A sentence that is only unhelpful, or in the wrong tone, goes in the instructions, which tell the agent how to answer. Every team has three or four of the first kind.

The screens here come from Larkmoor Hosting, demo data we built, with invented customers and staff. On the agent’s Instructions page, Add guardrail opens an editor for the rule, up to 80 characters, and an optional note. Larkmoor’s first rule is open in that editor below, with a note that says who decides.

The Guardrail editor open on the rule Never promise a refund or a credit, with its note: Billing decides. Say that someone from billing will reply.
The note tells the agent what to say in its place: that someone from billing will reply.

Larkmoor keeps four rules in all. A hosting team could start from the same list.

Four guardrails on the Instructions page, one line each, two of them with a note, under the words Apply on every channel, above the instructions.
The words above the list say the rules apply on every channel and rank above the instructions.

The morning after an outage

Larkmoor has auto replies on. Its support lead starts the day in the Auto-reply history, filtered to Guardrail broken. The filter leaves one row, an outage ticket from the evening before.

The Auto-reply history filtered to Guardrail broken: one outage ticket marked For a person, with its confidence, handled by a team member.
The confidence beside the reason reads Great, and the row still says For a person, with the name of whoever answered.

A shared server had stopped that afternoon. At 19:40 a customer wrote that their site had been offline from about three until five. They asked what happened, and whether it was fixed. Konrado’s draft gave the times and said nothing was lost. Then it added a line the customer had not asked for: “To make up for it, your next month is free.”

The draft scored above Larkmoor’s confidence bar, so on score alone it would have gone out. The check before sending caught the free month and held the reply for Larkmoor’s team, with the reason Guardrail broken. A person on the team opened the draft at 19:47. At 20:05 they sent it without the free month, and ended it by asking the customer to write back if a booking still failed.

The row’s details show the customer’s message, the held draft, the reply that was sent and the reason.

A held row's details: the draft that promises a free month, the reply the team sent without it, and Guardrail Broken naming the rule.
Under AI Reasoning, Guardrail Broken quotes the free month line and names the rule it broke.

A draft can still carry a sentence a rule forbids, as this one shows. The rest of it went out as Konrado wrote it.

A team can let confident drafts go out on their own, and a draft that breaks a guardrail still goes to a person. Chris Danks is Managing Director of The Hosting Heroes, a hosting provider in the UK. In their case study, he says they chose Konrado because “it automatically drafts a high-quality reply for nearly every ticket”.

If the customer asks for the credit

When the customer asks for a refund or a credit, the ticket should reach a person before any draft is scored. A guardrail is the wrong tool for that. It stops a reply that breaks it, and a draft saying someone from billing will reply breaks no rule. Those tickets belong under Always hand to a person, on the Auto replies page.

Larkmoor’s own list names what the customer asks for, one rule per line.

The Always hand to a person rules: a customer who asks for a refund or a credit, or wants to cancel a plan, a domain or an add-on.
The text above the rules says a match is never answered on its own, whatever the confidence.

The refund and credit rule did not match the outage ticket, because the customer did not ask for a credit. The draft offered one, and the guardrail held it back.

Billing may later approve a credit for a customer. The person on the ticket can then ask Konrado to improve the draft and add it. Guardrails do not apply to that request, because the person asked for the change on purpose.

Teams this order does not fit

If a person reads and sends every draft, and nothing goes out on its own, the instructions matter more than which you write first. The guardrails still shape their drafts, but a broken one costs nothing until someone sends it.

On a desk bound by a long contract, the sentences that could cost money will not fit in a few rules of 80 characters. Put a person on those tickets instead of writing a longer list.

What to do now

Open your agent’s Instructions page and write your first guardrail, for the promise you would least want a customer to read. Give it a note that says what Konrado should do instead. The Guardrails section of the docs says what the editor asks for and lists four rules a hosting company keeps. Then list refunds and cancellations under Always hand to a person. Once auto replies run, filter the Auto-reply history to Guardrail broken each week and open every row.

Ready to Transform Your Support?

Save time, reduce costs, and free up your team with Konrado.AI