Tickets, alerts and SLAs that run themselves.
For MSPs, IT service providers and internal IT teams. Requests and monitoring alerts become tickets with an SLA clock that only runs in your business hours, a warning reaches a person before the target passes, the on-call engineer is paged, every device and licence is on the register, and the hours logged against a client become the invoice line.
28 tools switched on for this trade at setup. Untick any you don't need.Default project tabs
Backlog replaces List and Timeline because a service desk plans in days, Keys holds each client's credentials, and Tools books shared consoles.
Projects created on day one
- Service Desk
- Client Projects
- Internal IT
What changes, in the hours it actually changes.
Three moments from an ordinary week. Every one of them is a thing the product does, not a thing it could be configured to do one day.
07:40
an alert fires before anyone is at a desk
PagerDuty, Datadog, Zabbix, Alertmanager, UptimeRobot or any JSON webhook posts to a Navalo endpoint. The alert becomes a task on the right board with its SLA attached, and the person the on-call rota says is carrying it this week is paged. A repeat of the same alert updates the ticket it already made instead of opening a second one.
11:15
the queue is triaged, and the clock stops at six
Requests come in through Intake with a category and a priority and are triaged to a named engineer. Each severity tier carries its own response and resolution target, and every card shows a live countdown that runs only inside your working window, so a Friday-evening ticket does not burn its target over the weekend.
15:05
the warning arrives while there is still time
At three quarters of the target the warning goes to the assignee, to the ticket's channel and to an inbox. If nothing moves, the escalation chain pages the next step: the people you named, plus whoever is holding the pager right now. The SLA at-risk card on the home screen lists the near misses before they become breaches.
The three that do the heavy lifting.
Choose this industry during setup and its tools are queued for you. Review the list, drop anything you don't want, and the workspace initialises with the rest already working - or install any one of them on its own, later, from the marketplace.
SLA Timers
Severity tiers with their own response and resolution targets, counted on a business-hours clock, with a warning before the target passes rather than a badge after it.
- A live countdown on the card and the task panel
- Business-hours clocks, per severity tier
- A pre-breach warning that reaches a person
- Attainment measured over closed promises
Monitoring & RMM Webhooks
Adapters for PagerDuty, Datadog, Prometheus Alertmanager, Zabbix and UptimeRobot, and a mapping screen for anything else that posts JSON. None needs an API key.
- An inbound URL per endpoint
- An alert opens a task with its SLA attached
- A repeat updates the ticket instead of opening another
- A recovery closes it and stops the clock
Inventory & Assets
Every laptop, licence and spare part per client: who holds it, where it is, every movement logged, and reorders drafted as purchase orders.
- Assets with a holder and a location
- Stock levels per location, with a low-stock alert
- Items attached to the ticket that used them
- Reorders drafted as purchase orders to the vendor
How IT & Managed Services actually runs.
Each of these is a project in Navalo - its own board, tab strip, meetings, calendar and members. They are not pre-built modules and we will not pretend they are: what the industry gives you is the right defaults around them.
These sit on top of the whole product.
- On-call runs the rotation and the handover, and for a serious enough alert its home-screen takeover shows what broke, the clock and who is carrying the pager, with one press to acknowledge or escalate
- Time Tracking & Billing keeps the hour on the ticket it is billed against, and Invoicing turns a client's billable hours and the parts sold to them into the invoice
- The Keys tab on every client project holds credentials behind a code, with a timed unlock and a reminder before a secret expires; the Tools tab books shared consoles and lab boxes
- Intake is the front door every client request comes through, with a category, a priority and a named owner
- The CRM keeps accounts and renewals next to the work, with each account's health and its invoices on the account itself
- Every workspace also gets the core: Announcements, Forms, Polls & Surveys, Kudos, Standups, Approvals, Checklists & SOPs, Recurring Tasks, the Decision Log, the Timeline, Hands-On Scheduling, Notes, the Corkboard, the Handbook, the Policy Library, Structures, Navalo Signatures, Conversation Stats and Budgets
The honest edges.
- An SLA clock pauses when a person presses pause. There is no rule that stops it on its own because a ticket moved into a column called Waiting on customer.
- Navalo does not replace your RMM or your PSA. It receives their alerts and runs the work that follows.
- Intake is a queue people type into, not a mailbox that opens tickets on its own.
- Invoices are produced, numbered and exported by Navalo; collecting them stays in your accounting system.
Built for the way your trade actually runs.
The ones buyers ask first.
Do the SLA clocks stop outside business hours?
Who does an escalation page?
Does a flapping alert open a ticket every minute?
How do hours and parts become an invoice?
Open a workspace that already knows IT & Managed Services.
Answer what your organisation does, review what gets installed, and start with the boards, meetings, chat and calendar already in the right shape.
Free to start · No credit card required