How WebsiteChat Handles Website FAQs

This page is how WebsiteChat handles website FAQs. The visitor asks in the widget. WebsiteChat retrieves the FAQ section, or a related published page, and answers. The FAQ page stays on the site as the source.

What WebsiteChat does with an FAQ question

  1. The visitor asks, often in wording that is not an FAQ heading. Example: “I opened the package yesterday. Can I still return it?”
  2. WebsiteChat retrieves the returns FAQ, or the policy page if that is where the rule lives.
  3. It answers from that passage. It does not extend the window because the question was polite.
  4. A follow-up (“what do I include?”) can use the same page or a second crawled page.
  5. If no passage covers it, the reply says so and offers the contact path. That case belongs with customer support, not with a stretched FAQ item.

Sources in the same crawl can include product, service, pricing, policy, help, and documentation pages. Setup of that crawl is on the WebsiteChat overview.

What this use does not decide

Whether a short FAQ page is enough on its own, without a chat, is a publishing decision. This page assumes you are using WebsiteChat and describes the FAQ job inside it. A conversation that should become a request a person receives is lead generation, not another FAQ answer. A law firm site uses that same published-FAQ job for intake questions already on the site; see WebsiteChat for law firms.

This page is how WebsiteChat handles FAQ questions. If you are deciding whether a normal FAQ page is enough, that is a different question: How to automate FAQ answers on a website.

Frequently asked questions

Can WebsiteChat answer from the FAQ page?
Yes, when that page is in the crawl. It retrieves the matching section and answers in the chat. The FAQ page itself stays on the site.
Can it use more than the FAQ?
Yes. Service pages, pricing, policies, help docs, and company pages in the same crawl can be part of the same answer. A follow-up can pull a second page.
What if the visitor does not use the FAQ heading?
They can ask in their own words. WebsiteChat still needs a passage that covers the question. Different wording is not a license to invent the policy.
Can it collect a lead from an FAQ conversation?
Only if you have configured a conversion goal and the turn matches it. A plain FAQ answer can end without asking for contact. See lead generation for that handoff.
What does the support team see when the FAQ does not cover it?
WebsiteChat should say the source does not cover the question and point to the contact path you already publish. The person then handles the gap. The chat does not stretch a nearby FAQ item into a new promise.

Add this chat to your website

Start a 14-day trial, or compare plans if you already know what you need.