The mistake small teams make with a website assistant is not choosing the wrong tool. It is switching it on without deciding what it does and what people still do. A week later there is a pile of captured leads that everyone assumed someone else was handling, and a customer who was promised a call that never came.
Getting AI and staff roles right is mostly a question of boundaries. The assistant is excellent at the first reply, at asking the same qualifying questions every time and at being awake at 11pm. People are better at pricing exceptions, awkward complaints and knowing when a customer is worth bending a rule for.
How you draw that line depends heavily on headcount. A sole trader, a three-person office and a ten-person business have different pinch points, so here are three separate splits.
The one-person business
When you are the whole company, the assistant is less a colleague and more a filter between you and your phone. The goal is fewer interruptions without losing work.
What the assistant owns:
- First replies, all hours: prices, service area, lead times and what to do next.
- Fact-finding: job type, location, preferred dates and contact details, captured as a lead.
- Polite deferral: anything it cannot answer from your content gets recorded, and the visitor is told a person will follow up.
What you own: quoting, anything unusual, and the follow-up itself.
The trap for a solo operator is treating every lead notification as urgent. Pick two fixed slots, say 8am and 4pm, and clear leads then. The assistant has already told the visitor when to expect a reply, so a few hours is fine. If you want a structure for those sessions, the morning follow-up routine is a good template.
The three-person office
With three people, the problem shifts. There is usually cover during the day, but nobody is sure whose job the website is. Typical setup: an owner, someone doing the work, and someone part admin, part everything.
| Task | Assistant | Admin | Owner | Specialist |
|---|---|---|---|---|
| Answer routine questions | Yes | Backup | No | No |
| Capture leads and booking requests | Yes | Reviews daily | No | No |
| Take over live chats | No | When on duty | Occasionally | No |
| Follow up captured leads | No | Owns | High-value only | No |
| Handle complaints | Opens ticket | Owns | Escalation | Input |
| Review unanswered questions weekly | Records them | Owns | Approves answers | Supplies facts |
The important column is the admin one. One person owns follow-up and the weekly review. The owner steps in on large jobs and signs off new answers. The specialist, who does the actual work, gets asked for facts but is not expected to watch the inbox.
This is the size where live takeover earns its place. Mark the admin as on duty during office hours so they can step into a conversation when a visitor needs a person, and leave evenings to the assistant.
The ten-person business
At ten people you have enough staff that the risk is not neglect but duplication. Two people reply to the same lead, or a sales enquiry lands with the support person.
Routing fixes this. Here is a sequence that works for most teams this size:
- Decide the two or three enquiry types that matter most, for example new sales, existing customer support and supplier or job applications.
- Switch on lead capture for sales and support tickets for existing customers, so the two arrive in different places.
- Use a webhook to send new leads to your CRM or a team Slack channel, tagged by type.
- Assign each type a named owner and a named deputy for holidays.
- Set on-duty cover in shifts, so live takeover always has a human behind it during opening hours.
- Give one person, not a committee, the job of reviewing knowledge gaps each week.
One warning at this size: resist the urge to let every department tweak the assistant's answers. When five people can edit Q&A pairs, contradictions creep in within weeks. Suggestions can come from anyone, but one person approves and publishes them, the same way one person would own the wording on your website.
It also helps to agree what "on duty" means. It should mean watching the inbox and able to reply within a couple of minutes, not merely being at work. A colleague marked on duty while in a two-hour site visit is worse than nobody, because the visitor is told a person is coming.
There is more detail on the mechanics in routing leads to the right salesperson automatically, and the actions involved are listed on the features page.
Who owns the follow-up
This deserves its own heading because it is where almost every setup fails. The assistant can capture a request perfectly and still lose you the customer if nobody replies.
The rule is simple: every lead, ticket and booking request has exactly one owner, decided before it arrives, not after. "The team" is not an owner. Neither is "whoever sees it first".
A quick worked example to test your own setup. Say your assistant captures 12 leads over a weekend. Monday morning, how many have a name next to them by 9:30? If the answer is fewer than 12, your split has a gap. Replace 12 with your own weekend number and try it this Monday.
Handovers between assistant and person
The moment a person takes over is where customers notice if your team is organised. A clean handover looks like this:
Visitor: I've had two quotes already and yours is higher. Is there any room on that?
Assistant: That is something a member of the team would need to discuss with you. I can pass your details and the quote reference to them now, or someone on duty can join this chat.
Visitor: Join now if you can.
Sam (on duty): Hi, Sam here. I can see your quote. Let me look at what we can do on the materials side.
The assistant did not negotiate, did not invent a discount and did not pretend to be Sam. Deciding in advance which topics trigger that handover saves your staff from cleaning up afterwards. Deciding when a person takes over covers the triggers in more depth.
Your next step
Write your split on one page before you change any settings. List the enquiry types you get, then put a name next to each for first reply, follow-up and escalation. Where the first-reply name is "the assistant", check your content actually answers that question.
Then show the page to everyone involved. Ten minutes of agreement now is cheaper than a lost lead that three people each thought someone else had.