Skip to content

The service desk the whole shop works from.

Service is the professional services automation (PSA) system in The One Stack, the platform MSPs run their whole business on. It carries a request through ticket, dispatch, time, approval, invoice and payment for your service desk, your field technicians and your billing staff. It takes the place of a separate PSA, project tool, paging tool and the billing add-ons around them.

Tickets, dispatch, projects and on-call share one queue and one clock. Time posts to the contract, the contract writes the invoice, and the client pays it in your portal.

Replaces: your PSA, project tool, paging tool and billing add-ons.

Harbor ITMeridian LawSample data

Service desk

All open tickets
Queue5 open
T-4821File server slow since this morningMeridian LawFixed by THEO
T-4820New hire setup, two laptopsCascade FinancialOn track
T-4819Backup missed on APX-SQL-02Apex ManufacturingFrom Backup
T-4817Phishing report, invoice lureNorthwind DentalFrom Security
T-4815Front desk printer offlineMeridian LawOn track
T-4821 · on this ticket
CallerDana Whitfield, Meridian Law
DeviceMER-FS01 · disk alert cleared
ContractManaged Complete · covered
Opened byTHEO, from a phone call
THEO

The cleanup runbook ran on MER-FS01 during the call, and the disk is back under its threshold. The volume still needs more space. That is outside the runbook, so it is assigned to you.

Take the follow-upSee what ran

Illustrative product view with sample data.

The job, start to finish.

The work Service carries, in the order it happens, and where it hands off.

  1. 01

    Request

    A request arrives by phone, email, a portal form or an alert from a device. Every channel lands in the same queues.

  2. 02

    Ticket

    The ticket opens with the client, the contact, the contract that covers the work and the response clock running.

  3. 03

    Dispatch

    A dispatcher assigns the ticket by skill and availability, or schedules an onsite visit. The technician works the job from the mobile companion.

  4. 04

    Time

    The technician logs time on the ticket, by timer or by hand. The entry carries the ticket’s contract.

  5. 05

    Approval

    Each contract sets whether an entry is approved as it is logged or waits for a manager. Nothing bills before it is approved.

  6. 06

    Invoice

    Billing staff post approved, billable work to an invoice, and the invoice run adds each contract’s recurring lines for the period.

  7. 07

    Payment

    The client pays by card or bank account in your portal, or autopay charges the saved method. The payment is recorded on the invoice and posts to your accounting.

Inside Service.

A few of its screens. Every module page shows its own.

A ticket

The ticket holds the conversation, the device it is about, the call that opened it and the contract that covers it. Time logged on it is what the invoice later reads.

Service desk

Illustration, sample data. One ticket with its conversation, the device it is about, the call that opened it and the contract that bills it.

The dispatch board

When a ticket needs a visit, the dispatcher places it on a technician’s day. The visit stays tied to the ticket, so the time and parts recorded on site land on the same record.

Dispatch and field service

Illustration, sample data. Each technician’s day beside the queue of unassigned work, with every visit tied to a ticket.

The invoice run

A billing run reads the contracts that are due for the period and lists them for review. Someone checks the list and generates one invoice per client.

Contracts, invoices and payments

Illustration, sample data. An invoice run: the contracts due for the period, reviewed in one list before any invoice is made.

What it hands to the other systems.

A device alert opens a ticket

When monitoring raises a critical alert, a ticket opens with the device attached. A repeat of the same alert joins the open ticket.

Monitoring and alerting

A detection opens a ticket

A detection from Defend arrives as a ticket with its recorded details. Response actions wait for a technician to approve them.

Detection and response

A reported phish opens a ticket

A message a client reports from Outlook opens a ticket in its own queue for your team to triage.

Email security

A missed backup opens a ticket

When a device stops reporting backups, a ticket opens for it. If it stays silent, the incident goes to on-call.

Monitoring and reporting

A missed call opens a ticket

A missed call or a voicemail opens a ticket matched to the caller, and the call summary is added to the ticket as a note.

Phone system

A signed quote becomes a contract

When a client accepts a quote, the contract is written with its services and its first billing periods. Nobody re-enters the lines.

Quotes and signatures

Margin reads the same record

Analytics reads tickets, logged time, contracts and invoices from the record the service desk works on, and reports margin per client and per contract.

Analytics

What changes for you.

For owners

One system carries the work from the request to the paid invoice, so margin per client and per contract comes from the time your team logged. You retire the project tool, the paging tool and the billing add-ons around your PSA.

MSP owners

For technicians

The ticket opens with the client, the device, the contract and the clock on it. You log time where you work, and the onsite job, the parts and the signature stay on the same ticket.

Service managers and technicians

For co-managed IT

Your client’s IT staff work their own company’s tickets in the thread your technicians read, inside the scope you grant. When they need you, they escalate the ticket to your team from the ticket itself.

Co-managed IT

Proof slot

A customer running Service on The One Stack

A named MSP, the tools it retired for this system, and a quote approved in writing by the customer.

Switching to it.

What imports

Integrate imports companies, contacts, tickets with their notes, and time entries from ConnectWise and Autotask. From Autotask it also brings contracts and invoice history. It connects QuickBooks Online and Xero for your accounting and takes other data by CSV.

Bring your data

What runs side by side

Integrate keeps a recurring sync from your current PSA, so tickets and contacts keep arriving in One while you move one client at a time. Your accounting stays where it is.

Run side by side

What you turn off

When the last client is on the service desk here, you retire your PSA, your project tool, your paging tool and the billing add-ons around them, on the renewal dates you choose.

How switching works

Questions

Questions about Service

Does Service replace my PSA?

Yes. Service is a full PSA: tickets, queues, SLA timers, dispatch, projects, on-call, time, contracts, invoices, payments and inventory. Your history imports through Integrate, and you can run both while you move.

How does time get to an invoice?

A technician logs time on a ticket, the entry is approved under the contract’s rule, and billing staff post approved, billable entries to an invoice. Time the contract already covers stays off it.

Can clients pay online?

Yes. A client pays an invoice in your portal by card or bank account, and can enroll in autopay. The payment is recorded against the invoice and a receipt is sent.

Does it sync with my accounting?

Yes. Invoices and payments post to QuickBooks Online through Integrations (Integrate), so nobody keys them twice. Integrate connects Xero as well.

What does THEO do in the service desk?

THEO triages new tickets, summarizes long threads and drafts replies. When a request matches a runbook you have switched on for that client, THEO runs the fix through Tier Zero. Anything else goes to a technician with the context on the ticket.

How is Service priced?

Service is included in the plan, which is priced by people and devices and not by module. The pricing page explains the units.

Start

Run on One.

Start a trial and bring one client across, or book a walkthrough and follow a call down the line with us.