A SaaS website chatbot for pricing pages and demo requests
Buyers on your pricing page want to know about seat limits, SSO and annual billing before they talk to sales. A website agent answers from your own pricing and security docs, then books a demo for the ones who fit.
What should a chatbot on a SaaS pricing page do?
It answers the plan questions that stall a buyer, such as seat limits, which tier includes SSO or an API, and how annual billing works, using only your pricing page, docs and security FAQ. It then asks a few qualifying questions you choose, like team size and use case, and books qualified visitors into a sales calendar through Calendly while sending smaller ones to self-serve signup.
Worked example
Routing visitors by fit, not by who asked first
Below is an example routing table for a product with a free tier, a team plan and an enterprise plan. Set your own thresholds.
| Visitor answer | Example rule | Next step |
|---|---|---|
| 1-5 users, no SSO need | Self-serve | Link to signup and the getting-started guide |
| 6-50 users | Team plan | Offer a 20-minute demo slot with an account executive |
| 50+ users or security review | Enterprise | Book with a senior rep, attach the transcript |
| Existing customer with a bug | Support | Hand off to the support inbox or Zendesk |
Reps open each meeting already knowing the seat count and the question that brought the visitor in, because the transcript and answers go to HubSpot or Salesforce.
Setup checklist
What to load before it answers buyers
- Pricing page and plan comparison, by URL, so changes are picked up when you retrain.
- Security and compliance FAQ exactly as your team has approved it; the agent should not go beyond it.
- Integration docs for the questions buyers ask most.
- Qualification questions, three at most, and the routing rules above.
- Calendly links per team and the CRM fields to write.
The embed is one line of code, and the agent can be live in about 5 minutes once the documents are in.
Boundaries
Questions the agent should pass to sales
Custom discounts, contract terms, data residency commitments and anything not written in your security FAQ go to a person. The agent should say "I'll get someone from our team to confirm that" rather than infer an answer. Also decide whether it may mention competitors at all, or should keep to your own product.
Measuring it
Numbers to watch in the first month
Track chats on the pricing page, demos booked from chat, demo show rate and the share routed to self-serve. Then read the transcripts for unanswered pricing questions; each one is a line your pricing page is missing.
See SaaS AI guide a new user through setup
Book a demo to map onboarding or demo qualification onto Botcadence with CRM write-backs.
Common Questions
SaaS website chatbot questions
Not if it waits to be asked and sends small teams straight to signup. Set it to open only when clicked, or after a visitor spends time on the plan table, and keep qualification to two or three questions.
Only from the security FAQ or documents you upload. It quotes what is written and routes anything else to your team. Do not upload drafts or internal notes you would not want a buyer to read.
HubSpot, Salesforce, Pipedrive and Zoho CRM connect directly, and Google Sheets, Slack and Zapier or a custom webhook cover the rest. The lead arrives with the qualifying answers and the full chat transcript.
Point the agent at your live pricing page URL and retrain it when the page changes. Remove old PDFs that mention retired plans, because the agent answers from whatever content it has been given.
Start with onboarding help or demo qualification
Start with guided onboarding or demo qualification, then add voice and billing answers once the agent handles the first set of questions well.
- Reader-first workflows
- Human handoff when needed
- Grounded in your content