Skip to content

Help Desk or PSA: What a Small MSP Actually Needs

Ben PuzzuoliFirst published 6 min read

Downtown Toronto from the air, block after block of towers down to the lakeshore

If you run a small MSP, a help desk is probably enough. That's true when you know every client, billing is simple, and you already like your remote monitoring (RMM) and accounting tools. You need a PSA when contracts, agreement billing, quotes and projects start running your week, because that's the work a PSA is built for and a help desk isn't.

Buy the bigger tool too early and you'll spend your time setting up parts you don't use. If a help desk is the right fit, our MSP help desk software page shows how Cayzu sets one up for each client.

What a PSA does that a help desk doesn't

PSA stands for professional services automation. It's the back office of a service business in one tool. As of October 2026, Gartner's Peer Insights page for the category lists what a PSA has to include: contract management, project management, ticketing, billing and invoicing, connections to other tools (at least your accounting system), resource management, time and expense tracking, and reporting on profit. ConnectWise PSA, Autotask and HaloPSA are well-known examples. Some are sold together with an RMM tool, so the same vendor watches your clients' machines and bills for the work.

A help desk covers the ticket line of that list, and usually some time tracking too. It takes in requests, puts them in one queue, holds you to response times, and tracks the time spent. It doesn't write contracts, build quotes, run projects or send invoices.

So the question is how much of that list you do today.

When a help desk is enough

A help desk is enough when most of these are true:

  • You have a handful of clients, or a few dozen, and you know each one.
  • Billing is simple: a flat monthly fee, or hours at a rate, sent from your accounting tool.
  • You already picked your RMM and your accounting tool, and you're not looking to replace them.
  • Projects are rare enough to live in a spreadsheet or a shared board.
  • What actually hurts is the inbox: requests getting lost, two techs on one job, clients asking "did anyone get my email?"

That last one is the tell. If your pain is tickets, buy a ticket tool. A PSA will fix the inbox too, but you'll pay for, and set up, a lot of back office you weren't asking for.

When a PSA is the right call

A PSA is the right call when the back office is the problem:

  • You bill against agreements: blocks of prepaid hours, different rates per contract, or retainers that roll over.
  • You send quotes often and want them to turn into projects and invoices without retyping.
  • You run real projects, like a migration or an office move, with tasks, owners and dates across several techs.
  • You want your RMM alerts to open tickets and your tickets to feed billing, all inside one vendor.

If that's your week, a help desk will feel thin, and we'd tell you so. Look at the PSA category instead.

Cayzu is a help desk, not a PSA or RMM

Cayzu is a help desk. It doesn't do contracts, quotes, projects or invoices, and it doesn't monitor your clients' machines. There are no ready-made app integrations at launch, so it won't plug into your RMM or accounting tool out of the box. On every plan, the Cayzu API lets your own tools create tickets, pull ticket history and sync customer records.

What it does do is the ticket side, for many clients at once. That's the part below.

What the help desk part has to do for an MSP

An MSP's help desk has a harder job than one company's. Every client wants to feel like your only client, and your techs still need to see all the work in one place.

A record for each client company

Every ticket should belong to a client, so you can see each client's hours and response times on their own. In Cayzu, clients are companies: the time sheet totals by company, and the SLA report shows the company on each ticket. A client's users are added to their company automatically, by their email domain, or an agent can add them by hand. Companies are on every plan.

Response targets and business hours

SLA targets are set per priority, counted in your business hours, with holidays paused. The queue flags tickets that are about to miss, and the report shows how you did against each target. The SLA and business hours page has the setup.

A client who pays for faster support can have its own SLA policy. Each policy has conditions, and a ticket gets the policy whose conditions it matches. One condition is the company, so a policy can cover just that client. SLA policies are on Pro and Enterprise. A policy can also be limited to one brand, but brands are on Enterprise.

Help desk time tracking you can bill from

Every ticket has a timer. Start it by hand, or set it to start when an agent opens a ticket, and mark each entry billable or not with a short note. The time sheet lists entries by company, agent and date. Cayzu makes the time sheet, not the invoice, so the numbers go into your accounting tool or a spreadsheet. More on the time tracking page.

A branded portal for each client

On Enterprise, each client gets their own brand. That client's users see its logo, its portal and its address, never your name. Your techs work every client from one queue, labeled by brand. The multi-brand page covers the setup.

Roles that match who does what

By default, agents see every brand's tickets. On every plan, the ticket access scope setting can limit an agent to their own groups' tickets, and custom roles on Enterprise can too. So if a client's work must be kept apart, give it its own group as well as its own brand, and turn on the access scope setting for the agents who shouldn't see it.

How to run it day to day

Here's how we'd set it up for a small shop.

  1. Create a brand for each client and forward their support address to its mailbox. Every message becomes a ticket in your one queue.
  2. Route by brand with assignment rules. If certain techs own a client, send that client's tickets to their group. If everyone works everything, use round robin.
  3. Set your business hours, holidays and targets per priority. Start loose and tighten what you beat.
  4. Turn on the automatic timer, write down once what counts as billable, and check the first week's entries against what people remember.
  5. At month end, export by brand and invoice from the time sheet.

Which plan: SLAs and time tracking are on Pro, at $49 per agent a month or $39 billed yearly. A custom domain is on every plan. A portal per client, custom roles and round robin are on Enterprise, at $79 or $65. Your clients' users don't count as agents. See the plans.

Start with a help desk if tickets are the problem

If you're not sure, the help desk is the smaller bet to test first.

If you want to see how a portal per client feels, Cayzu's 15-day free trial has every feature, and you don't need a card.

Running a help desk?

Cayzu is the simple, affordable one. Every feature free for 15 days.