Service desk & incident management
Every request answered, and every promise kept.
Service desk, ticketing and incident management with live SLAs, major incidents, a public status page, changes with CAB, knowledge and an asset register.
The business problem
What Resolva fixes.
Without it
- SLA clocks pause without anyone knowing why, so breaches surprise everyone.
- Major incidents are run over chat, and customers learn about outages last.
- Laptops and phones are issued without acknowledgement or a clean return process.
With Resolva
Agents work a keyboard-first queue with live SLA countdowns; incidents run from one cockpit with a public status page; assets are issued, acknowledged and returned.
Core functionality
Everything in one place.
Tickets & live SLAs
Countdowns that explain exactly why a clock is paused.
Major incidents
An incident cockpit and a public status page.
Problems & changes
Change requests with CAB, risk questions and freeze conflicts.
Knowledge & catalog
A self-service portal that suggests answers as people type.
Asset register
Issue devices with digital acknowledgement and a wipe gate on return.
Nova assistant
One-click triage and a drafted reply for every ticket.
Meet Nova, the Resolva assistant.
Built on the same governed pattern as every Alexon assistant.
- Off until an administrator enables it
- Sees only what the user may see
- Every question and action is audited
Built on the unified platform
The foundation comes standard.
The same security and governance practices sit under every platform. Read the trust centre.
Email sign-in, with roles per organisation.
Row-level security in the database.
Every change and approval recorded.
Open exports and documented APIs.
Also in Operations & Service
Engineering disciplines behind it
Who is Resolva for?
Service desk, ticketing and incident management with live SLAs, major incidents, a public status page, changes with CAB, knowledge and an asset register.
What problem does Resolva solve?
The usual starting point: SLA clocks pause without anyone knowing why, so breaches surprise everyone. With Resolva: agents work a keyboard-first queue with live SLA countdowns; incidents run from one cockpit with a public status page; assets are issued, acknowledged and returned.
Is our data kept separate from other organisations?
Yes. Each organisation's data is separated by row-level security in PostgreSQL, enforced by the database itself, and every sign-in, change and approval is written to an audit trail.
Do we have to use the Nova assistant?
No. Nova is switched off until an administrator in your organisation turns it on. When it is on, it sees only what the signed-in user is allowed to see, and its questions and actions are audited.
Can Resolva connect to our other systems?
Yes. Every Alexon platform has documented APIs and webhooks, and connections set up once in the integrations hub can be reused across products. We confirm the specific connectors you need during discovery.
Can we get our data out?
Yes. Your data can be exported in open formats at any time, and everything the interface can do is also available through documented APIs.
How quickly can we get started?
Discovery takes one to two weeks. You then work in an environment on your own data while we configure, integrate and prove the platform, typically by weeks four to eight depending on scope and data migration.
See Resolva on your own data.
A working session with an engineer, not a slide deck. Bring the process you want to fix.