By The short answer: choose around the enquiry you are missing. A telephone receptionist helps with incoming calls. A website chatbot helps people already on your site. A voice button on a website lets visitors speak in that browser; it does not, by itself, answer your business phone. Start with the contact channel that needs help, then decide what the assistant should be allowed to do.
For a small service business, those distinctions matter more than how natural a demo sounds. Someone calling while your team is on a job needs a different route from someone comparing your services online at ten in the evening.
Three tools, three different starting points
An AI telephone receptionist
This is a system connected to a telephone workflow. Depending on the product and configuration, it may answer calls, collect a message, provide approved information or route the caller elsewhere.
Do not assume every product can transfer a call to your existing number, handle your busiest period or book into your calendar. Those are separate capabilities to verify with your phone provider, the software and a real test.
A website chatbot
This helps a visitor through a text conversation on your website. A useful scope might be answering service questions, checking which information is needed for an enquiry and helping the visitor reach your team.
It cannot help someone who never visits the site. It also needs an answer for the point where the conversation stops being routine: a complaint, an unusual request or a question that needs a person’s judgment.
A website voice assistant
This gives a website visitor a way to speak rather than type. It can be part of the same enquiry journey as the chatbot, but it is not the same as a telephone answering service.
On Lumin’s website, for example, Lumi offers text and optional browser voice. Voice begins after the visitor selects the start action and grants microphone permission, subject to browser support and usage limits. That demonstration shows website voice, not a connection to a business telephone line. See how Lumi works.
Find the gap before choosing the tool
Look at a representative week of enquiries. Where did people first contact you? Which requests waited? Which questions came up repeatedly? What did the team need before it could respond?
- Calls go unanswered: assess your current phone handling, staffing and an answering service or telephone assistant.
- Website visitors need basic answers: improve the service information first, then consider a chatbot for questions and enquiry capture.
- Visitors prefer speaking: consider optional website voice alongside a usable text route.
- Enquiries arrive but nobody follows up: fix ownership and routing. Adding another assistant will not, on its own, resolve that gap.
You may need more than one improvement. You do not need to introduce them all at once.
Answering is not the same as booking
A conversation can sound complete before anything has happened in the business system.
There is a difference between sharing a booking link, collecting a preferred time and creating a confirmed appointment. The last step needs the right connection, permission and checks. Your team should be able to verify the appointment in the calendar, not rely only on the assistant saying it is booked.
The same applies to quotes and promises. Decide whether the assistant can explain your pricing approach, collect details for a quote or make a commitment. Keep those boundaries explicit. A request for a callback should not become a promise that someone will call within ten minutes unless your team can support it.
Make the human handoff part of the purchase
Ask a prospective supplier to demonstrate a request the assistant cannot finish. Watch what happens next.
- Can the customer reach a person or leave a clear request?
- Does the right team member receive the relevant details?
- Can staff see what the customer was told?
- What happens outside working hours?
- What happens if the calendar, notification or telephone connection fails?
A notification is not a reply. Assign someone to own the next step and explain to the customer what to expect. Avoid passing an urgent request into an inbox that nobody is watching.
A hypothetical Edmonton example
Imagine a small home-service company whose crew cannot always answer the phone while working. Its website already explains its services clearly, but callers leave incomplete voicemails.
A website chatbot alone would not solve that telephone problem. The first assessment should look at the missed calls, the details needed for a callback and the route to a person. A telephone answering option may fit, provided its actual handling and escalation work for that business.
Now imagine a different company whose phone is covered, but website visitors regularly ask whether it serves their neighbourhood and what to prepare for an estimate. Clearer website information, supported by a focused chatbot, may be the smaller useful step.
Neither example proves a return on investment. Measure whether the chosen setup produces usable enquiries and reduces work for the team.
What to check before you commit
- Channel: does the proposal cover telephone calls, website chat, browser voice or a specific combination?
- Information: who supplies and maintains the approved answers?
- Actions: what can it do, and what stays with a staff member?
- Connections: are your exact phone, calendar and CRM products supported on your current plans?
- Data: what is recorded or saved, who can access it, where it is processed and how long it is kept?
- Customer choice: how will people know they are using AI, and what alternative route is available?
- Costs: what is included, what is metered and what happens when an allowance runs out?
- Testing: will the demonstration include missing details, requests for a person and unavailable systems?
Only collect information the task needs. Before recording calls or handling sensitive customer details, have the proposed data flow and notices reviewed for your circumstances. A vendor’s general assurance is not a substitute for understanding your setup.
Where Lumin fits
Lumin builds website chat and voice assistants around approved business information, enquiry capture and a clear human next step. Connections to calendars, CRMs and other tools are scoped after checking the products, permissions and workflow.
Our public Lumi demonstration is a website assistant, not a production telephone receptionist. If missed phone calls are your main problem, say that at the start so the assessment addresses the right channel rather than treating a website assistant as the answer.
Bring one example of an enquiry that currently gets stuck, with private details removed. We can discuss where an assistant may help, what your team should retain and what needs testing before you rely on it.