Skip to content

PSA for MSPs

MSP PSA software, built into the operations platform.

Tickets, SLAs, time tracking, quotes, projects and a client portal. Same database as the RMM and the billing engine. The work flows through one place, and so does the data.

A lot of "RMM with PSA" products treat the PSA as a ticket tab. You can raise a ticket, sort of assign it, sort of track time on it. Then you find out at month-end that the time entries do not join cleanly to the contract lines, the SLAs do not respect business hours, and the client portal is a different SaaS you have to brand separately.

OpsMerge treats the PSA as a peer to the RMM. Tickets point at assets. Time entries roll into billing. SLAs respect business hours and impact-urgency. The client portal is the same SPA, branded per organisation. One platform, one screen, one set of credentials.

Read the deep dive on ticketing · See the client portal · How the PSA feeds billing

OpsMerge PSA ticket queue showing SLAs, priorities and asset linking for MSP technicians

  • Real ticketing

    Statuses, priorities, ITIL impact-urgency, time tracking, internal notes, email-to-ticket with Message-Id threading. Configurable per organisation.

  • Client portal in the same SPA

    Branded per MSP. Invite-based login (passwordless magic-link in design). Clients raise tickets, see status, see invoices, all without a separate vendor.

  • Quotes that spawn the work

    Accept a quote and one click writes the invoice and opens the project ticket. No re-keying between systems.

  • Row-level tenant isolation

    Tenant boundaries enforced at the database. Clients cannot see other clients. Operators see only the organisations their role permits.

What ships

The PSA pillars

Ticketing

SLAs, time tracking, email-to-ticket, RFC 5322 Message-Id threading, per-tenant reply addresses, ITIL impact-urgency matrix.

Quotes

Build, send, accept. Acceptance is atomic: one click writes the invoice and opens the project ticket. No re-keying.

Products and catalogue

Suppliers, distributors, product rows with margins. CSV import. Used by quotes, invoices and recurring contract lines.

Client portal

Branded per MSP. Same SPA, same data model. Invite-based login; passwordless magic-link in design. VIP contact flag with priority handling.

Reporting

SLA performance, technician utilisation, billing rollups, audit log. CSV export today, BI replicas post-GA.

Asset linking

Tickets point at the same asset rows the RMM agent populates. One register, both pillars.

PSA questions

Common questions from MSPs evaluating us

  • What does an MSP PSA actually do?
    A PSA (professional services automation) tool runs the service side of an MSP: tickets, SLAs, time tracking, quotes, projects, client portal, and the billing rollup at the end of the month. OpsMerge ships all of those on the same database as the RMM.
  • Is the OpsMerge PSA a real PSA or a ticket tab?
    A real PSA. Statuses, priorities, ITIL impact-urgency matrix, time tracking, email-to-ticket with Message-Id threading, asset linking, internal notes, quote-to-invoice atomic acceptance, branded client portal. All shipped today.
  • How does email-to-ticket threading work?
    Per-tenant reply addresses route inbound mail to your tenant by sub-domain. Threading uses RFC 5322 Message-Id matching against stored comments, so replies survive subject mangling, forwards and threading-header stripping.
  • Can clients raise tickets without an account?
    First touch is an invite link: the client gets a one-time link emailed, sets a password, then signs in from the branded portal. Passwordless magic-link login is in design.
  • Does the PSA cover full ITIL ceremony (CAB, KEDB, service catalogue)?
    Not yet. We are explicit about this trade-off. CAB, KEDB and service catalogue features are on the post-GA backlog. If your operations depend on full ITIL today, HaloPSA is probably the better fit — see /compare/halopsa.
  • Can I migrate from HaloPSA, Atera or SuperOps?
    Yes, with caveats. Tickets and assets translate cleanly. Custom workflows take work. We will walk you through migration during beta onboarding.

Run your PSA on the same platform as your RMM

If you are tired of re-keying between RMM and PSA, the closed beta is the right time to look. Tell us what you are running today and what hurts most.

OpsMerge is a product of Brindleford Technologies Ltd, company number 16871436, registered in England and Wales.