How WebsiteChat Captures Website Leads

This page is how WebsiteChat captures and qualifies a website lead. The visitor is already in the chat. WebsiteChat answers from the site, continues when they show they want a person, and collects the contact step you configured.

The WebsiteChat lead workflow

  1. The visitor asks something the site can answer: coverage, a published price range, what a plan includes, how long setup takes.
  2. WebsiteChat answers from those pages first.
  3. If they continue with a request a person must receive — a demo, a quote, a viewing, a consultation — that is the qualifying turn.
  4. When a Conversion Goal matches, a call-to-action can appear under the reply and open an inline form. Goals stay off until you enable them, and only after the site has crawled knowledge.
  5. Your team receives the inquiry. WebsiteChat does not sync a CRM, start an email sequence, write a proposal, or book a calendar.

If you would rather keep the site’s existing form, the same turn can point there instead of opening the inline form.

What WebsiteChat collects, and what it leaves

In the chat With your team
The published answer, then the contact step you configured The proposal, the price that is not on the site, the commitment
A comparison of published options, if they are still choosing Negotiation. Comparison itself is sales assistance
An hours or policy answer that ends without a form A support exception. That job is customer support

A plain FAQ answer that should not ask for contact is website FAQs. Install steps are in the guides.

This page is how WebsiteChat captures and hands off a lead. If you are deciding whether chat belongs between a visit and an inquiry, start here: How to turn website visits into qualified inquiries.

Frequently asked questions

Can WebsiteChat collect a lead in the chat?
After the site is crawled, you can turn on Conversion Goals. On a turn that matches a goal, WebsiteChat still answers first, then can show a call-to-action and an inline form. Nothing appears until you enable those goals.
What does a qualified handoff look like?
The visitor has already asked something your pages can answer, and a follow-up has shown they want a person: a demo, a quote, a visit, or a consultation. The form or the contact page receives that context. WebsiteChat does not write the proposal.
Can it ask a qualifying question?
It can continue the conversation from the visitor’s question. It should ask only what your published content and your configured goal support. It does not score leads or push them into a CRM.
Does every conversation become an inquiry?
No. An hours question can end as an answer. The contact step is for the turn where the visitor wants a next step a person has to receive.
How is this different from the sales use case?
Sales assistance compares published options so someone can choose. Lead generation is the handoff when they want a person to receive the request. One chat can do the comparison first and the handoff second.

Add this chat to your website

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