Table of Contents
- Key takeaways
- What is a lead generation chatbot?
- What SiteGPT can and cannot do for lead capture
- How to build a lead generation chatbot in 7 steps
- Step 1: Train the chatbot on buying-stage pages
- Step 2: Write lead instructions and pick a persona
- Step 3: Turn on lead collection and choose the contact fields
- Step 4: Choose when the lead form appears
- Step 5: Pick an industry template or add custom fields
- Step 6: Route every lead to the people who follow up
- Step 7: Install the chatbot and test with a new email
- How to choose your trigger and lead routing
- What does a lead generation chatbot cost with SiteGPT?
- Worked example: a demo request on a pricing page
- Common mistakes when building a lead generation chatbot
- Frequently asked questions
- Basics
- What is a lead generation chatbot?
- Is a lead generation chatbot better than a contact form?
- Can the chatbot qualify or score leads?
- Setup
- How do I build a lead generation chatbot without coding?
- What information can the chatbot collect?
- Can the chatbot ask for details before the conversation starts?
- Does the chatbot slow down my website?
- Leads and CRM
- Where do the leads go?
- Does SiteGPT connect to HubSpot or Salesforce?
- What happens when the same visitor submits the form twice?
- Cost and plans
- How much does a lead generation chatbot cost?
- Is there a free plan?
- Can the chatbot capture leads in other languages?
- Sources

- A lead generation chatbot answers a visitor's question, then shows a short form inside the chat and saves the details as a lead.
- With SiteGPT the build takes 7 steps and no code: train, instruct, turn on lead collection, pick a trigger, add fields, route leads, install and test.
- Pick one of three triggers. When user shows interest is the recommended default. When unable to answer and After N messages are the other two.
- Lead emails, the Leads Dashboard, and CSV export work on every plan. The leads webhook, the only automatic route into a CRM, needs Scale or above.
- The lowest cost is SiteGPT Starter at $468 a year billed annually, or $59 a month billed monthly.
Key takeaways
Question | Short answer |
What does a lead generation chatbot do? | Answers questions from your content and collects contact details in a form inside the chat |
When does the form appear? | At one trigger you choose: when the visitor shows interest, when the AI cannot answer, or after a set number of messages |
What does it collect? | Email always, plus name, phone, and custom fields you define. The page URL is saved automatically. |
Where do leads go? | The Leads Dashboard and lead emails on any plan. A webhook to your CRM on Scale and above. |
Which SiteGPT plan is needed? | Any plan for lead capture. Starter is $59 a month, or $39 a month billed yearly ($468 a year). |

What is a lead generation chatbot?
What SiteGPT can and cannot do for lead capture
Task | SiteGPT | Plan |
Answer product, price, and service questions from your pages | Yes | Any plan |
Show a lead form inside the chat | Yes, with one of three triggers | Any plan |
Ask for details before the chat starts | Yes, with the Pre-Chat User Details form | Any plan |
Collect custom fields such as budget or company size | Yes, with the Custom template | Any plan |
Email each new lead to your team | Yes | Any plan |
Export leads as a CSV file | Yes | Any plan |
Send each new lead to a CRM automatically | Through the leads webhook and a tool that receives webhooks | Scale and above |
Create a CRM contact directly | No. There is no built-in CRM connection, and no HubSpot integration today. | Not available |
How to build a lead generation chatbot in 7 steps
Step 1: Train the chatbot on buying-stage pages

- The pricing page, so the chatbot answers cost questions without guessing.
- Product, feature, or service pages, so it answers "does this fit my case?"
- Comparison and integration pages, which hold the answers that decide a purchase.
- FAQ, security, and policy pages, which answer the objections that stop a visitor from reaching out.
Step 2: Write lead instructions and pick a persona
- Sales Expert highlights benefits and guides the visitor toward taking action.
- Consultant advises, asks qualifying questions, then suggests a solution.
- Urgent & Action-Oriented creates urgency and uses strong calls to action. Use it with care on considered purchases.

You are the website assistant for [Company Name].
Answer only from the product, pricing, and FAQ content you were trained on.
Answer the visitor's question first. Then offer a demo or more information.
Never invent a price, a feature, an integration, or a customer result.
If the content does not answer the question, say so and offer to have the team follow up.
Keep answers short and end with one clear next step.Step 3: Turn on lead collection and choose the contact fields

- Under Basic Contact Fields, turn on Name, Phone Number, or both. Email Address is always collected and cannot be turned off.
- Under Industry Template, pick a template or Custom. Step 5 covers this choice.
- Under Collection Triggers, pick one trigger. Step 4 covers this choice.
- Select Save Changes.
Step 4: Choose when the lead form appears
Trigger | What happens | Fits |
When user shows interest (Recommended) | The AI shows the form when the visitor shows real interest, for example a pricing question | Most sales and demo pages |
When unable to answer | The AI shows the form when it needs more details about the visitor's situation to answer well | Quotes and case-specific services |
After N messages (static form) | The form shows after the visitor's Nth message, with N from 1 to 20. The AI does not decide. | Teams that want the same moment every time |

