Service desk

Service desk and client portal (built-in PSA)

For MSP teams who want tickets, time and customer records in the same product as their monitoring. Each ticket opens with the device, the customer and the history already attached.

Inside Revolutionary RMM · Service desk

Revolutionary RMM service desk board with tickets grouped by stateRevolutionary RMM service desk board with tickets grouped by stateRevolutionary RMM service desk board with tickets grouped by state

The board, with tickets grouped by the state they are in. Product capture with fictional customer names.

What it does

Everything a ticket needs to be useful.

How it works

From the first message to the invoice.

01

Intake

An email, a portal request, a text message or a monitoring alert opens the ticket.

02

Context

The ticket links to its device and customer. Related alerts are grouped into a case, with the tickets under it.

03

Work

The timer runs, remote sessions log their minutes, and service-level targets escalate when they slip.

04

Resolve and bill

Logged time is billed when the ticket is resolved, and a satisfaction survey goes out with the resolution.

Inside Revolutionary RMM · Cases

Revolutionary RMM cases list grouping related alerts and ticketsRevolutionary RMM cases list grouping related alerts and tickets

Cases group related alerts and the service work under them. Product capture with fictional customer names.

Client portal

Somewhere useful to send your customers.

Customers sign in to a portal with your logo, colors and business details. Which tabs each portal role sees is set per customer organization.

Around the ticket

The parts that make a desk a desk.

Limits

What it does not do yet.

Limits

  • Contract, service agreement and procurement workflows are limited compared with a dedicated PSA.
  • Tickets export with the rest of the workspace from Account > Billing, but full ticket threads and attachments are not in that export yet.
  • Text message tickets need your own SMS provider and business number, and have seen limited field use so far.
  • AI answers run only when a technician asks, and need your workspace's own AI key.
  • Not for you yet if your billing depends on contract management or procurement inside your PSA. Keep that tool for now and bring us the rest of the ticket workflow.

Not in the product today: honest outcome metrics (time to owner, time to verified resolution, technician minutes per case), and customer-facing outcome reports.

See the roadmap →

Questions

Good to know.

Many teams will not. Tickets, time, customers, documentation, assets and invoicing are in the same product, so work is not re-entered on its way to a bill. Check contracts, agreements and procurement against your own process first, because those areas are limited today.

Yes. A support mailbox is polled, replies thread onto the existing ticket by mail conversation, and held messages queue on a pending board instead of disappearing.

Yes, once you connect voip.ms, Twilio or Telnyx and a business number. Inbound texts open or continue tickets and replies are sent as texts. This path has seen limited field use so far.

No. A technician asks for it on a ticket, it answers with the device context in hand, and the question and answer are logged. It uses your workspace's own AI key and is not shown to customers.

Logged ticket time is the source of truth. Work is billed when the ticket is resolved, and remote sessions add their measured minutes to the ticket they belong to, so they are not billed twice.

Yes. It carries your logo, colors and business details, and so do the documents it produces.

Keep exploring

Limits, checked daily

Not in the product today.

Each line below is a gap recorded against this capability in the product's own feature record. A line leaves this page by itself on the next daily run once that record says the gap is closed, so the list cannot fall behind what we ship. The rest of this page is written by hand.

  • Parts and products cannot be added to a ticket and carried through to the invoice; recorded time is what reaches billing.
  • There is no add-in for the mail client, so a message becomes a ticket through the ticket mailbox rather than from inside the inbox.
  • Time is recorded on tickets and cases and reaches billing; a technician timesheet, with utilization to review and approve, is not built yet.

Next step

Bring us a ticket that took too many steps.

Half an hour on a call. We will walk through it in the product, from the first message to the invoice.