Your technicians are drowning in tickets, but it's not because you're understaffed—it's because 73% of MSPs have misconfigured their Autotask routing rules, sending the wrong tickets to the wrong people at the worst possible times.
I've watched MSPs hire more staff to handle ticket volume, only to discover their real problem was routing chaos. Critical infrastructure alerts sit unassigned while junior techs get flooded with complex network issues. The symptoms look like capacity problems, but the root cause is configuration.
These aren't obvious misconfigurations either. They're subtle traps built into Autotask's flexibility—features designed to help that accidentally sabotage your workflow when combined incorrectly.
API-Only Categories: The Black Hole That Swallows Manual Assignments
API-only categories seem like a clever way to control automated ticket creation. You set them up for RMM integrations or third-party tools, hiding them from manual selection to keep things clean. But they create a hidden trap that breaks manual ticket assignment.
Here's what happens: API-only categories are invisible everywhere you manually select a category. When a tech tries to reassign a ticket that was created via API with an API-only category, they can't see or modify that category assignment. The ticket appears to accept the new assignment, but the underlying routing logic still follows the API-only category's rules.
The result is tickets that seem assigned to the right person but continue following the wrong escalation paths, SLA settings, and notification rules. Your ConnectWise RMM alerts keep going to the server team even after you manually assign them to the network specialist.
Common API-only category mistakes:
- Setting overly broad auto-assignment rules in API categories
- Forgetting to configure queue assignments for integrated tools
- Using API categories for internal tickets that need manual reassignment
- Not documenting which categories are API-only for your team
Fix this by reviewing your API-only categories and ensuring their auto-assignment rules match how you actually want those tickets routed. If you need manual control over API-created tickets, create parallel non-API categories with similar configurations.
The Co-Managed Help Desk Configuration Trap
Co-managed help desk sounds perfect for MSPs working with client IT teams. You enable it, configure some users, and suddenly tickets meant for your internal team start appearing in your client's portal. The feature that should improve collaboration instead exposes internal processes.
The trap lies in the co-managed visibility settings. When you configure co-managed help desk, every ticket category gains a "Co-managed Visibility" field. This field defaults to showing tickets to co-managing users unless explicitly restricted.
Internal tickets about server maintenance, billing issues, or strategic planning suddenly become visible to client contacts who have co-managing access. Your private notes about client relationships or technical debt appear in their view. It's not a security breach—it's working as designed, just not as you intended.
What gets exposed accidentally:
- Internal infrastructure maintenance tickets
- Billing and contract discussions
- Security vulnerability assessments
- Strategic technology planning
- Performance issues with client's own staff
The fix requires methodical category review. For each ticket category, explicitly set the co-managed visibility to match your actual business process. Categories for client-facing issues can remain visible to co-managers. Internal categories must be restricted to internal users only.
Also check your existing tickets. Tickets created before you properly configured visibility settings may still be exposed. Use Autotask's bulk edit features to correct visibility on batches of historical tickets.
AD User Matching Rules: Creating Phantom Assignments
Active Directory integration should make user management seamless. Instead, poorly configured matching rules create phantom assignments—tickets assigned to users that don't exist in Autotask or exist but never receive notifications.
The problem starts with how AD user and contact matching rules handle partial matches and similar names. Your workflow rule assigns tickets to "John Smith" based on email signature analysis, but AD sync created three potential matches: John Smith from IT, John Smith from Accounting, and J. Smith from the remote office.
Autotask picks the first match it finds, which might be the accounting person who never checks tickets. The real John Smith from IT never sees assignments meant for him. Meanwhile, your reports show tickets properly assigned, masking the routing failure.
Common AD matching failures:
- Multiple users with similar names creating assignment ambiguity
- Deactivated AD accounts that still exist in Autotask routing rules
- Email aliases pointing to the wrong Autotask user record
- Service accounts being assigned tickets meant for actual technicians
- Name changes not properly synchronized between systems
Audit your AD sync regularly. Look for duplicate names, verify that workflow rules reference active users, and test assignment rules with actual ticket creation. Consider using employee IDs or email addresses instead of display names for more reliable matching.
Service Desk Automation Settings That Destroy Efficiency
Autotask's service desk automation promises to streamline your workflow. But several "helpful" settings actually create efficiency killers when configured incorrectly.
The biggest trap is over-automating status changes. You set up rules to automatically move tickets between statuses based on time elapsed, technician actions, or client responses. This seems efficient until tickets start bouncing between statuses without human oversight.
A ticket gets automatically moved to "Waiting on Client" when you send an email, then automatically moves back to "In Progress" when they respond, then back to "Waiting" when you reply again. What should be a simple conversation becomes a status-change circus that confuses everyone and breaks SLA calculations.
Problematic automation patterns:
- Automatic status changes based on email replies
- Time-based escalation rules that fire during client-requested maintenance windows
- Template auto-population that overwrites manual priority settings
- Workflow rules that trigger on every ticket update, creating notification spam
- Checklist automation that marks items complete based on unrelated actions
The service desk automation settings page offers extensive customization, but restraint is key. Automate the repetitive work—ticket creation, initial assignment, standard notifications. Leave decision-making to humans.
Start with minimal automation and add rules gradually. Test each rule thoroughly before deploying. Monitor your ticket metrics after changes to catch unintended consequences early.
Workflow Rules: The Complexity That Kills Performance
Workflow rules can transform Autotask into a powerful automation engine. They can also create a nightmare of interdependent logic that breaks in unpredictable ways.
The problem builds gradually. You create a simple rule to assign network tickets to the network team. Then you add conditions for priority levels. Then exceptions for specific clients. Then time-based escalation. Then integration with external tools. Each change seems logical in isolation.
Eventually, you have dozens of overlapping rules that interact in ways no one fully understands. A simple ticket update triggers multiple rules simultaneously, each trying to apply different assignment logic. The ticket bounces between technicians while automated emails flood everyone's inbox.
Signs your workflow rules have become problematic:
- Tickets getting assigned and reassigned multiple times automatically
- SLA clocks starting and stopping unpredictably
- Notification storms when simple actions trigger cascading rules
- Long delays between ticket creation and initial assignment
- Rules that work perfectly in test but fail in production with real data
Fix this by documenting every workflow rule and its intended purpose. Map out rule interactions to identify conflicts. Simplify by combining related rules or adding conditions that prevent rule conflicts.
Consider rule execution order. Autotask processes rules in sequence, so later rules can override earlier ones. Make sure your most important rules run last, or add conditions that prevent overrides.
Getting Your Routing Back on Track
These configuration traps are sneaky because they develop slowly. Your routing worked fine with 50 tickets per day, but breaks down at 200. Features that solved specific problems create new problems elsewhere.
The solution requires systematic review of your entire ticket routing configuration. Start with ticket categories—both regular and API-only. Verify that auto-assignment rules match your actual team structure and skills. Test routing with sample tickets to confirm assignments work as intended.
Review your workflow rules next. Document what each rule does and why it exists. Look for overlapping logic or rules that haven't been updated as your team changed. Simplify where possible.
Finally, audit user assignments and Active Directory synchronization. Verify that workflow rules reference active users who actually handle tickets. Clean up phantom assignments and duplicate user records.
The goal isn't perfect automation—it's predictable routing that matches your team's actual workflow. Sometimes the best configuration is simpler than what you thought you needed.
See how Giant Rocketship's Service Management Orchestration fixes misconfigured triage in under 30 days, without rebuilding your entire Autotask setup from scratch. Book a Demo