Five Jobs You Should Not Give an AI Employee
Knowing where AI doesn't belong is what makes the rest of it trustworthy. Here are five jobs to keep firmly in human hands, and the reason each one fails in a way you won't notice until it's expensive.
Most articles about AI are about what it can do. This one is about the opposite, because an AI employee is easier to trust once you have drawn a clear line around it.
An AI employee is very good at jobs with a settled shape and a known right answer. It gets into trouble on jobs where the right answer depends on judgment, relationship, or consequence. The trouble is that it doesn't look like trouble. It looks like a confident, well-written response that happens to be wrong.
Here are the five jobs to keep out of scope, and how each one goes wrong when it doesn't stay out.
1. Anything that commits your money
Approving an invoice. Issuing a refund above a trivial amount. Agreeing a discount to save a deal. Signing off a purchase order.
An AI employee can prepare all of these. It can pull the numbers, match the PO to the delivery note, draft the credit note and flag the discrepancy. What it shouldn't do is press the button at the end. The failure mode here is a slow leak. A refund policy that is slightly too generous, applied again and again, or a duplicate invoice paid because it looked legitimate, costs real money before anyone notices.
The rule: AI prepares, a human approves. Set a threshold. Say anything under $50 goes through and anything above lands in someone's queue. You keep the speed on the small stuff and never hand over the checkbook.
2. Anything with a legal or regulatory consequence
Tenancy notices. Employment decisions. Medical or clinical advice. Tax positions. Anything where being wrong means being wrong to a regulator, not just to a customer.
The problem isn't that AI is careless here. It's that these areas are full of rules that look general but aren't. The right answer varies by jurisdiction, by contract, by the specific circumstances of the person asking. A confidently phrased general answer is worse than no answer, because the recipient acts on it.
The rule: in regulated territory, the AI's job is to route, not to answer. "That's a question for Sarah, I've passed it to her and she'll come back to you today" is a perfectly good response, and it's the right one.
3. The conversation where someone is upset
A complaint that's escalated. A customer who's genuinely angry. Bad news about a delay that's going to hurt someone's plans. A cancellation someone is trying to talk you out of.
These conversations aren't really about information. They're about being heard by a person who can actually do something. An immaculate, empathetic-sounding automated reply in this moment reads as a brush-off, and it is one. People can tell, and the resentment sticks to your brand rather than to the technology.
The rule: train the escalation, not the reply. An AI employee that spots frustration early and hands over quickly, with the full history attached so the human doesn't ask the customer to repeat themselves, is worth far more than one that tries to smooth it over.
4. Anything that's actually a relationship
The call to your biggest client. The negotiation with the supplier you've used for fifteen years. The check-in with the customer who's gone quiet and might be leaving.
You could automate the scheduling of these. You should not automate the substance. A relationship survives on the accumulated evidence that a specific person is paying attention to you. Outsource that and you're not saving time, you're spending goodwill you built up over years, on a saving that's smaller than you think.
The rule: if losing this account would ruin your quarter, a human makes the contact. Let the AI make sure the human never forgets to.
5. Any job nobody can describe
This is the sneaky one. Sometimes a task fails the test not because it's risky, but because when you sit down to explain how it's done, nobody can. It lives entirely in one long-serving employee's head, and every case is a judgment call informed by twenty years of context.
You cannot automate what you cannot describe. An attempt produces something that handles the easy cases and mangles the rest without telling you. The cases it mangles are the ones that needed the twenty years.
The rule: if two people in your business would explain the job differently, it isn't ready. Sometimes the useful project is writing the job down, and automation comes a year later. That's a real result, not a consolation prize.
Why the boundary is the point
There's a temptation to read a list like this as a list of limitations. It isn't. It's the thing that makes the rest work.
An AI employee with a narrow, clearly stated remit, like answer these questions, log these jobs, chase these documents, escalate everything else, is something your team can trust and your customers don't resent. An AI employee with an unclear remit gets second-guessed by everyone, which means every output gets checked by a human anyway, which means you've added a step rather than removed one.
Write the "not this" list before the "yes this" list. It takes an afternoon, and it spares you the awkward conversation later about why a customer got a refund they shouldn't have.
If you want a straight read on which of your jobs sit safely inside the line and which don't, our free AI-readiness audit is built around exactly that question. Our services page covers what we take on and what we leave with your team.
At BuildPulse, we care as much about where your AI stops as where it starts.