Skip to content

Answer routine website and messaging enquiries

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.

What the service covers, and what it does not

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.

What is included

  • A list of the routine questions the assistant may answer, written or approved by your team, such as hours, location, parking and your cancellation policy.
  • The channels you choose from website chat, WhatsApp and SMS, each scoped with you and written down.
  • A knowledge source for the approved answers, with a named owner and a rule for how a change is approved.
  • The wording the assistant uses to say it is automated, approved by your team before go-live.
  • A booking-link rule that says when the assistant offers your existing link and confirms that it has no write permission.
  • Handover rules that name who receives each type of enquiry and the note that travels with it.
  • A test of each path before go-live, including a question outside the approved set and a booking request.
  • A written scope that names what is set up, which later changes are covered and what is quoted separately.

What is not included

  • Starting conversations of its own. This assistant replies to enquiries people send. Outbound calls and messages are set up separately, only for people who have agreed to receive them, with the wording, the audience and how often agreed with you in writing first.
  • Write permission on your booking system. The assistant has none, and it cannot create, move or cancel a booking.
  • The booking writes that other products make. They need a verified scope and an API permission, and they belong to those products.
  • Clinical, medical or veterinary advice, or a judgement about an individual case.
  • Replacing a helpdesk, a support platform or your team. The assistant answers questions on the approved list and passes the rest to a person.
  • A connector to a CRM or any other system. This page describes none. If you need one, say so on the fit call and it is assessed there.
  • Any promise about how quickly an enquiry is answered or how quickly a person replies.
  • A promise that no enquiry is misunderstood. Approved answers, tests and handover reduce mistakes but cannot remove them.
  • A legal view on what visitors are told or how enquiries are kept. You approve the wording, and you should take qualified advice where the question matters.

Channels, knowledge and the booking link

The three channels share one set of permissions. Each is scoped and set up with you separately.

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.

WhatsApp

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.

SMS

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.

Knowledge source and updates

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.

The booking link and the write boundary

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.

How the assistant is set up and tested

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.

  1. Choose the questions and the channels

    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.

  2. Approve the knowledge

    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.

  3. Set the booking-link rule

    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.

  4. Set the handover

    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.

  5. Test each path

    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.

  6. Confirm 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.

Four enquiries, and what the assistant does with each

These patterns are for scoping and are not client results.

A routine question inside the approved set

A visitor asks something your team has already answered in writing.

Trigger
A message arrives on a channel your team has switched on.
Systems or sources
The channel and the approved knowledge set.
What the assistant does
Reply from the approved set, make clear that it is an automated assistant and point to the next step your team has chosen.
Human checkpoint
Your team owns the knowledge set and approves every change to it.
Exception route
A question the set does not cover goes to a named person with a note of what was asked.
Success measure
How many questions were answered from the set, how many were passed on and which questions were missing, reviewed by your team.

A visitor wants to book

A visitor asks to make, move or cancel an appointment.

Trigger
The visitor asks about booking.
Systems or sources
Your existing booking link and your booking platform, which the assistant cannot write to.
What the assistant does
Offer your existing booking link. The visitor completes the booking on your platform. The assistant does not create, move or cancel anything.
Human checkpoint
Your team owns the diary and every change to it.
Exception route
A request the link cannot settle goes to a named person, and the assistant assumes no booking has been made.
Success measure
How many visitors were offered the link and how many requests reached a person instead, reviewed by your team.

An uncertain or sensitive enquiry

The question is outside the approved set, unclear, sensitive or clinical.

Trigger
The assistant cannot match the question to an approved answer, or the question touches a topic your team has reserved for a person.
Systems or sources
The approved question list and the handover map.
What the assistant does
Say plainly that a person needs to answer, and pass the enquiry on with a note of what was asked. The assistant does not guess.
Human checkpoint
A named person decides how to answer, and whether to answer at all.
Exception route
Clinical, medical or veterinary questions and any individual case go to a named person. The assistant gives no advice on them.
Success measure
Which questions were passed on, how many were new to the set and whether the set needs a new answer or a new reserved topic.

A handover to a person

The visitor asks for a person, or the enquiry matches a handover rule.

Trigger
The visitor asks for a person, or the enquiry matches a rule your team has set.
Systems or sources
The handover map and the place where your team receives enquiries.
What the assistant does
Tell the visitor the enquiry is being passed to a person, and pass it on with the conversation so far, where your channel allows it, and a note of the reason.
Human checkpoint
The named person takes the enquiry and decides what happens next.
Exception route
The rule for an enquiry nobody takes is agreed at setup and tested. The assistant does not close it and does not promise a reply.
Success measure
How many enquiries were handed over, to whom and how each was resolved, reviewed by your team.

Human ownership, and who does what

The assistant answers inside rules your team has approved. Anything it cannot settle reaches a named person.

Durward prepares

  • The list of approved questions, the knowledge set and the wording that says the assistant is automated, for your approval.
  • A channel scope for website chat, WhatsApp and SMS, written down and agreed with you.
  • A booking-link rule that records that the assistant has no write permission.
  • A handover map that names who receives each type of enquiry and what they are told.

Your team keeps

  • Approval of the answers, the channels and the wording before anything goes live.
  • The diary, and every booking, change and cancellation in it.
  • Every question about advice, safety, treatment or an individual case, and every enquiry that is unclear or sensitive.
  • The decision on what visitors are told and how enquiries are kept, with qualified advice where it matters.

When this is the right size of tool

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.

This assistant adds value when

  • The same few questions reach you on your website or by message, and a person answers each one by hand.
  • Visitors need an answer first and a booking link second, and you want a written rule for what happens when the answer is not in the set.
  • You are content for the assistant to point to your booking link and for a person to own the diary.

Use what you already have when

  • Your booking platform or messaging account already answers routine questions in a way you are happy with, and someone owns the result.
  • You need the assistant to place bookings directly in your diary. This one cannot. Other products may, where the platform's API supports it and the scope is verified, and the fit call is the place to ask.
  • Nobody can be named to take handovers.
  • The aim is to message people who have not contacted you. This service does not do that.

Bring your most common questions and your booking link

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.