An AI agent can reliably handle the routine part of support and sales: common questions, first replies to new enquiries and passing qualified leads to your CRM. It should not be left alone with unclear, sensitive or high-stakes conversations. Those belong to a person.
The useful question is not whether an agent can replace your team. It is which tasks are worth handing over, and what the agent must never do.
What agents can handle
Agents do best with work that repeats and has a known answer.
- Common questions. Opening times, how an order works, what a service includes, where to find a form. You agree the answers with the agent’s builder.
- First replies. A quick response to a new enquiry, with a few useful questions asked in return.
- Qualifying leads. Collecting the details your salesperson needs, then passing the lead to your CRM.
- Routine internal tasks. Status updates, reminders and data entry that currently eat someone’s day.
The benefit is mostly speed and consistency. Customers do not wait, and your team stops answering the same question again.
What agents cannot handle well
Be honest about the limits.
- Questions outside what the agent was given. It may guess, and a confident wrong answer is worse than “let me find someone.”
- Complaints, refunds and anything where the customer is upset.
- Price negotiation and any promise your business has not authorised.
- Legal, medical or financial advice.
- Situations that need judgement about a long-standing customer.
If a topic could cost you money or trust, keep a person in the loop.
Human handoff is not optional
Every agent should hand over to your team whenever a conversation needs a person. Decide the triggers in advance:
- The customer asks for a person.
- The agent does not know the answer.
- The customer sounds frustrated.
- The topic is on your never-automate list.
Handoff must be smooth. The person who picks up should see the whole conversation, so the customer does not repeat themselves. Also make sure someone is there to pick up, including when the office is closed, or say clearly when you will reply.
Guardrails
Guardrails are rules about what the agent may say and do. Write them down.
- A list of topics it answers, and a list it never touches.
- Tone and wording that match your business.
- A rule never to state prices, terms or policies it has not been given.
- Limits on what it can change in your systems.
- A clear statement to customers that they are talking to an automated agent.
Keep the knowledge it uses small, correct and up to date. An agent is only as reliable as the material behind it. If your policy changes, the agent must change the same day.
Test with real conversations
Before any customer sees it, your team should try real conversations. Use real past enquiries. Try the awkward ones: vague questions, mixed languages, angry messages, attempts to push the agent outside its rules.
After launch, read conversations on a regular basis. Look for questions it failed, handoffs that came too late and answers that drifted from your policy. Improve it step by step. An agent that nobody reviews slowly gets worse.
Choosing where it lives
Agents can answer on your website or on WhatsApp. If you already use WhatsApp automation for confirmations and reminders, an agent can sit alongside it. Agents work with your CRM, WhatsApp and Odoo, so details are not copied by hand. You do not need Odoo to use one.
A sensible way to start
- Pick a few tasks that cost your team the most time.
- Agree what the agent must never do.
- Build it, then test it with your own staff.
- Launch in a limited way, review often and widen slowly.
Agree who owns the agent and its content at the start, in writing.
Where Teapot Techies fits
We build AI agents for support, sales and routine operations and run them for you. We start by picking the tasks worth handing over and what the agent must never do, agree when a person takes over, test with your team, then host the agent and review its conversations. Each project is scoped and quoted. See agentic AI for more.