A software buyer reads your homepage, opens the pricing page and then looks for a reason to say no. The questions are predictable: what does it cost, is there a free plan, does it work with my tools, is my data safe, can I cancel. A SaaS website chatbot can answer those questions in seconds, as long as it answers only what you can stand behind.
This guide covers what to teach the bot, what to keep for your team, and the claims to avoid. It describes ConvoRail's live features only; where something is on the roadmap it says so.
What Do SaaS Buyers Ask Before Signing Up?
SaaS visitors ask about pricing, free plans, setup effort, integrations, security and cancellation. These questions decide whether they start a trial, so unclear answers cost sign-ups.
- Pricing: what each plan costs, what limits differ and what is included for free.
- Trial and free plan: whether a card is needed, how long it lasts and what happens afterwards.
- Setup: how long it takes, whether a developer is needed, what the first hour looks like.
- Integrations: which tools it connects to today, and which are planned.
- Security and data: where data lives, who can see it, which certifications exist.
- Cancellation and billing: how to cancel, refund rules, invoices.
How Should the Chatbot Answer Pricing Questions?
State the plan names, prices and the limits that differ, then link to the pricing page. Never let the bot round, discount or promise a custom price it has not been given.
Write one pair per plan question rather than one giant answer, and write them the way buyers type: "how much does it cost", "is there a free plan". Keep the numbers in one place so they are easy to update when pricing changes. The detail is covered in how to answer pricing questions in a chatbot.
What Can You Honestly Say About Integrations and Security?
Say only what is live today, and label the rest as planned. Buyers forgive a missing integration far more easily than a claim that turns out to be false.
| Topic | Safe answer pattern | Avoid |
|---|---|---|
| Integrations | "Works today with X and Y. Z is planned." | Listing planned integrations as available |
| Security | State what exists, such as account-level data separation | Naming certifications you do not hold |
| Data location | Point to your privacy policy | Guessing where data is stored |
| Uptime and speed | Link to a status page if you have one | Quoting numbers you have not measured |
ConvoRail follows this rule on its own site: security shows tenant data isolation as live and compliance certifications such as SOC 2 as roadmap, not a current claim. A bot taught the same honesty protects you from overpromising in chat.
What Should Go to a Person?
Hand over custom pricing, security questionnaires, procurement requests, bug reports and anything involving a specific customer account. The chatbot should not take actions in someone's account.
When the bot has no confirmed answer it tells the visitor so, offers a short form for name, email and phone, and flags the conversation as urgent in your shared inbox. A teammate replies live and the visitor sees the answer in the same chat. That is also the right route for sales-qualified questions, which deserve a human reply fast. See when a chatbot should hand over to a human.
How Do You Set Up a SaaS Chatbot Quickly?
Write answers for your top ten pre-sales questions, add them as Q&A pairs, set page-specific greetings for pricing and docs, and paste one script tag.
- 1Collect pre-sales questions from your inbox, demo notes and support tickets.
- 2Write plain answers with the fact first, linking to the pricing, features or docs page.
- 3Set a different opening message on the pricing page than on the homepage.
- 4Add three starter questions: pricing, free plan, how setup works.
- 5Test the awkward questions, including ones about features you do not have.
Pro Tip: Add a pair for "does it do X?" for each feature people wrongly assume you have, with an honest no and what you offer instead. It saves demos and builds trust.
How Do You Learn From the Conversations?
Use the unanswered-question list and conversation ratings to find missing answers and confusing pages. Every repeated gap is either an answer to add or a page to clarify.
SaaS teams often discover that visitors ask about comparisons, limits or onboarding that the site barely mentions. The weekly unanswered-question routine turns those into content.
What Do Sample SaaS Q&A Pairs Look Like?
Keep SaaS pairs factual, short and linked to the source page. These are templates; use your own plans, limits and policies.
| Visitor question | Answer pattern |
|---|---|
| Is there a free plan? | Yes. The free plan includes [limits] and needs no credit card. See [pricing link] for current limits. |
| Do I need a developer to set it up? | State the real setup steps. If it is one line of code, say so; if an integration needs a developer, say that. |
| Does it integrate with [tool]? | Say yes only if live today. Otherwise: "Not yet. It is planned / not planned." |
| Where is my data stored? | Link to the privacy policy; state only what you can verify. |
| How do I cancel? | Exact steps, any notice period and what happens to data afterwards. |
How Do You Stop a Chatbot Overpromising Features?
Give the bot an honest answer for every feature people wrongly assume you have, and keep a live-versus-planned list in sync with your product. Overpromising creates refunds and bad reviews.
- List the five features prospects most often ask about that you do not have.
- Write a pair for each: a plain no, and what you offer instead.
- Mark roadmap items as planned with no dates unless you can commit.
- Review the list whenever you ship or drop a feature.
ConvoRail's own site follows this rule by showing what is live and what is on the roadmap side by side, and its FAQ says plainly that advanced tone controls are not available today.
How Does a SaaS Team Use the Inbox Differently?
SaaS teams often use tags to separate sales, support and billing conversations, and assign pre-sales questions to whoever owns trials. That keeps the right person on the right conversation.
Create tags such as pricing, security, integrations and billing, and review them weekly. If many conversations carry the same tag, that topic needs a better page or a clearer answer. The shared inbox guide explains status, priority and assignee in detail.
Related reading: FAQ page vs chatbot, security questions to ask chatbot vendors and how to test a chatbot before launch.
Conclusion
A SaaS chatbot should answer pricing, free plan, setup, live integrations, security facts and cancellation, and label anything unbuilt as planned. Send custom pricing, security questionnaires and account issues to your team, and use the unanswered list to improve your site.
Key takeaways
- SaaS buyers ask about pricing, trial, setup, integrations, security and cancellation before signing up.
- Answer pricing with plan names, numbers and limits, and keep the numbers in one place.
- Say only what is live and label planned features and certifications as planned.
- Send custom pricing, security questionnaires and account issues to a person.
- Use the unanswered list to find gaps in your pricing and onboarding pages.
Quick Summary
A SaaS website chatbot should answer pre-sales questions about pricing, the free plan, setup effort, live integrations, security facts and cancellation, using only what is true today. Roadmap items and missing certifications should be labelled as planned. Custom pricing, security questionnaires and account-specific issues belong to your team, reached through a shared inbox with the visitor's details attached.
Want to see grounded answers on your own site?
Start free, add your Q&A pairs and paste one script tag. No credit card required.

Founder & CEO
Writes about grounded AI chatbots for websites: how they work, how to measure them and what to check before you buy.
Topics
Get new posts by email
Guides on AI chatbots for websites, straight to your inbox.
