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 RMM alerts that open themselves as work. Turn the IT & Managed Services preset on and your workspace arrives already knowing how an MSP runs.
Preset: IT & Managed Services · 3 extensions installed at setup
What changes, in the hours it actually changes.
07:40 — an alert fires before anyone is at a desk
Your RMM posts to a Noots endpoint. The payload mapping you configured turns it into a task on the right board with the right fields, attaches an SLA, opens an incident channel, and pages the on-call team. Nobody transcribes an alert into a ticket ever again.
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.
Three extensions, switched on at setup.
Choose this industry during onboarding and the bundle is queued for you. Review it, drop anything you don't want, and the workspace initialises with the rest already working.
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
RMM Webhooks
Each endpoint gets its own inbound URL and a mapping screen that says which field of the alert payload becomes which field of the task.
- A per-endpoint inbound URL
- A payload-to-task-field mapping UI
- An alert opens a task with its SLA attached
- An incident chat channel opens and pages the team
The extensions 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.
- Invoices are produced and exported by Noots; sending and collecting them stays in your accounting system.
Built for the way your industry actually runs.
The ones buyers ask first.
Do the SLA clocks stop outside business hours?+
Yes. Each severity tier carries its own response and resolution target and its own business-hours definition, so time outside the working window is not counted against the target.
What happens when an SLA is about to breach?+
The escalation chain you configured pages the next name up through chat and through mail. If the target passes anyway, the breach is recorded against the task rather than being silently dropped.
Can our RMM post alerts into Noots?+
Yes. RMM Webhooks gives each endpoint its own inbound URL and a mapping screen where you decide which field of the alert payload becomes which field of the task. An arriving alert creates the task, attaches an SLA, opens an incident chat channel and pages the team.
Is any of this locked to a plan?+
Extensions respect your plan the same way the rest of Noots does, and an admin can install, enable, disable or uninstall any of them from Administration at any time. Disabling one removes its surfaces and stops its background jobs on the server, while keeping the data it already wrote.
Let your meetings run the project.
Connect Noots once and watch every conversation turn into updated boards, written summaries, and hours handed back to your team.
Free to start · No credit card required