A practical starting point
A website assistant needs an accurate source of information and a clear route to a real person. Its first job is to help the visitor explain their request.
Build a small approved answer library covering opening hours, enquiry steps and confirmed product details. Date the answers and assign an owner. Leave stock, unusual pricing and delivery promises for confirmation.
A contact form can be a better first step than a chatbot when traffic is low. Compare completed enquiries, reply time and unresolved requests before deciding which interface helps customers.
The practical guide below works through a hypothetical example, the decisions to check and a way to review the result. Use it to prepare questions for your own situation; adapt the exercise to the information and tools you are authorised to use.
A busy chat window can generate many messages and very few useful enquiries. Track completed requests, missing information and cases requiring a second contact. Compare that with a short contact form. Website Enquiry Automation should reduce the work between a question and a useful response. Pair it with Customer Follow-up Planning so completed enquiries have an owner and a clear next action.
Read the practical guide
Website Enquiry Automation: a practical planning guide →Related topics
Start with a better brief.
Use the free planning tool, then tell us what you want to achieve.