# A website chatbot for lead generation and follow-up.

Use a WebotX website chatbot to answer service questions from approved content and give interested visitors a way to request follow-up. Leads can include contact details, the original enquiry, and contact permission so your team has context for a useful response.

Canonical: https://webotx.com/use-cases/lead-generation
Updated: 2026-11-05

## Help visitors decide what to ask next

A useful enquiry starts with clarity. A visitor may want to know whether you serve their area, what a package includes, or how an initial consultation works before sharing contact details. Prepare those answers so the assistant can explain your service and point to the relevant source.

Choose an enquiry journey your team can handle. For example, a service business might answer coverage questions, explain the published consultation process, and invite a visitor to request follow-up. The chat should reflect your actual process rather than promising a quote, appointment, or outcome the assistant cannot confirm.

## Prepare service information and follow-up expectations

Review your public service descriptions, coverage areas, eligibility conditions, contact page, and any published starting prices. Correct vague or outdated information in the captured summaries before approving it. When a price depends on a person's circumstances, describe the published process for obtaining a quote.

Set a greeting and suggested questions that help visitors explore the service. Test the important questions in Live simulator, including an enquiry outside your usual scope. The goal is a supported answer and a useful next step, not a commitment to accept every request.

![WebotX chatbox designer with website colors and an example assistant conversation](https://webotx.com/docs/screenshots/example-assistant-designer.jpg)

The chatbox designer pairs your appearance settings with an example conversation. This is a design preview, not a visitor chat.

- [Set up and test your assistant](https://webotx.com/docs/getting-started)

## Test the enquiry before asking for contact details

The following examples illustrate a service website workflow. Use your own approved facts and follow-up process when testing.

| Visitor question | Information to approve | Useful next step |
| --- | --- | --- |
| Do you work in my area? | A clear public service-area policy | Explain the listed coverage and hand off an uncertain location. |
| What is included in the consultation? | Published consultation description | Explain the scope and link to the source page. |
| Can someone discuss my project? | Your contact and enquiry process | Offer the configured follow-up option with contact permission. |
| Can you guarantee a price today? | Published pricing conditions | Explain the quote process instead of inventing a binding price. |

## Collect details with context and permission

Configure the available contact-collection options for the workspace and review what the visitor sees. A person may provide an email address or phone number and agree to be contacted about their enquiry. Custom fields and integrations depend on the workspace's membership and configuration.

In Leads, review the original question alongside the contact information and permission. Assign a person to follow up using the information the visitor provided. Keeping the enquiry attached to the lead helps the team respond to the actual request instead of starting the conversation again.

![Fictional Alex Example lead showing a delivery enquiry, original question, and contact permission](https://webotx.com/docs/screenshots/example-leads.jpg)

Leads brings together the enquiry, original visitor question, and contact permission. Alex Example and alex@example.com are fictional sample details.

- [Learn how conversations and leads work](https://webotx.com/docs/conversations)

## Review enquiry quality and the next action

After launch, read enquiries for patterns: visitors asking about the wrong service, unclear coverage, missing package details, or requests nobody followed up. Improve the approved source material and your team's process together. A higher count of submitted details alone does not show that the experience is helping visitors.

Test the mobile widget, an out-of-scope request, a request for a person, and the lead view before expanding the assistant to more pages. Keep published expectations aligned with what your team can deliver. If live paid plans are not enabled, use the current dashboard membership status when checking available lead options.

- Confirm contact permission and the original enquiry are available to your team.
- Agree who follows up and how the request is tracked.
- Refresh and approve service information when your offering changes.

## Lead generation: common questions

### How can a website chatbot support lead generation?

It can answer approved service questions and give interested visitors a configured way to request follow-up. Your team reviews the enquiry and contact permission before responding.

### Does WebotX automatically book appointments or send quotes?

The workflow described here collects and explains website enquiries. It does not establish an automatic appointment-booking or binding quotation integration. Give visitors your approved next steps and let your team confirm individual arrangements.

### Are custom lead fields available on every plan?

Lead collection options and integrations depend on membership and workspace configuration. Check the dashboard and pricing preview for your current allowances and billing availability.

## Continue with the next step

- [Install on Wix](https://webotx.com/platforms/wix)
- [Install on Squarespace](https://webotx.com/platforms/squarespace)
- [Review conversations and leads](https://webotx.com/docs/conversations)

## Support

Email: [support@webotx.com](mailto:support@webotx.com)