ISPINO: conversations, context, and knowledge
Use the operational assistant and understand threads, sources, permissions, suggestions, and limits.
Last updated: 2026-09-08
What ISPINO is
ISPINO is the assistant built into ISP Billing. In the administrative area it helps operators locate functions, understand prerequisites, interpret the page they are working on, and prepare operational text. It can explain a procedure, but it never replaces the operator’s checks, permissions, or final decision.
The public website uses a separate commercial instance. That version answers visitors with deliberately publishable product information: features, module differences, prerequisites, and supported workflows. It has no access to ISP tenants, customer records, invoices, tickets, or administrative actions.
How to open it and ask a question
Open ISPINO from its shortcut as a side panel when you want to keep the current page visible, or switch to fullscreen for a longer consultation. Describe the objective and the relevant function or record: “How do I configure automatic invoice reminders?” is more useful than “How does it work?”.
Include only the context needed to answer. Never paste passwords, API keys, payment data, authentication tokens, complete logs, or unnecessary personal information. If the answer depends on a value that ISPINO cannot see, state that value in a safe and redacted form.
Onboarding hint and initial suggestions
The introductory pill explains what ISPINO can help with and proposes starting questions. Open it when you need an example, or dismiss it once you know how to formulate requests. The suggestions are shortcuts, not fixed commands: adapt them to the module and outcome you actually need.
A useful first question identifies the area, the action, and the expected result. For example: “Which settings are required before creating the first contract?” or “What must be configured before customers can recharge a prepaid service?”.
Conversations and retention
New conversation starts a clean topic. The history can be searched across questions and answers; a thread can be renamed with a recognizable title, closed when the work ends, reopened, and resumed later. Closing archives the conversation and removes it from the active list, but does not delete it.
ISPINO retains the latest 30 threads. When new conversations exceed that limit, the oldest excess threads and their messages are removed. Keep unrelated customers and procedures in separate threads, and preserve any information that must become an official operational record through the ISP’s approved documentation process.
Follow-up questions and page context
A short follow-up such as “where is that setting?” is interpreted together with the recent exchange in the same thread. Continue an existing conversation only when it still concerns the same module, customer, ticket, or procedure; otherwise start a new one to prevent context from being mixed.
Answers, links, and proposed actions
On Hotspot pages, ISPINO may automatically add suggested checks for some errors with no identified cause, using approved official MikroTik documentation. Sources are linked in the explanation. The suggestion does not change the device or create a conversation in the history.
An answer may contain links to the relevant protected page or describe an action available in the current workflow. Check the destination, customer, service, and module before opening it. ISPINO does not silently save settings, send communications, issue documents, or alter network configuration.
When a response contains several steps, complete them in order and verify the stated result after each important change. If the interface differs from the explanation, stop and consult the current module page or the updated manual rather than improvising.
Preparing operational text and ticket replies
ISPINO can prepare drafts for supported fields. From the Ticket detail, the generation command opens the normal ISPINO panel with a fresh conversation for that ticket. It reads the authorized history from oldest to newest, distinguishes customer and ISP messages, excludes internal notes, and asks what should be communicated. A complete operator instruction produces the draft immediately; another question is appropriate only when an essential fact is missing.
Insert reply places only the customer-facing draft in the editor and does not send it. The system signature is managed separately. Before sending, reread the recipient, customer details, dates, amounts, links, and promised actions.
Official contextual information
Information icons connected to ISPINO open an official explanation written for that exact field, option, or command. This entry generates a fresh contextual response: it does not resume an old thread and does not create a saved conversation by itself.
Read the explanation and its links first. If the operator writes a follow-up, the exchange then becomes a normal conversation and enters history. Contextual information explains what an option does; it does not enable, save, or change that option automatically.
Feedback
Before reporting a bad answer, distinguish between missing documentation, an ambiguous question, outdated knowledge, and a permission that correctly hid operational data. This makes the correction actionable.