A chatbot answers. An agent does the thing — then shows you what it did, and lets you reverse it. That gap is why most “AI features” shipped in 2024–25 felt like toys, and why the products winning in 2026 feel like staff.
Chat is a surface. Agency is a system.
If your model can only talk, you built a search box with worse latency. An agent needs three extra layers:
- Tools — calendar, CRM, payments, CMS, ticketing. Named, scoped, logged.
- Policy — what it may do alone vs what needs a human confirm.
- Memory — the last decision, the customer's constraints, the open ticket. Not the entire chat dump.
"If the user still has to copy-paste the answer into another tab, you didn't ship AI. You shipped homework." — kickoff note we use on AI scopes
The trust contract users now expect
- Preview before commit. Show the email, the refund, the calendar invite — then a single confirm.
- Obvious undo. Especially for money, access, and messages that left the building.
- Citations when it claims facts. “According to your order #4812” beats “I think.”
- A kill switch. One tap to pause the agent without hunting Settings.
People will forgive a slow answer. They will not forgive a confident agent that charged the wrong card. Design the failure, not just the demo.
Where we actually put agents in client products
Not on the homepage. On the high-frequency, high-friction jobs:
- Rescheduling, refunds, and “where is my order” — with CRM + payments tools.
- Internal ops: drafting PRs against a ticket, tagging invoices, filling compliance forms.
- Onboarding: collecting the brief, generating a first draft site/app map, not hallucinating a quote.
A shipping checklist we use
- Write the job in one sentence: “When X, the agent does Y, then Z.”
- List every tool. If a tool can move money or delete data, it needs confirm + audit log.
- Eval set: 30 real user utterances, including the nasty ones. Run it every deploy.
- Show the plan in the UI before the first tool call on destructive paths.
- Log traces. If you can't replay a bad run, you can't fix it.
What not to build
A floating bubble that “answers anything about the company” with no tools, no evals, and no owner. That's a support ticket generator with extra steps. Start narrower. Make one job faster. Then widen.