How to Answer Account Questions Inside Your SaaS App Without Guessing

Most advice about website chat is about the marketing site and the visitor who has not signed up yet. But once someone becomes a customer, the questions change. They stop asking "does it do this?" and start asking "which plan am I on?" or "where is my order?".

Those are account questions, and they are where a chat assistant earns trust or loses it fast. A general answer to a specific question feels like being ignored. A confident wrong answer about someone's account is worse. Here is how to put chat inside your app so it helps customers with their own account, without guessing and without exposing anything it should not.

Why account questions are different

A signed in customer asks questions where the answer depends on who is asking. "What is left on my account?" has a different answer for every user. A chat that only knows your public pages can explain how accounts work in general, but it cannot tell this person what is true for them. If it tries, it is making something up.

So the first rule for in app chat is simple: a general question gets an answer from your docs, and a personal question gets an answer from real account data or from a person on your team. Never from a guess.

Put the chat where your customers already are

When something goes wrong, customers want to ask right there, on the screen where they got stuck, not hunt for your marketing site and explain everything from scratch.

Adding the chat to the layout your signed in pages share fixes that. The chat appears on every screen of the app, and you can pass along who is signed in: their name, email, user id and details like their plan or company. Your team then sees who they are talking to, and the chat stops asking for an email address it already has.

Know who is really signed in

Anyone can type a name or an email into a web page. If your chat simply trusts whatever details arrive with the browser, a person could pretend to be one of your customers and ask about their account.

The fix is to have your server sign each user with a secret key only it knows, and let the chat check that signature. In Assistly, your server signs the user id (or the email, if you do not pass an id) with your own secret key, and the inbox shows a Verified user tick only when the signature is right. Unverified names show as "says they are". You can also turn on a setting that only accepts verified users, so any details that arrive without the right signature are ignored and that visitor is treated as a guest. The key stays on your server, never in your web pages or the chat code. For verified users the bot can also use details like plan and company in its answers, so a customer hears "on your plan, this works like this" instead of a list of every plan. Verification comes with Pro and Premium, including during a free trial of them.

Let the assistant check real data, safely

Once you know who is asking, the assistant can look things up in your own system and answer from the real result.

Assistly calls these AI actions. You describe an action in plain words, such as "check order status when a customer asks where their order is", and point it at an https address in your own system. When a verified customer asks, the bot calls that address with the verified user's id, and your system decides what that user is allowed to see. If a detail is missing, like an order number, the bot asks for it first.

A few things make this safe by design:

• Only verified signed in users can trigger an action. Guests and unverified visitors never do. If they ask, the bot says it can only check that for signed in users and offers a person from your team.
• The bot answers only from what your system sent back. If the call fails, takes too long or comes back empty, it says it could not check right now and offers a person instead of guessing.
• Every call is logged as a note in the conversation, so your team sees what was checked.

AI actions come with Pro and up, also during a free trial, and nothing runs until you add an action and turn it on. Start with the question your team answers by hand most often.

Hand off the moment it is personal and sensitive

Some account questions should always go to a person: refunds, a suspected security issue, a billing dispute, a frustrated customer. Decide in advance which topics always go to your team. When a customer asks for a person, the chat should flag it and alert you. In Assistly, that chat gets a Needs you tag and an email goes to your lead alert address. You can take over the conversation, reply yourself, and then hand it back to the AI so it keeps answering anything else. Because the user is verified, you already know who they are and can skip the "can you confirm your email?" step. And if they left before you replied, your answer also reaches them by email when they shared their email address.

Close the loop every week

In app conversations show exactly where customers get stuck after they sign up, in their own words. Once a week, read the questions the assistant could not answer. Each one is either a missing doc, a confusing screen or a good candidate for a new action. On Starter and up, Assistly collects those unanswered questions in one place so you do not have to dig through every conversation.

A simple way to start

Add the chat to your signed in pages, turn on verification, decide which topics always go to a person, then add one action for your most common account question.

Assistly has a free plan with 50 chats a month, and paid plans from $29.99 a month, with a 30 day free trial that needs no card. Verification and AI actions are part of Pro ($149) and Premium ($299), and you can try them during the trial. You can see every plan at assistlychat.com/pricing.

Frequently asked questions