How to Answer SaaS Onboarding and Setup Questions From Your Website Chat

A new trial user signs up late in the evening, logs in, and hits the first wall. Where do I connect my data? How do I invite my cofounder? Which setting turns off those emails? The answer is probably in your docs. The user just cannot find it in the next two minutes, so they close the page and plan to come back later.

Many never do. Setup questions are not sales questions and not bug reports. They are "how do I" questions, asked at the exact moment a person is trying to get value from your product.

This guide shows how to answer onboarding and setup questions from your website chat, so new users get their next step right away, at any hour, without waiting for your team to wake up.

Why setup questions decide your trial

Pricing questions come before the signup. Setup questions come after it, when the person has already said yes once and is now deciding whether your product is worth the effort.

An answer that arrives tomorrow morning by email reaches someone who has already moved on. An answer that arrives in seconds, on the page they are looking at, keeps them going.

Setup questions also repeat, which makes them a perfect fit for a chat that answers from your own material.

The four kinds of onboarding questions

Read your support inbox from the last few months and sort every message from trial users. Most setup questions fall into four groups.

• First login and account. How do I sign in, reset my password, change my email or switch workspaces?
• Connecting things. How do I connect my other tools, import my data or install the snippet? Do I need a developer for this?
• Inviting people. How do I add teammates, what roles exist, and does adding people change my bill?
• Finding a setting. Where do I change notifications, my time zone, my branding or my billing details?

Write the questions down in your users' own words, not the words in your menu.

Give your chat the right material

An AI chat can only answer setup questions well if it has read the places where the answers live. For most SaaS products, that is three sources.

Your help docs or help center. This is where the step by step answers already are. In Assistly you can add a help center or docs site as its own source next to your main website, so the chat can answer how to questions from it. When an answer comes from a help page, the chat ends it with a "Read more" link to that page, so the user can open the full guide.

Your own questions and answers. Some setup answers are too important to leave to whatever a page happens to say: whether a developer is needed, what happens to the bill when someone adds a seat, which plan includes a given integration. Write those as short entries yourself. Keep each one to the point and use the exact button names from your product.

Files. If your setup guide lives in a PDF or a document rather than on a page, add it as a file so the chat can use it too.

One rule matters more than the rest: the chat should answer only from your material. If something is not there, it should say it does not know instead of guessing. A confident wrong answer during setup does more harm than an honest "I am not sure."

Put the chat where setup happens

A chat on your marketing site helps people decide. Onboarding questions, though, mostly happen after login. If your chat only lives on the homepage, the user has to leave the product to ask.

Assistly can run inside your own app too. You add the chat code to the layout your signed in pages use and pass who is signed in. Your team then sees the user on the conversation, and the chat does not ask for an email it already has. With identity verification, which comes with Pro and Premium and during a free trial of them, your server signs each user with a secret key, and the chat can use the user's plan and company in its answers for verified users. That lets it say something like "on your current plan, here is where that setting lives" instead of a general answer.

On your public pages, suggested questions help too. You can show up to 3 questions under the chat's first message and set different ones for up to 5 pages. On your getting started guide, that might be "How do I connect my data?" and "How do I invite my team?" One tap and the answer appears.

Be honest about what the chat cannot do

Setup questions often touch the user's own account: "Why is my import stuck?" or "Did my teammate get the invite?" A website chat that answers from your docs cannot look inside a customer's account or press buttons for them, and it should not pretend to.

Teach it a clear path for these cases instead. Give the general steps from your docs, then offer a person. In Assistly, when a visitor asks to talk to a person, the chat gets a Needs you tag and an email goes to your lead alert address. You can switch the conversation from AI to You, answer yourself, and hand it back when you are done. If the user already left and gave an email address, your reply reaches them by email with a link back to the same chat.

Bugs belong in the same lane: a quick personal reply beats any automated message.

Close the gaps every week

The best part of answering setup questions in chat is what you learn from them. Every question a new user types shows you where your onboarding is unclear.

Once a week, look at the questions your chat could not answer. Write the answer once and the chat uses it from then on. In Assistly you can also rate any answer with a thumbs down and type what it should have said. If the same setup question keeps coming up, the real fix may be a clearer empty screen, a better label or a line in your welcome email.

When you ship a change to setup, update the help page and your own answers in the same release. Assistly rereads your website and help docs every week on its own, and you can press Refresh to read them right away after a big change.

Frequently asked questions

New trial users are most motivated in the first hour after signup. To make sure every setup question in that hour gets an answer, start a 30 day free trial at assistlychat.com, no card needed.