What Kolli does

Typed or spoken, from the browser.

An incoming email becomes a ticket at once, under the sender's own account.

Kolli answers the call, in Hungarian, and files a ticket.

The same conversation, from your pocket.

Its own speech recognition and its own voice. It never uses the browser's voice, because that would send the text away. Three Hungarian voices to choose from.

The customer's text is never turned into audio.

Every generated audio file carries machine-readable marking.

Kolli says only what a person wrote and approved. Word for word. It never improvises.

Fixed questions per request type. A colleague who does not write code can change them.

If a simple fix exists, Kolli shows it and files nothing.

A list computed from the knowledge base, including what it cannot do.

Only after an explicit yes.

The customer sees their own tickets and their state.

"What this was" and "How we solved it". Drafted by AI, approved by a person, then visible to the customer. Hungarian and English.

Cost, risk, who is affected, rollback, precedent. On one phone screen.

A recorded, named state. It cannot be skipped.

Today for one request type: a developer desktop from an email. The pattern extends to further request types.

In the customer's language, no internal detail. A person sends it.

A customer's admin sees their own organisation only. The right is granted to a person, never by default.

Six months, with the notice stated. Your organisation's admin may read it too.