A service desk that warns you in time.
Queues with business-hours SLAs, warnings before the breach and escalation, ITIL types, a service catalog and automation rules. A big ticket becomes a project without retyping.
What it does
SLAs and escalation
Per-queue policies, pause while waiting, warnings and escalation to the right person.
ITIL types
Incident, request, problem and change, each with its fields.
Service catalog
Each service with its form; users request it from the portal.
Automation rules
They assign, prioritize and link the affected service.
Time and survey
Time worked per agent and a satisfaction survey on resolution.
Email, API and webhooks
Tickets from email, a token-based API and signed webhooks.
How it works
The ticket arrives
From the portal, email or another system via the API.
Rules sort it
Queue, priority, owner and service.
The clock runs
On business hours, with a warning before it breaches.
It is resolved
And the user rates the service.
See it in one minute
Your data, wherever you decide
Your project documents stay wherever you put them.
On your servers or in the cloud
Installed on your infrastructure, or on a dedicated instance we operate on Google Cloud.
Encrypted files
Every file is encrypted with AES-256-GCM and a per-project key; connections run over TLS.
Audit log
Key actions are logged with user, date, IP and device.
AI privacy
Enterprise APIs that don't train on your data, or a local model on your infrastructure.
Our security standards
Frequently asked questions
Does the SLA count weekends?
It depends on the queue's policy: 24×7 or business hours with holidays, and it can pause while the ticket is "Waiting". The warning arrives before it is breached.
Shall we see it with your documents?
No commitment · Support in Spanish and English