Most "AI agents" we see on small business sites are just chatbots with better English. They answer questions, then hand off to a human. That's not an agent — that's a glorified FAQ.
A real agent closes the loop. It books the meeting, sends the confirmation, updates the CRM, and only escalates when something is actually unusual.
If your bot still requires a human reply, it's a chat. If it doesn't, it's an agent.
The four pieces you actually need
For a dental clinic, a travel agent, a loan officer — the stack is the same:
- A channel. WhatsApp is where people already are. Web chat is fine but lower intent.
- A calendar. Google Calendar or Calendly works. The agent reads availability and writes events.
- A CRM or sheet. Even a Google Sheet works for the first 100 leads. The agent writes the name, phone, request, and source.
- A model wrapped in a workflow. We use n8n or Make to orchestrate. The model handles understanding; the workflow handles the actions.
The handoff rule
Most agents fail because they try to do everything. Ours have one rule: if the user asks for something the agent can't do in three steps, escalate to a human.
For a dentist, that means: agent books cleanings, reschedules, sends location, and shares insurance providers. Anything else — pain, emergency, billing dispute — hands off with full context to Kiro or the office manager.
What "good" looks like in numbers
On a recent travel client, the WhatsApp agent handles roughly 62% of inbound requests end to end. Reply time is under three minutes, day or night. Bookings happen at 11pm, 4am, Sunday afternoons — windows a human team would miss.
The 38% that escalate are the high-value ones: custom itineraries, group bookings, complaints. Those are exactly where you want a human anyway.
How to start small
Don't try to ship a full agent in week one. Start with this:
- Week 1. Agent reads inbound, classifies the intent, suggests a reply for the human to send.
- Week 2. Agent auto-replies on the three highest-frequency intents (hours, location, pricing).
- Week 3. Agent books the calendar slot directly, no human in the loop.
- Week 4. Agent updates the CRM, sends the confirmation, and pings the team only on escalations.
By week four you have a real agent. By month two you've saved the team a few hours a day. By month three the math is obvious.
Want one of these for your business? Tell us about your use case and we'll quote a 4-week build.