PSA and ticketing

A professional services automation (PSA) platform is the operational core of a service desk: ticket queues with service level agreement timers, client and contract records, technician time tracking, and the billing that turns time and fixed fees into invoices. Most PSAs also carry light project management for onboarding and infrastructure work, a client-facing portal, and a knowledge base for repeatable fixes. What a PSA does not do is monitor or patch endpoints itself, back up data, or secure a network; those jobs belong to the RMM, backup and security tools that report into it. A PSA that tries to do everything usually does ticketing and billing worse than one built for that alone.

PSA pricing is almost always per technician or per named user who logs into the system, billed monthly, sometimes with a lower band for light or view-only seats. A few products offer a flat fee for a small team instead of counting seats individually. Client-facing portal access and end users raising tickets are not usually counted as billable seats, but it is worth confirming, since some vendors licence by total contacts rather than by technician.

The features that separate PSAs are ticketing with proper SLA timers and escalation, contract and agreement management that can hold multiple billing types per client, time tracking that ties directly to those agreements, and billing or invoicing that produces an accurate bill without a spreadsheet in between. Beyond that, look at project management for onboarding work, a client self-service portal, a built-in knowledge base, workflow automation for ticket routing, asset and configuration tracking, and how well reporting and dashboards show technician utilisation and SLA performance. A mobile app matters more for MSPs with field technicians than for a desk-bound team.

The PSA is the hub most other tools connect to. RMM integration lets alerts open tickets with device context already attached, which is usually the single biggest time saver in a service desk's day. Accounting integration, typically QuickBooks or Xero, avoids re-keying invoices, and documentation integration surfaces passwords and configuration notes inside a ticket instead of a separate tab. Before committing, check which RMM, documentation and accounting tools a PSA already has a native connector for, since a missing one means building and maintaining an integration yourself.

Ask what the contract term is and whether it renews automatically, what happens to historical ticket and client data if you leave, whether there is a minimum seat count, and whether implementation or data migration from your current PSA is included or charged separately. Also ask how seats are counted for part-time or seasonal technicians, and whether the price per seat changes at renewal.

A one or two-person MSP often gets more value from a simpler, cheaper PSA with fast setup than from a platform built for multi-department service desks, since SLA escalation chains and departmental routing add configuration overhead without much benefit at that size. A larger MSP with several technicians and multiple SLAs per client usually needs the contract flexibility, automation and reporting depth that the simpler products do not offer, and can absorb a longer implementation in exchange for tighter billing accuracy.