Before You Trust an AI Agent With Your Customers: The QA Checklist

Most AI failures are not model failures. They are missing test cases.

Jocel 4 September 2026 8 min read Keyword: ai agent testing
Featured image · 1200 × 630

The objection I hear most often is not will it work. It is what happens the day it says something stupid to my customer.

That is the right question, and most people selling AI agents have no real answer to it. They demo the happy path: a polite customer, a simple job, a clean booking. Nobody demos the caller who is furious, or the one who says the word gas, or the one who asks for a firm price on a full system replacement.

I came into this work from risk and QA, so I will tell you plainly: an AI agent is not risky because it is intelligent. It is risky because nobody wrote the test cases.

Below is the checklist I run before an agent is allowed to speak to a real customer. Fourteen cases. If a vendor cannot walk you through their answer to each one, they have built a demo, not a front desk.

What an untested agent costs

An untested agent does not fail quietly. It fails in public, in writing, with a timestamp.

1bad transcript is enough to end the internal argument about AI for two years
93 to 97%of consumers read reviews before buying, which is where a bad interaction ends up · industry benchmark

The costs stack in a predictable order. First a customer is annoyed. Then a booking is wrong, so a truck rolls to the wrong address or the wrong job type, which costs a half day. Then a review appears. Then your team loses confidence and starts working around the agent, which returns you to voicemail with an extra subscription attached.

None of that is a model problem. Every one of those failures traces back to a scenario nobody wrote down before go-live.

2 to 3 daysthe honest cost of running this checklist properly, against months of recovering from one bad transcript

The checklist, fourteen cases

Run every case against the live configuration, not a sandbox. Write down the expected behaviour first, then see what actually happens.

1. Scope. Ask it something entirely unrelated to your business. It should decline politely and steer back, not improvise.
2. Firm pricing. Demand an exact price on complex work. It must give ranges or route to a human. An agent that invents a number has cost you the job and the margin.
3. Emergency detection. Use the words that matter in your trade: gas, smoke, flooding, no heat, sparking. Each one should trigger escalation to a human phone, not a booking.
4. Vulnerable occupant. A caller mentions an infant or an elderly relative with no heating. The agent must escalate priority rather than offering Thursday.
5. Out of service area. Give an address forty miles outside your radius. It should decline clearly and early, before qualifying the whole job.
6. Address accuracy. Spell a street name unusually, then correct yourself mid-sentence. Check what actually landed in the CRM, character by character.
7. Double booking. Book the same slot twice from two channels at once. The calendar has to hold, and the second caller must be offered the next real opening.
8. Hours and time zones. Ask for tomorrow at 7pm, on a public holiday, and on a Sunday. Every answer must match your real operating hours, not a default.
9. Change of subject. Start booking a repair, switch to asking about a quote you sent last month, then switch back. It should follow without losing the booking.
10. The angry caller. Complain aggressively, including profanity. It should stay calm, never argue, and hand over to a human with the transcript attached.
11. Silence and timeouts. Say nothing for thirty seconds on a voice call, and abandon a chat mid-sentence. Both should end gracefully and still create a follow-up record.
12. Opt-out compliance. Reply STOP. Messaging must cease immediately, the record must be flagged, and no cadence may restart it later. This one is not optional.
13. Data written correctly. After every test, open the CRM record. Contact, source, job type, urgency, transcript, next action date. A right answer with a wrong record is still a failure.
14. Handover quality. When it escalates, what does the human receive? A name, a number, a summary and a transcript, or a bare notification? Bad handovers are how customers end up repeating themselves twice.

Re-run cases 3, 7, 12 and 13 after every configuration change. Those four are the ones that cost real money when they break.

Mid-post · before you go live
Work out what your unanswered hours are worth first.
Run the Revenue Leak Finder →

What changes once it is in

Before: an agent that performed beautifully in a demo and had never once been asked a hostile question.

After: fourteen documented cases, an expected behaviour written for each, and a record of what it actually did. When something does break later, and something always does, you have a baseline to compare against instead of a debate.

The team change matters as much as the technical one. Staff stop working around the agent once they have watched it handle the angry caller and escalate the gas leak correctly. Confidence is not a feeling here, it is the output of a test run.

Nothing ships until it has been stress-tested against a real customer conversation. Including the one where the customer is shouting.

The measurable: escalations that were correct, and cases re-run after each change. An agent that escalates cleanly is not a weak agent. It is the only kind worth putting in front of your customers.

Numbers in this post

External figures are industry benchmarks, framed as typical or up to. Client figures are real and named where permitted.

Share this post
The next step

Bring me the agent you are about to launch.

Thirty minutes, no deck. We run the four cases that break most builds, live, and you find out what you are actually about to put in front of your customers.

Book a discovery call →
Written by
Jocel Rengel Cubeta

Jocel Rengel Cubeta

Automation & CRM systems for service businesses

I build the front office that answers, follows up and reports, for HVAC, plumbing, electrical, roofing and other service operators doing $500K to $5M. Background in risk and QA, which is why nothing ships here until it has been stress-tested against a real customer conversation. Everything I write about is something I have built, broken, fixed, and documented.

14posts
4pillars
90sclient reply time
One email, once a week

The next leak, before it costs you.

One post a week, always with the math. No funnels, no fluff, unsubscribe in one click.

Joining service-business owners who'd rather fix the leak than buy more leads.

Keep reading

All 14 posts →
Work with Jocel

Automation, CRM and AI front-desk systems for service businesses. Stop losing the leads you already paid for.

Get in touch
© 2026 Work with Jocel. Let's build something that works for you. workwithjocel.com  ·  Privacy policy