Step 5: Pick an industry template or add custom fields

- Under Custom Form Fields, select Add Field.
- Enter a Display Label, such as Company size, and a Field Name, such as company_size. The field name shows in exports and webhooks.
- Pick a Field Type: Text, Email, Phone, Text Area, or Select Dropdown.
- Turn on Required field if the visitor must fill it in, then select Save Changes.
Step 6: Route every lead to the people who follow up

- Lead email. Under Lead Capture Email Notifications, keep Enable Lead Notifications on and add recipients. With an empty list, every team member except the Agent role gets the email.
- Leads webhook. In Settings, then Webhooks, enter a Leads Webhook URL and a token. SiteGPT sends a JSON POST for each new lead with the token in the X-WEBHOOK-TOKEN header. This needs Scale or above.
- CSV export. In the Leads Dashboard, select Export CSV for every lead that matches the current filter.
- Auto-escalate on lead capture. Turn this on to hand the chat to a person after the visitor submits the form. Human support must be set up first.

Step 7: Install the chatbot and test with a new email

- Ask a question that matches your trigger, such as a pricing question for When user shows interest.
- Submit the form with a new test email address.
- Check that the lead shows in the Leads Dashboard.
- Check each route you set up: the New Lead Capture email, the webhook request, or a row in the CSV export.
- Ask a question your content does not cover, and confirm the chatbot says so instead of guessing.
How to choose your trigger and lead routing
If you need | Pick | Why |
Demo or quote requests from pricing questions | When user shows interest | The AI asks when the visitor shows buying interest, after it answers |
Leads for case-specific questions such as a custom quote | When unable to answer | The form appears when the AI needs the visitor's details to answer |
The same capture moment in every chat | After N messages | Fixed and predictable. The AI does not decide. |
A contact for every conversation, even short ones | Pre-Chat User Details set to Required | No one chats without sharing details, so fewer people start a chat |
A salesperson alerted in their inbox | Lead email on any plan | Each new lead arrives with its fields and a Reply to button |
Every lead in a CRM without manual work | SiteGPT Scale with the leads webhook | The webhook is the only automatic route out of SiteGPT |
A weekly import into a spreadsheet or CRM | CSV export on any plan | No webhook needed, so Starter is enough |
What does a lead generation chatbot cost with SiteGPT?
Plan | Billed monthly | Billed yearly | What it adds for lead generation |
$59 a month | $39 a month ($468 a year) | 1 chatbot, 4k messages a month, lead form, lead emails, CSV export | |
$129 a month | $79 a month ($948 a year) | 2 chatbots, 10k messages, 4 members, iOS app, Slack and other chat integrations | |
$429 a month | $259 a month ($3,108 a year) | 3 chatbots, 40k messages, 10 members, leads webhook | |
SiteGPT Enterprise | Custom | Custom | Custom limits, signed DPA on request |

- Starter: $468 a year billed yearly, against $708 billed monthly ($59 x 12). Annual billing saves $240, or 34%.
- Growth: $948 a year billed yearly, against $1,548 billed monthly. Annual billing saves $600, or 39%.
- Scale: $3,108 a year billed yearly, against $5,148 billed monthly. Annual billing saves $2,040, or 40%.
- The webhook step-up: moving from Starter to Scale to get the leads webhook adds $2,640 a year on annual billing. A team that imports leads once a week can use CSV export on Starter instead.
- Message volume: 4k messages a month on Starter is about 133 a day. The quota is 4k GPT-4.1-mini messages or 400 GPT-4.1 messages, with any mix in between.
Worked example: a demo request on a pricing page
Turn | Visitor | Chatbot |
1 | Does the Pro plan include single sign-on? | Answers from the pricing page and names the plan that includes it. |
2 | What would it cost for 40 users? | Explains the per-user price from the pricing page, then offers a demo. |
3 | Yes, a demo would help. | Shows the lead form with name, email, and company size. |
4 | Submits the form | Confirms the details were saved and keeps answering questions. |
5 | Leaves the site | Nothing. The sales rep has the lead email with the page URL and can reply from it. |
Common mistakes when building a lead generation chatbot
- Asking before answering. A required pre-chat form stops visitors before their first question. Start with When user shows interest.
- Too many fields. Every extra field is one more reason to close the chat. Email plus one custom field is often enough.
- Training on the home page only. Pricing, comparison, and FAQ pages hold the answers that lead to a demo request.
- Prices typed into the instructions. Keep prices on a page the chatbot is trained on. Starter refreshes content manually, Growth monthly, and Scale weekly.
- No one reads the lead emails. Add a named recipient list instead of relying on the default team list.
- Testing with the same email. A repeat email updates the existing lead and does not fire the webhook, so a test can look broken when it is not.
- Promising a CRM sync on Starter. The leads webhook needs Scale. On Starter and Growth, use lead emails or CSV export.
















