Website chat
A chat on your own website. It replies to a question a visitor types, from the approved answers, and says that it is an automated assistant.
This page sets out what a website and messaging assistant does with an enquiry that a visitor or customer has sent you. It lists the channels and permissions and says where the assistant stops. It has no write permission on your booking system.
A website and messaging enquiry assistant is a bounded service that replies to enquiries a visitor or customer has sent you, using answers your team has approved. It replies to enquiries people send and does not start conversations of its own. When someone wants to book, it offers your existing booking link. It has no write permission on your booking system. Anything it cannot settle goes to a named person. Durward agrees the questions, the channels and the handover with you and tests each path before go-live.
A website and messaging enquiry assistant is a bounded service that replies to enquiries a visitor or customer has sent you, using answers your team has approved. It replies to enquiries people send and does not start conversations of its own. When someone wants to book, it offers your existing booking link. It has no write permission on your booking system. Anything it cannot settle goes to a named person. Durward agrees the questions, the channels and the handover with you and tests each path before go-live.
The three channels share one set of permissions. Each is scoped and set up with you separately.
A chat on your own website. It replies to a question a visitor types, from the approved answers, and says that it is an automated assistant.
Replies to a message a customer sends you on WhatsApp, with the same permissions as website chat. How it is set up, what Meta requires and when the free app is enough are covered on the WhatsApp chatbot page.
Replies to a text a customer sends to your number, with the same permissions. The scope is agreed with you first. A wider front-desk build covers phone and further channels and is scoped separately.
The assistant answers only from information your team has written or approved. A question outside that set goes to a person and is not guessed at. The set is written down so your team can read it, and it changes only when your team approves a change.
When someone wants to book, the assistant offers your existing booking link and the booking is made on your platform. This assistant has no write permission on your booking system. Some other products write bookings, but only where a platform's API supports it and the scope has been verified. That boundary belongs to those products and does not carry over to this one.
Nothing goes live until your team has approved the questions, the knowledge, the booking-link rule and the handover, and each path has been tested.
Your team lists the routine questions the assistant may answer and picks the channels from website chat, WhatsApp and SMS. Each channel is scoped with you and nothing is assumed.
Buyer receives: A list of approved questions and a written channel scope.
Your team writes or approves each answer and the wording the assistant uses to say it is automated. We agree who may change the set and how a change is approved.
Buyer receives: An approved knowledge set and a named owner for changes.
We agree when the assistant offers your existing booking link and what it says. We confirm in writing that it has no write permission on your booking system.
Buyer receives: A written booking-link rule that records the missing write permission.
We agree which enquiries go to which named person, what the visitor is told and what note travels with the enquiry. How long enquiry records are kept is agreed for your workflow and is not set on this page.
Buyer receives: A handover map with a named person for each type of enquiry.
On each channel we test a routine question, a question outside the set, a sensitive question and a booking request, then the handover for each.
Buyer receives: A test log for each channel and path, kept with the scope.
The implementation fees are published on the pricing page and are not repeated here. We confirm in writing what is set up, which later changes are covered and what is quoted separately.
Buyer receives: A written scope and a named owner for each handover.
These patterns are for scoping and are not client results.
A visitor asks something your team has already answered in writing.
A visitor asks to make, move or cancel an appointment.
The question is outside the approved set, unclear, sensitive or clinical.
The visitor asks for a person, or the enquiry matches a handover rule.
The assistant answers inside rules your team has approved. Anything it cannot settle reaches a named person.
Check first whether your website, messaging account or booking platform already answers routine questions. A feature you already pay for is recommended where it does the job.
These pages cover the other ways of handling an enquiry, the current status of each data-handling item and a first conversation.
Supporting information: See this one working · Dental enquiry handling · Salon enquiry handling · Accountancy enquiry handling · Animal-service enquiry handling · Assessments: how the bounded first stage is chosen for your workflow · Pricing: how our work is priced and scoped · Security: the current status of each data-handling item
Tell us which questions reach you most, which channels you use and which booking platform you have. We will say plainly if something you already have covers it.
With your permission, Google Analytics uses cookies to help us understand how this site is used. We remember your choice for six months; you can change it at any time using Cookie settings in the footer. How Google uses data.
Your choice could not be saved. Please check your browser storage settings.