Every misrouted ticket in Autotask isn't just an annoyance for your dispatcher. It's a quietly unpaid invoice waiting to happen.
The connection between routing chaos and margin erosion is hiding in plain sight inside your PSA configuration, and most MSPs don't see it until they're staring at a month-end billing reconciliation that doesn't add up.
Here's the uncomfortable truth: the same ticket that went to the wrong tech, sat in the wrong queue, and got logged under the wrong work type didn't just burn your team's time. It probably never billed correctly either.
Walk through this scenario. A client submits a ticket via email. Incoming email processing drops it into a generic queue because your routing rules don't catch the keyword pattern. A Level 1 tech grabs it instead of the network engineer it should have gone to. The L1 logs two hours under "Remote Support" when the work type should have been "Onsite Support" at 1.2x the role rate. The ticket was supposed to roll up under a Time & Materials contract, but instead it hits the client's Recurring Service contract.
That's three billing errors from one routing miss.
Autotask's roles and work types aren't just labor codes. They're billing multipliers. "Onsite Support" applies 1.2x the standard technician rate. "Emergency / After-Hours Support" applies 2x. When a tech logs time under the wrong work type, you're not just misfiling a record. You're billing at the wrong rate, or potentially not billing at all if a non-billable work type gets applied by mistake.
Contracts in Autotask add another layer. A Recurring Service contract absorbs labor differently than a Block Hour or Time & Materials contract. If a ticket lands under the wrong contract, the time entry may get swallowed by prepaid hours that should be covering something else entirely. By the time anyone reviews the Approve & Post page, the context that would have flagged the error is long gone.
Billing context is baked into routing decisions. It is not something you bolt on afterward.
Most MSPs configure Service Desk automation settings during onboarding and revisit them roughly never. I've seen Autotask instances where the workflow rules were last touched three years ago, right before the company added four new service lines and two acquisition clients.
The most common Autotask PSA configuration issues I see:
The ticket settings documentation covers the full range of configurable elements: ticket categories, statuses, priorities, issue types, sources, and user-defined fields. Each one is a routing signal. When they're misconfigured or stale, your automation isn't routing tickets. It's routing noise.
The thing about workflow rules is that they fail silently. A ticket that doesn't match any rule just … lands somewhere. Usually wherever your dispatcher didn't want it.
Here's the full lifecycle of a ticket, and where money leaks at each stage:
The error at step one compounds through every subsequent step. By step five, reversing it requires manual intervention across multiple records, assuming anyone even notices.
This is why dispatch accuracy is a financial control, not just an operational preference. A routing error isn't a dispatcher problem. It's a revenue leak with a very long fuse.
These aren't theoretical. Each one addresses a specific failure mode in the chain above.
API-only ticket categories exist for integration workflows, but they're commonly misconfigured to catch tickets that don't match anything else. If tickets are landing in an API-only category when they shouldn't be, you have a routing exception that's invisible to your normal dispatch flow. Pull a report of all tickets created in API-only categories over the last 90 days and review whether those categories are doing what you intended.
Map this deliberately:
When the alignment is right, a technician logging time under the correct work type on a correctly categorized ticket produces the correct invoice line. When the alignment is wrong, every time entry is a coin flip.
The specific widgets to configure:
A weekly 15-minute review of this dashboard catches routing drift before it compounds. Without it, you're reviewing the damage at month-end instead of preventing it.
None of these fixes are one-time tasks. Ticket routing degrades continuously as your service offerings change, as you onboard new clients with unusual contract structures, and as technicians find workarounds for categories that don't fit their work.
The MSPs that keep routing clean treat it as an ongoing operational discipline, not an initial setup checkbox. That means quarterly audits of workflow rules, category lists, and work type assignments. It means reviewing the Approve & Post page not just for approval, but for pattern recognition. It means your service manager having a dashboard that shows routing health in real time, not a spreadsheet they build manually when something goes wrong.
When routing is right, billing is right. When billing is right, you get paid for the work you actually did. The configuration work to get there isn't glamorous, but the alternative is discovering your margin problem six months too late.