Your Autotask workflows were supposed to eliminate manual ticket routing and reduce response times. Instead, tickets are still piling up in the wrong queues, SLAs are being missed, and your team is manually triaging everything just like before automation existed.
I've seen this scenario play out dozens of times. The promise of automated ticket routing gets MSPs excited, but the reality often falls short. The good news? Most workflow failures stem from five common configuration mistakes that are surprisingly easy to fix once you know what to look for.
The Five Workflow Configuration Mistakes That Break Everything
1. Conflicting Category Rules
Most MSPs create multiple ticket categories without realizing they can contradict each other. When a ticket matches criteria for multiple categories, Autotask picks one arbitrarily—often not the one you expect.
Example: You have a "Hardware Issue" category that routes to Level 2 and a "Priority Customer" category that routes to Level 1. When Priority Customer Inc. submits a hardware ticket, you can't predict which category wins.
Fix: Create a category hierarchy. Use API-only categories for specific integrations and reserve manual categories for user-submitted tickets. This prevents category conflicts that break routing.
2. Incomplete Field Dependencies
Workflow rules often depend on fields that aren't consistently populated. If your rule checks for "Issue Type" but 30% of tickets leave this blank, those tickets bypass your automation entirely.
Quick audit: Run a report on tickets created in the past month. Check how many have empty values for fields your workflows depend on: - Issue Type - Priority - Contact information - Custom UDFs
3. Wrong Queue Permissions
Your workflow routes tickets perfectly, but resources can't see them because queue permissions are misconfigured. The ticket sits in a queue where nobody has access.
4. Overly Complex Criteria
Some MSPs create Byzantine workflow rules with eight conditions that must all be true. These rarely work because real tickets don't fit perfect patterns.
Better approach: Start with simple rules (2-3 conditions max) that handle 80% of cases. Add complexity gradually and only when data proves it's needed.
5. No Fallback Rules
What happens when a ticket doesn't match any workflow criteria? Most MSPs don't define this, so these tickets end up unassigned in a default queue where they're forgotten.
Always create a "catch-all" workflow rule that runs last and assigns unmatched tickets to a triage queue with specific owners.
How Misconfigured Routing Rules Create Bottlenecks
Routing rules that look logical in theory often create chaos in practice. Here's why:
The VIP Problem: You create a rule that immediately escalates all tickets from VIP customers to senior technicians. Sounds good, but now your most expensive resources are handling password resets and basic questions that junior staff could resolve in minutes.
The Skills Trap: You route all "Server Issues" to your server specialist, even when they're out sick or swamped. The ticket sits unassigned while other capable technicians handle less critical work.
The False Positive Flood: Your rule flags tickets containing "down" as critical, but catches phrases like "downloading files" or "slowing down." Now your emergency queue is flooded with routine tickets, masking real emergencies.
Building Smarter Routing Logic
Instead of routing by customer tier alone, combine multiple factors: - Ticket description keywords (weighted, not absolute) - Time of day and business hours - Technician availability and current workload - Issue complexity score based on historical resolution times
The official Autotask automation documentation provides detailed configuration options for these advanced routing scenarios.
Step-by-Step Workflow Audit Process
Most MSPs assume their workflows are broken when tickets get misrouted. But sometimes the workflow is working exactly as configured—it's just configured wrong. Here's how to audit what's actually happening:
Phase 1: Data Collection (2-3 hours)
- Export ticket data from the past 30 days including: Category, Queue, Assigned Resource, Resolution Time, Customer
- Document current workflow rules with screenshots of each rule's criteria and actions
- Map actual vs. intended routing for 20-30 recent tickets
Phase 2: Pattern Analysis (1-2 hours)
Look for these red flags:
-
Tickets with multiple category changes (indicates conflicting rules)
-
High percentage of manually reassigned tickets (workflow isn't catching common scenarios)
-
Tickets sitting unassigned for >1 hour (permission or queue issues)
-
Similar tickets routing to different queues (inconsistent criteria)
Phase 3: Rule Testing (30 minutes per rule)
Create test tickets that should trigger each workflow rule:
-
Submit via email (using incoming email processing)
-
Submit via portal
-
Submit via manual creation
Document which rules fire, in what order, and what the final ticket assignment looks like.
Phase 4: Exception Handling (1 hour)
Identify tickets that bypass all rules. Common causes:
-
Missing required field values
-
Categories without associated workflow rules
-
Time-based rules that don't account for after-hours submissions
-
Integration-created tickets using different field mappings
Advanced Automation Settings Most MSPs Never Configure
These configuration options exist in every Autotask instance but rarely get attention:
Service Level Agreement Escalation
Most MSPs set up SLAs but don't configure automatic escalation when SLAs are at risk. You can automatically:
-
Reassign tickets approaching SLA breach to senior resources
-
Send alerts to managers when multiple tickets are at risk
-
Increase priority levels based on elapsed time
Smart Queue Distribution
Instead of round-robin assignment, configure rules that consider:
-
Current workload (number of open tickets per resource)
-
Estimated completion time based on ticket complexity
-
Resource specialization scores for different issue types
-
Geographic proximity for on-site requirements
Conditional Field Requirements
Make certain fields required based on ticket category or priority. For example:
-
Critical tickets must have customer contact phone number
-
Hardware issues must specify device serial number
-
Security incidents must have impact assessment
Automated Status Progression
Set up rules that automatically advance ticket status when certain conditions are met:
-
Move to "In Progress" when first time entry is added
-
Change to "Waiting Customer" when specific note templates are used
-
Close tickets automatically after customer confirms resolution
Integration-Specific Categories
Use API-only categories for tickets created by monitoring tools or other integrations. This prevents these automated tickets from cluttering your manual workflow categories while still applying appropriate routing rules.
Fixing What's Actually Broken vs. What Looks Broken
Sometimes workflows appear broken when the real issue is elsewhere:
Problem: Tickets are getting assigned correctly but taking too long to resolve.
Real Issue: Resource scheduling problems, not workflow routing.
Problem: VIP customers complain about slow response times.
Real Issue: The workflow routes correctly, but assigned technicians don't monitor their queues frequently enough.
Problem: Tickets are going to the wrong queue.
Real Issue: The queue is correct, but resources don't understand their role boundaries.
Before rebuilding your entire workflow system, verify that routing is actually the bottleneck. Often, the workflows are doing exactly what they're configured to do—the configuration just doesn't match your actual business processes.
Making Automation Actually Work
Successful workflow automation requires ongoing maintenance, not just initial setup. Schedule monthly reviews to:
-
Analyze tickets that required manual reassignment
-
Update workflow criteria based on new service offerings
-
Adjust queue assignments as team responsibilities evolve
-
Test workflows with realistic scenarios, not just perfect examples
The goal isn't to automate everything, it's to automate the routine decisions so your team can focus on complex problem-solving. Start with rules that handle your most common ticket types, then gradually expand coverage based on real data about where manual intervention is still needed.
Share via: