Your help desk is processing the same "how do I reset my password" ticket for the 847th time this month, while Autotask's Knowledge Base sits empty, doing nothing to help either your techs or your clients.
I've watched MSPs burn through technician hours on tickets that could be resolved in seconds with properly configured self-service. The frustrating part? Autotask already includes the tools you need. You just need to know how to use them strategically.
This article will show you how to identify which tickets are eating your time, set up automated routing for common issues, and measure the ROI of getting clients to solve problems themselves.
Find Your Top 20 "Deflectable" Ticket Types
Before you build anything, you need data. Run a ticket report for the past 90 days and sort by ticket category or title keywords. Look for patterns that scream "this should be self-service."
The usual suspects include:
-
Password resets and account lockouts
-
Email setup instructions (Outlook, mobile devices)
-
VPN connection troubleshooting
-
Software installation guides
-
Basic hardware questions (printer offline, monitor settings)
-
Network drive mapping
-
Two-factor authentication setup
Export your ticket data and create a pivot table showing ticket volume by category. Focus on categories with high volume and low complexity. These are your goldmine for deflection.
Here's the key insight most MSPs miss: don't just count tickets. Calculate the total time spent on each category. A ticket type that appears 50 times per month but takes 45 minutes each is worth more than one that appears 200 times but takes 5 minutes.
Track both first-call resolution rates and escalation patterns. If 90% of "password reset" tickets close without escalation, those are perfect Knowledge Base candidates. If only 40% close quickly, you might need better initial documentation or training.
Set Up Automated Knowledge Base Routing
Once you know your target ticket types, you need to activate and configure Autotask's Knowledge Base properly. Most MSPs skip the setup steps that make automation actually work.
Start by activating the Knowledge Base feature in your Autotask instance. This adds Knowledge Base options to your ticket interface and search functionality.
Next, create a logical category structure. Don't overthink this - you can have up to 4 levels of categories, but 2-3 levels usually work better:
-
Email & Communication
-
Outlook Setup
-
Mobile Email
-
Signature Configuration
-
Network & Access
-
VPN Connection
-
Drive Mapping
-
WiFi Troubleshooting
-
Security
-
Password Reset
-
Two-Factor Authentication
Here's where most MSPs stumble: they create articles but forget to configure the routing. Use Autotask's tagging system to automatically surface relevant articles when techs open tickets. Tag your articles with keywords that match common ticket descriptions.
For password reset articles, use tags like: "password", "reset", "locked", "account", "login". When a ticket comes in with "user locked out" in the description, these articles should appear in the Knowledge Base dropdown on the ticket page.
Leverage Global Knowledge Base Features Most MSPs Don't Know Exist
Autotask includes global Knowledge Base articles created by Datto that most MSPs completely ignore. These pre-built articles cover common BCDR scenarios and can handle tickets automatically.
The Global Knowledge Base includes articles for Datto BCDR issues that get tagged automatically when tickets are created. If you're using Datto backup solutions, these articles can resolve tickets without any technician involvement.
But here's the feature most MSPs miss entirely: external article references. You can create Knowledge Base entries that link to external resources - your own documentation sites, vendor knowledge bases, or step-by-step video tutorials. The article stub stays in Autotask, but the content lives wherever it's most useful.
This solves the maintenance problem. Instead of copying and pasting vendor documentation that goes stale, you reference the source. When the vendor updates their instructions, your Knowledge Base automatically reflects the changes.
You can also publish Knowledge Base articles to your Client Portal. This moves common questions completely outside your ticket system. Clients can search for solutions themselves, and you get deflection credit for problems that never become tickets.
Configure Client Portal Self-Service Integration
The real magic happens when you connect your Knowledge Base to client self-service. Autotask's Client Portal configuration lets you control which articles clients can see and how they interact with your Knowledge Base.
Set up service request types that guide clients through common scenarios. Instead of letting clients submit generic "computer problem" tickets, create specific request types like "Email Setup Help" or "Password Reset Request" that automatically suggest relevant articles.
Configure the priority question mapping feature. Rather than letting clients choose ticket priority directly, ask them two questions: "How urgent is this?" and "Who is impacted?" This data helps you route tickets appropriately and identify which issues need immediate attention versus Knowledge Base deflection.
Use the Client Portal's dashboard features to surface your most useful Knowledge Base articles prominently. Create a "Common Solutions" dashboard tab that shows your top deflection candidates right when clients log in.
Measure Deflection Rates and Calculate Self-Service ROI
You can't manage what you don't measure. Set up reporting to track Knowledge Base usage and deflection success rates.
Track these key metrics:
-
Article view counts (both internal and client portal)
-
Ticket volume changes for categories with Knowledge Base articles
-
Time spent per ticket in categories with good documentation
-
Client Portal login rates and self-service completion rates
Create a baseline measurement before implementing Knowledge Base deflection. Run the same ticket reports monthly to see volume changes in your target categories.
Calculate the financial impact using your standard technician hourly rate. If password reset tickets averaged 15 minutes each at $75/hour, that's $18.75 per ticket. Deflecting 100 password reset tickets per month saves $1,875 in direct labor costs.
But don't forget the indirect benefits. Techs who spend less time on routine tickets can focus on higher-value work. Clients who solve problems themselves are generally more satisfied than those who wait for ticket responses.
The most successful MSPs I work with see 25-40% deflection rates on their target ticket categories within 90 days of proper Knowledge Base implementation. The key is focusing on high-volume, low-complexity issues first, then expanding to more complex scenarios once you have the process working.
Set up automated reporting to track your progress. Autotask's reporting tools can show you Knowledge Base article usage alongside ticket volume data. Review these reports monthly and adjust your article strategy based on what's actually being used versus what you thought would be helpful.
Share via: