Your users unblocked straight away, your support team free for the hard questions

How do I turn this feature on, why can't I log in, is something down, where is my invoice: many questions to your support team are already answered somewhere in your documentation, but your users can't find it. With AI customer service they get an instant answer from your own guides and help articles, and the questions that really need a specialist reach your team complete.

Reset linkSentI can't log in

The questions you receive

  • "How do I set up this feature?"
  • "I can't log in, and the reset email isn't arriving."
  • "Is it down on your end, or is it me?"
  • "How do I add a user or change permissions?"
  • "Where can I find my invoice, and how do I change my plan?"
  • "Could you add this feature?"

What you can automate

Question typeWhat happensChannel or service
How-to questionsAn answer in plain language from your own documentation, with a link to the right help articleKnowledge base
Login and accessThe steps for a reset, and a ticket for support if it still does not work. The AI never asks for a passwordChatbot for your website
OutagesThe AI mentions known outages and points to your status page. New reports reach your team bundledHelpdesk setup
Users and permissionsAn explanation per role, and a request ready for support if an admin cannot do it themselvesKnowledge base
Invoices and plansAn explanation of where to find it, and a complete request for your billing team or account managerEmail and ticket automation
Ideas and feature requestsLogged and sent to your product team, with no promise about whether or when it will comeIntegrations with your systems

Example scenario

Example scenario

Example scenario: not a client case, but a realistic illustration.

Situation
A software company with an online platform for business customers gets questions through the in-app chat, email and phone. A large share is about how a feature works, logging in and adding users, while the answer is already in the help articles. After an update or during an outage everything arrives at once, and the support team answers the same question over and over.
Solution
An assistant in the application and on the website that answers from the documentation and help articles, and links to the right article. With login problems the AI explains the steps and never asks for a password. During a known outage it points to the status page, and new reports come in bundled. Questions that need a specialist go to second-line support as a complete ticket, with customer, environment and what has already been tried.
What it delivers
Users get an instant answer, outside office hours too and in their own language. The support team spends more time on hard questions, and the tickets that come in are complete.

→ More example scenarios

Multiple products or offices?

Many software companies have several products, plans or customer environments, and sometimes teams in different countries. The AI knows which product or plan a question is about, from the question itself, from where it is asked in the application or by simply asking. Per product or team you record:

  • which documentation and help articles belong to that product;
  • which features come with which plan;
  • which team is responsible and where a question should go.

General knowledge, such as logging in, invoices and terms, lives in one place. A change applies to every product straight away.

Connections you often need

  • Your documentation and help articles, so answers always come from the current version.

  • Your ticketing system, for complete tickets with customer, environment and history.

  • Your status page, so the AI knows about known outages.

  • Your customer or subscription records, for questions about invoices and plans.

People stay in control, and your customers' environments stay safe

Example conversation. Customer: I'd like to move my membership to a different location. AI assistant: That's possible. Because your contract is still running, I'll pass you to a colleague. Lisa from the team is taking over Lisa (team): Hi, I'm Lisa. I can see your question, I'll sort it out right away.

  • Never asks for passwords or keys

    The AI does not ask for passwords, codes or access keys, and warns users if they share them anyway. That also teaches your users that your support never asks for them.

  • Only answers from your own sources

    If something is not in your documentation, the AI says so honestly and passes the question on. It does not make up a feature or a fix.

  • Nothing changed without your rules

    You decide in advance what the AI may and may not do in a customer's environment. Changes to settings, permissions or data go through your team by default.

  • Handover

    Bugs, outages with real impact and unhappy customers go to your support team, with everything that is already known.

  • Agreements on data

    Customer data is only used for the question at hand. Data processing agreements are put in place with the suppliers.

Frequently asked questions

How up to date are the answers after an update?

The AI answers from your documentation and help articles. When you update those, the AI uses the new version. Anything not yet documented, it passes on to your team.

Can the AI run inside our application, not just on the website?

Yes. The assistant can work on your website, in your application and in your helpdesk, based on the same knowledge.

Does this work with our ticketing system?

That depends on the system. A connection is often possible; otherwise questions arrive by email in your existing workflow. The first step looks at what is possible.

Can the AI answer technical questions from developers too?

If the answer is in your documentation, yes. Questions that need more go to your second-line support as a complete ticket.

What happens during a major outage?

You report the outage once, for example on your status page. The AI mentions it with every question about it, and new reports reach your team bundled, so they do not keep pouring in one by one.

Ask the AI a question the way your users do

For example: "How do I give a new colleague read-only access?" Or book a demo using your documentation as the example.