ERPONA
Nüvə və interfeys

Assistant

You ask in a chat - the assistant finds the screen, explains the term and walks through the procedure step by step. When it does not know, it says so.

The problem

Hundreds of menus, hundreds of screens

In a system with hundreds of menus a user's question always takes one of three forms: "where is it?", "what is this?", "how do I do it?". An onboarding tour does not solve them - a tour happens once, the questions arise daily.

The answers are in fact already in the system: menu names, the help text of screens, the company's own glossary. They are simply not where anyone looks - the user does not know what to search for.

How it works

Two hard rules

First: nothing is invented. An answer comes only from the system's own index. If the match is weak the assistant says it does not know and offers the closest results as suggestions. In an accounting system an invented answer is worse than none.

Second: the assistant opens no door. It finds only the screens you are allowed to see - someone else's data never appears in an answer.

Unanswered questions are logged. That is the most honest list of where the documentation falls short.

Screens

What this module adds

In the system this module opens the following items.

Şablon cavablar Assistant Köməkçi indeksi Köməkçi indeksini yenidən qur Sual jurnalı Prosedurlar Hazır suallar Müştəri lüğəti Addım-addım sessiyaları
Questions

Most often asked

Does the assistant send data outside?

The index is on your own server. The optional language-model layer is off by default; when it is switched on, only the question and the facts found for it are sent.

What happens when no answer is found?

It says so, offers the closest screens and writes the question to the log - the next documentation update is planned from exactly there.

See this module with your own data

The demo database is full of real documents - not a mock-up. Send a request and we will walk through your scenario.