Every ticket has a clock. Noots runs it.
Severity tiers, response and resolution targets on a business-hours clock, billable time that becomes an invoice, and monitoring alerts that open themselves as work. Choose IT & Managed Services at setup and the workspace arrives already knowing how a service desk runs.
Default project tabs
Backlog replaces Timeline — a service desk plans in days, not quarters.
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 Noots endpoint. The vendor adapter turns the payload into a task on the right board with the right fields, attaches an SLA, opens an incident channel and pages the on-call team. A repeat of the same alert updates the ticket it already made instead of opening a second one.
11:15 — the clock is visible, not buried
Every card on the board carries a live countdown to its response or resolution target, and the clock only runs during your business hours. When a target is about to breach, the escalation chain pages the next name up through chat and mail. Breaches are recorded, not silently forgotten.
17:30 — the hours are already billable
Engineers started a timer from the task, or added the entry by hand. Rates resolve per user, per project or per org. The Billing tab turns the week's unbilled hours into an invoice and exports the line items as CSV — no spreadsheet reconciliation on the last day of the month.
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 so a Friday-evening P3 does not breach over the weekend.
- Live countdown chip on the board card
- Business-hours clocks, per severity tier
- Escalation chains that page through chat and mail
- Breach states logged, not quietly dropped
Time Tracking & Billing
Start a timer inside the task, or add the entry afterwards. Rates resolve per user, per project or per org, and the Billing tab turns unbilled hours into an invoice.
- Task timers and manual entries
- Per-user, per-project and per-org rates
- A Billing tab that produces invoices
- CSV export of every line item
Monitoring & RMM Webhooks
Five vendor adapters — PagerDuty, Datadog, Prometheus Alertmanager, Zabbix and UptimeRobot — plus a custom mapping screen for anything else that speaks JSON. None of them needs an API key.
- A per-endpoint inbound URL, no API key required
- Vendor field and severity maps, or your own
- An alert opens a task with its SLA attached
- A repeat updates the ticket; a recovery closes it and stops the clock
How IT & Managed Services actually runs.
Each of these is a project in Noots — 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.
- Client calls join automatically and become the tasks they agreed to
- Autopilot plans the migration and reassigns when someone is over capacity
- The built-in CRM keeps accounts, opportunities and renewals next to the work
- GitHub sync closes a task when the fix is merged
- Chat channels are created per project and per team, with calls that survive navigation
The honest edges.
- Noots does not replace your RMM or your PSA — it receives their alerts and runs the work that follows.
- Six RMM vendors were deliberately left on the generic mapping rather than guessed at: a wrong field path maps nothing, which is indistinguishable from a broken integration.
- Invoices are produced and exported by Noots; sending and 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?
What happens when an SLA is about to breach?
Which monitoring tools can post alerts into Noots?
Does a flapping alert open a ticket every minute?
Is any of this locked to a plan?
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