AI Chatbot for Customer Support
This page is how WebsiteChat is used for customer support. A visitor is already on the site with a support question. WebsiteChat answers from the pages you published, continues if they ask again, and stops when the support team should take the case.
A typical support turn looks like this:
- “What are your opening hours?”
- “Do you cover my area?”
- “What is included in this service?”
- “What do I need before I book?”
- “What is your return rule?”
Where WebsiteChat sits in the support workflow
- The visitor asks a support question in the widget.
- WebsiteChat retrieves the published page or approved document that covers it.
- It answers from that material, on the page the visitor already has open.
- They can ask a follow-up. The next reply still has to come from retrieved content.
- If the case needs a person, WebsiteChat stops and points to the contact path the site already uses.
- The support team receives the harder case. Routine confirmation stays in the chat.
Documented FAQ items are one source among others. How WebsiteChat uses an FAQ page is covered under website FAQs.
What the support team still owns
| WebsiteChat in the chat | Support team |
|---|---|
| Hours, area, fees, and steps that are already published | Exceptions that were never written down |
| A second question about the same policy | Complaints, negotiation, and tone-sensitive threads |
| A clear stop when the source does not cover the case | Commitments, refunds, and professional judgment |
What WebsiteChat can and cannot handle
It can answer while staff are offline, but only for the documented question, and only while the service is running. It does not close an exception or make a promise at night. A visitor asking in another language is the multilingual use of the same support job.
Product setup — which pages are crawled, how a handoff is worded — is on the WebsiteChat overview and in the guides.
A short support example
A visitor asks whether a return is still allowed. WebsiteChat retrieves the returns page and states the published window. They ask what to include in the message. WebsiteChat uses the same page for the steps. They then say the item arrived damaged and they want an exception. That turn stops, and the contact path is the handoff. The support team gets the exception, not another copy of the policy.
When the visitor is asking in order to be contacted, rather than to resolve a documented question, that handoff is lead generation. A dental clinic site uses the same support pattern for published hours, insurance notes, and first-visit rules; see WebsiteChat for dental clinics.
This page is how WebsiteChat is used for support. If you are still deciding whether repetitive inquiries should be automated at all, start from the problem: Learn how to automate repetitive website inquiries.