Kibo / For IT service desk
IT service management, on time by design.
Tickets logged from a sentence or an email with due times from your service levels, recurring incidents turned into problems, and changes kept on their approval path. For security incidents, the regulatory clock starts from the moment the organisation becomes aware of them.
Service desk, problems, changes and security incidents.
Kibo works on tickets, problems, changes and security incidents. People describe the issue in plain language; Kibo files it, sets the targets from your service levels and shows the ticket before saving it.
Records it works on:
- Tickets
- Problems
- Known errors
- Changes
- Security incidents
- SLA targets
- Assets
Outcomes, not screens.
Due times come from your service levels, and the clock pauses while a ticket waits on its requester. Three or more tickets on the same cause within 30 days become one problem, whose workaround reaches every new ticket. NIS2 deadlines for significant incidents are tracked hour by hour, weekends included.
Approved once. Enforced every time.
Service levels are a policy: response and resolution targets per priority, approved by the head of IT, versioned and applied to every ticket the same way.
Sovereign by design.
On your own servers, or hosted for you in a region of your choice, with an open-licence model. Your systems, tickets and incidents are never sent to a third-party AI provider, and no telemetry is sent to anyone.
More: sovereignty · where Kibo runs · on-premise AI
Predictable cost.
Every requester, agent and ticket is included in the same annual licence as the rest of the company, with no per-seat, per-token or per-module pricing.
More: total cost of ownership
Service levels computed, not guessed.
Due times and regulatory clocks are computed by code. Nothing is closed, sent or changed without confirmation, and every ticket, change and incident is in the audit record with its timeline.
More: governance · security · policy as code