PSA is the business half of running a managed service. The RMM watches the machines; the PSA holds the clients, the agreements, the time, the tickets and the invoices, and its value is almost entirely in the joins between those things rather than in any one of them. A shop that has outgrown a spreadsheet of contracts and a mailbox of requests is the buyer for this category, and the symptom is usually that nobody can say which client was profitable last quarter.
Ask vendors to quote against your actual endpoint count
What is PSA in IT, and what is professional services automation beyond the ticket queue
The phrase comes from consultancies before it came to managed services, and it means the software that runs a business that sells people's time. In an IT context that is the client record, the contract, the ticket, the time entry, the project, the quote and the invoice in one place. The automation in the name is not clever: it is the fact that a closed ticket with two hours on it turns into a billable line without anyone retyping it. That single join is what most of the licence is buying.
PSA vs CRM: two systems that both think they own the customer
A CRM is built for winning work and a PSA for delivering it, and both keep a company record, both keep contacts, and both will claim the other is a feature of themselves. Small shops usually run the PSA alone and lose the pipeline. Larger ones run both and argue about which record is true. If you run both, pick one as the source for company and contact and let the other read from it, because two editable copies of a client list diverge within weeks and the one your invoices come from is the one that has to be right.
PSA ticketing, and the PSA integrations that decide whether it is one system
The queue is where technicians live, so it gets judged on speed and on how few clicks a normal day takes. What decides whether the rest of the product is real is the connections: the RMM, so alerts arrive as tickets and tickets can act on machines; the mailbox and the directory; and the accounting system at the other end. Ask which of those are built by the vendor and which are somebody else's connector, because PSA integrations written by a third party are the first thing to break after an upgrade and the last thing anyone will own.
An ITSM ticket tool, service desk management and where PSA differs
ITSM products are built for one organisation serving its own staff, with change, problem and a service catalogue modelled properly. PSA is built for a company serving other companies, so its native ideas are the agreement, the client and the billable hour. Service desk management as a discipline applies to both, and the process frameworks are worth reading whichever you buy. The practical split is that an internal IT department growing up buys ITSM, and an MSP that wants to be paid correctly buys PSA.
Other questions people ask
Is an ITSM service desk the same as a PSA?
No. An ITSM service desk models one organisation's own service processes; a PSA models many client companies, their agreements and the billing. There is overlap in the ticket screen and almost none underneath it.
Is cloud based helpdesk software a PSA?
Usually not. A hosted help desk gives you the queue; a PSA adds contracts, time, quoting and invoicing around it. Some help desk vendors sell modules that close the gap, which is worth checking before buying a second system.
Do I need a PSA if I already have an RMM?
If you bill for time or run agreements, something has to hold them. Several vendors here sell RMM and PSA as one platform, which is why the bundles exist; the test is whether the weaker half is weak enough to cost you more than the second licence would.
What does a PSA cost?
PSA is usually priced per technician rather than per endpoint, which makes it hard to compare with RMM. SuperOps publishes a per-endpoint platform figure of $1.50 at its 100-endpoint minimum. HaloPSA's pricing page answers a block to every reader available here, so this record carries no figure for it rather than repeating one.