After-hours enquiries
A website assistant answers questions about services, opening hours, and pricing from approved content, and books a call when the visitor is ready.
Chat, email, and voice assistants that answer routine questions from approved information, collect details, and hand over to a person when they should.
How it works · From customer question to confirmed booking
STEP BY STEP
In
Understand01
Question and intent identified
Intent: booking
Retrieve02
Answer found in approved content
Source: hours page
Reply03
Answer sent, clearly labelled as AI
Reply with source
Collect04
Name and contact details captured
Details complete
Hand over05
Booking passed to reception
Person confirms
Human checkpoint
Out
See how this would run on your own process, with your tools.
Book a free callThe problem
01
Customers ask the same questions, often outside office hours, and each one needs a reply. Staff spend hours on routine answers while urgent or complex requests wait in the same queue.
Use cases
02
Typical examples. Every build is scoped to your own process and systems.
A website assistant answers questions about services, opening hours, and pricing from approved content, and books a call when the visitor is ready.
Incoming support email is categorised, urgent messages are flagged, and a draft reply is prepared from the knowledge base for a person to approve.
Calls are answered, the caller's need and details are captured, and a summary is sent to the right person, with a transfer for anything urgent.
Scope
03
We agree what the assistant may and may not say, build it on your approved information, and test it against real questions before launch. Every assistant has a clear hand-off path and is monitored after go-live.
Assistants answer from approved information only and should say when they do not know. They tell people they are talking to an AI, and they do not give medical, legal, or financial advice or make commitments on your behalf.
Delivery
04
Discover
Days
Map
1–2 weeks
Design
Days
Build and test
2–6 weeks
Improve
Ongoing
Workflows
05
Each one has its own page with a diagram of how it runs.
Customer support
Routine questions answered instantly from approved content, with handover to a person.
See the workflowCustomer support
Tickets are classified, prioritised, and drafted before an agent opens them.
See the workflowCustomer support
Every call is answered, details captured, and bookings requested for confirmation.
See the workflowCustomer support
Each new customer gets the right welcome, setup tasks, and check-ins on time.
See the workflowCustomer support
Surveys go out on time and unhappy customers are flagged to an owner the same day.
See the workflowCustomer support
Pre-arrival messages, instant answers, and requests routed to the right team.
See the workflowCustomer support
Onboarding messages triggered by what each user has and has not done.
See the workflowQuestions
06
Yes. We design assistants to identify themselves clearly and offer a route to a person.
Conversations are logged and reviewed. Wrong or missing answers are fixed in the source content, and topics that should not be automated are routed to a person.
Yes, through the WhatsApp Business Platform. Your number needs Meta's approval, and messages you start must use approved templates.
The major languages the underlying AI models support. We test the assistant in each language you need before launch.
Next step
Tell us what is taking too much time, what is difficult to manage, or what you would like your systems to do differently. You do not need a technical specification to start.