Key takeaways
- A chat assistant talks. An agent works through steps inside your software.
- Agents need clear instructions, limited access, and someone checking the output.
- They fail in predictable ways: vague goals, messy data, and edge cases nobody wrote down.
- My own business line is answered by a voice agent, so you can hear one working.
- The technology is cheap. The management is the part most businesses skip.
On this page
One talks, one does
When you type a question into ChatGPT, Claude or Gemini, you're using a chat assistant. It writes a response and stops. If you want something done with that response, you copy it, paste it somewhere, and do the next step yourself. You are the hands.
An AI agent is the same kind of model with hands attached. It gets a goal ("handle new quote requests"), access to specific tools (your inbox, CRM and calendar), and permission to take a series of steps. It decides what to do next based on what it finds, does it, and moves on.
Here's the difference on one ordinary task, a new quote request landing in your inbox:
| Step | Chat assistant | AI agent |
|---|---|---|
| Notice the email | You | Agent |
| Pull out name, address and job details | You paste it in, it summarizes | Agent |
| Check whether the customer is already in the CRM | You | Agent |
| Create or update the CRM record | You | Agent |
| Draft a reply with next steps | It drafts, you copy it over | Agent drafts it in your email |
| Decide whether to send | You | You |
Notice the last row. A well-built agent still leaves the decisions that matter with a person. The point isn't to remove you. It's to remove the five small steps between you and that decision.
An everyday analogy
Think about the difference between calling a knowledgeable friend and hiring an assistant.
The friend (ChatGPT) gives smart advice on the phone, maybe even drafts a letter for you. But they don't have keys to your office. When you hang up, the work is still yours.
The assistant (an agent) has a desk, a login and a job description. You say "every morning, log new leads in the CRM and draft replies for me to approve," and they do it without you walking them through each email. When they're new, you check their work closely. Over time you check less, but never stop completely.
Agents are fast, never get bored, and work at 2 a.m. They also have no common sense about your particular business until someone writes it down. Picture a new hire who is brilliant, tireless and very literal.
A live example: if you call my business line at (314) 970-4001, a voice agent answers. It asks about your business, figures out whether a call with me makes sense, books a time on my calendar, and emails me a summary. That's three tools (phone, calendar, email) and a judgment call in one conversation. A chat window can't do that. It can only describe how someone might.

Get the checklist
What an agent needs to do useful work
Like a new employee, an agent needs a few things before its work is reliable.
1. Clear instructions. Not "handle email." More like: "For any email asking for a quote, pull the name, phone, address and job type. If the address is outside our service area, draft a polite decline. Otherwise create a lead in the CRM and draft a reply offering the next two open estimate slots." Most bad agent output traces back to vague instructions.
2. The right access, and no more. An agent that drafts replies needs to read your inbox and write drafts. It does not need to delete email, issue refunds or touch your bank account. Give it the narrowest access that gets the job done, ideally through its own login so you can see what it did and shut it off in one click. My security page covers how I handle this.
3. Examples of good work. Show it three replies you liked and a properly filled-out CRM record. Agents copy patterns well.
4. A checking step. Someone reviews the output before it reaches a customer, at least at first. For low-risk work like tagging emails, spot checks may be enough. For anything customer-facing or money-related, a person approves every piece.
5. Permission to say "I don't know." Good agents are told what to do when they're unsure: stop, flag it, and ask. Without that instruction they tend to guess, and a confident guess is the most dangerous kind of mistake.
Where agents fail
I build with these tools every day, and they fail in predictable ways. Knowing the patterns is most of the battle.
- Vague goals. "Keep the CRM clean" means something specific to you and nothing to a model. Without a definition, the agent invents one.
- Messy data. If your customer list has three versions of the same person, the agent will pick one, maybe the wrong one.
- Edge cases nobody wrote down. The customer who's also your brother-in-law. The job you always quote higher because of the steep driveway. People carry this in their heads; agents only know what they've been told.
- Made-up details. AI models sometimes state things that aren't true with total confidence. In an agent, that can mean a reply promising a discount you never offered. More on this in what happens when AI makes a mistake.
- Drift. Your software changes a screen, or your prices and policies change, and nobody updates the agent's setup. Work that was right six months ago slowly goes wrong.
None of these are reasons to avoid agents. They're reasons to run them like any staff: with instructions, supervision and feedback.
Why someone has to manage them
This is the part most AI marketing skips. The models are cheap and getting cheaper. The hard part is everything around them: writing instructions, setting up access, checking output, fixing what breaks, and updating the setup as your business changes.
Someone has to own that. In a business with five or fifteen people, it usually lands on the owner, squeezed between everything else. That's how a lot of AI projects stall after the first exciting week.
That gap is where I work. I run a team of AI agents on my own tools, work through a client's list of repetitive computer tasks, and check every piece before it goes back to them. It's what I mean by a fractional AI manager: you don't need a full-time AI hire, you need someone to manage the bots. Whether you hire that out or keep it in-house, the job itself doesn't go away.
What this looks like in a real small business
Example: picture a four-person residential cleaning company. The owner spends about an hour every morning separating real quote requests from spam, checking which neighborhood each one is in, entering contacts into the CRM, and writing back with pricing.
With a chat assistant, she can paste each request into ChatGPT and get a nice draft reply. That saves some typing, but she still does every step around it.
With an agent, each new request kicks off the work. The agent pulls out the name, address, home size and preferred day, checks the address against her service area, and creates a CRM record if the person is new. Then it drafts a reply using her pricing sheet and usual tone, and drops it in her drafts folder with a note: "New lead, 3 bed/2 bath, in area, prefers Tuesday."
Her morning hour turns into a short pass through the drafts. When something unusual comes in (a commercial job, an angry message, a request in Spanish), the agent flags it instead of guessing. She still makes every decision that matters. She just stopped doing the clerical part.
The honest part
Agents are not employees, and they're not magic. They don't understand your business the way a three-year employee does, they can be confidently wrong, and they need someone watching.
They're also not worth it for everything. If a task happens twice a month and takes five minutes, setting up an agent costs more time than it saves. If a task depends on reading a customer's mood across a counter, or on a license and professional judgment, keep it with a person.
Be skeptical of anyone selling a fully autonomous agent that "runs your business while you sleep." Agents do their best work on narrow, well-defined jobs with a person checking the output. The more open-ended the job, the more supervision it needs. Start narrow, check everything, and widen the job only after the agent earns it.
Quick questions
Is ChatGPT an AI agent?
Mostly no, though the line is blurring. The standard chat window writes text and waits for you. Some newer features let it browse the web or act in connected apps, which is agent behavior. The practical test: does it take several steps in your actual tools without you doing each one? If yes, it's acting as an agent.
Do I need to know how to code to use AI agents?
No, but someone involved needs to think clearly about process. Many agent and automation tools need little or no code. The harder skills are writing precise instructions, deciding what access to grant, and building in a review step. That's closer to managing staff than to programming.
Is it safe to connect an AI agent to my email and CRM?
It can be, if access is limited and logged. Give the agent its own account where possible, grant only the permissions it needs, keep a human approval step on anything customer-facing, and make sure you can revoke access instantly. Be wary of any tool that wants full admin access to everything on day one.

