Agents versus assistants: the difference that matters to a business owner
An assistant waits for you to ask. An agent gets to work on its own. That one line settles most of the confusion we hear from owners about what AI can do for them.
An assistant answers questions when someone asks. An agent carries out a job on a schedule or a trigger, often across several tools, and reports back. We build both, and the line we draw is this: agents can research, draft, and file on their own, but anything that reaches a customer or spends money waits for a person.
The one sentence version
An assistant is reactive. A visitor opens a chat on your site and it answers. You paste a document and it summarizes. Nothing happens until someone starts it.
An agent is proactive. It has a job, a schedule or a trigger, and a set of tools it is allowed to use. It wakes up, does the work, and leaves the result somewhere a person will see it. Nobody typed anything.
Both run on the same kind of model underneath. The difference is in what we wire around the model: the permission to act, the tools, the clock, and the reporting.
The agents we actually build
These are the four that come up most, in the order a client usually asks for them.
- The research agent. Given a company name or a list, it reads the public web, pulls what matters (who runs the company, what they do, recent news, whether they fit the client's ideal customer), and writes a short profile into the CRM. It runs when a new lead appears or when the owner drops a list in. It never contacts anyone.
- The outreach agent. It takes the research profile and drafts a first email and a follow up in the client's voice. Here is the line: it drafts. The owner or a salesperson approves before anything sends. Once approved, it watches for replies and drafts the next step.
- The applicant screening agent. When someone applies for a job, it calls them, asks the same set of questions every time, writes up the answers, and recommends hire or pass with its reasons. It logs all of it to the hiring pipeline. A person makes the decision.
- The morning brief. It reads overnight leads, bookings, site conversations, support tickets, and site health, and writes one short message to the owner before the workday starts. It runs alone, because reading and summarizing cannot hurt anyone.
What runs alone and what waits
The rule we use is simple enough to put on a sticky note. An agent may act on its own when the action is reversible, internal, and cheap. It must wait for a person when the action reaches a customer, spends money, or cannot be undone.
In practice that sorts like this:
- Reading, researching, summarizing, and filing: runs alone.
- Drafting emails, posts, and recommendations: runs alone, but the draft sits in a queue.
- Sending to a customer, posting publicly, booking on someone's calendar, moving money: waits for a tap from a human.
- Making a hiring or firing decision: never. It recommends.
We have had owners ask us to loosen this, usually after a few weeks of approving drafts that were all fine. Sometimes we do, one action at a time, with a log. Sometimes we talk them out of it. One bad email to a good client costs more than a hundred approvals.
Why owners feel the difference
An assistant saves time in the moment. Someone asks, it answers, the person moves on. The savings are real but they are spread thin across the day.
An agent removes a whole category of work. The owner of a custom home builder in Delray Beach no longer researches prospects, because that is done before they sit down. The office no longer phone screens every applicant, because the ones worth a human's time arrive already sorted. The difference is not that the work got faster. It is that it got off the owner's list.
What makes an agent trustworthy
Three things, and we build all of them in before an agent goes live. First, it works from a written job description that says what it may and may not do. Second, every action it takes is logged, so an owner can see what it did and why. Third, it has a way to say "I am not sure" and hand the item to a person instead of guessing.
An agent without those three is a liability with a schedule. An agent with them is closer to a reliable employee who happens to work at night.
Assistants and agents are two halves of the same system we put in front of our clients: the assistant on the website talks to customers, and the agents behind it do the research, the drafting, the screening, and the morning reading. One answers. The others get the work done.
Questions people ask
Is an agent just a more advanced chatbot?
Not really. A chatbot or assistant responds when asked. An agent has a job, a schedule or trigger, and tools it is allowed to use, so it does work without being prompted and reports back. The model underneath can be the same; the wiring around it is different.
Can an agent send emails or make decisions on its own?
In the systems we build, no. Agents research, draft, summarize, and file on their own. Anything that reaches a customer, spends money, or cannot be undone waits for a person to approve it. Hiring decisions are always made by a human.
How does an owner know what an agent did?
Every action is logged with the reason, and the agent works from a written job description that says what it may and may not do. If it is unsure, it hands the item to a person rather than guessing.
Want this done for your business?
Two minute intake. A real person reads every one and replies within a business day.
Keep reading
What an AI assistant on a website actually does all day
What a website AI assistant does all day for a Florida service business: page matched openers, tap qualifying, price callbacks, CRM leads and a morning recap.
AI at workHow we pick an AI model for a client project
How a Delray Beach studio picks an AI model for a client project: the job, speed versus depth, cost, privacy, and why one product often uses several models.
AI at workOpenAI, Anthropic, Google and the rest: what each is for when you are building
A builder's map of OpenAI, Anthropic, Google, Meta, xAI, DeepSeek and Mistral: what each is known for, hosted versus open models, and how we choose per job.