MSP Operations: Ticket Management, SLA Adherence, and IT Documentation
Operational excellence is what separates MSPs that scale profitably from those that grow headcount faster than revenue. As you add clients, your ticket volume increases, your documentation burden grows, and your SLA commitments become harder to meet without structured processes. The MSPs that achieve 75%+ gross margins at scale do so through automation, documentation discipline, and SLA reporting that demonstrates value consistently. This guide covers the operational foundations every MSP needs: ticket workflow design, SLA tracking, documentation standards, on-call management, and the monthly health report that keeps clients renewing and upselling.
READY TO TAKE ACTION?
Use the free LaunchAdvisor checklist to track every step in this guide.
Ticket Lifecycle Management in ConnectWise Manage
ConnectWise Manage (or your PSA of choice) should be the single source of truth for all client work — no email threads, no verbal commitments, no Slack messages that do not get logged to a ticket. Set up your PSA with the following ticket workflow: all inbound client contacts (email, phone, client portal) automatically create a ticket with source, priority, and client record attached; new tickets are auto-assigned to the on-call technician queue within 5 minutes; each ticket status maps to a workflow stage (New, Assigned, In Progress, Waiting for Client, Resolved, Closed); and SLA timers trigger alerts at 75% and 100% of the SLA window so technicians receive warnings before SLA breach occurs. Priority definitions must be clear, consistent, and communicated to clients: Priority 1 (business-wide outage affecting production), Priority 2 (significant impairment affecting a team or multiple users), Priority 3 (single user issue), Priority 4 (general request or non-urgent enhancement). Train clients on priority selection during onboarding — clients who habitually mark everything P1 need a direct conversation about appropriate usage.
SLA Adherence Tracking and Reporting
SLA adherence reporting serves two functions: it holds your team accountable to commitments made in client contracts, and it provides concrete evidence of your value in monthly reports and QBRs. ConnectWise Manage includes built-in SLA dashboards that show response time performance by priority, breach rates by technician, and trend data over time. Set a weekly internal SLA review: any ticket that breached response SLA requires a root cause note (was the breach due to ticket volume spike, resource unavailability, or process failure?) and a corrective action. Monthly SLA reporting to clients should show: total tickets received by priority, average first response time versus SLA target, SLA adherence percentage by priority tier (target 95%+ adherence), and resolution time averages. Clients who see consistent 97–99% SLA adherence in their monthly report do not question the value of their contract — it is quantified in writing every month.
IT Documentation with IT Glue and Hudu
IT Glue ($29/user/month) is the industry-standard documentation platform for MSPs. Its structure organizes client information into specific asset types: Configurations (every managed device with make, model, serial number, OS version, IP address, and last patch date), Passwords (AES-256 encrypted, accessible only to authorized technicians via the IT Glue vault), Contacts (client staff, vendors, and emergency contacts with phone numbers), Locations (physical addresses and network diagrams for each office), and Flexible Assets (customizable templates for domain registrars, ISP accounts, VoIP configurations, etc.). Every new client onboarding should produce a complete IT Glue documentation set within the first 30 days — a structured onboarding checklist ensures no asset type is missed. Hudu is a strong alternative at $25/user/month with similar functionality and a modern interface; many MSPs who started on IT Glue have migrated to Hudu for cost savings. Both platforms integrate with major PSAs and RMMs, enabling automatic population of configuration data from NinjaRMM discovery scans.
On-Call Rotation Management
After-hours and weekend on-call coverage is a client expectation for MSPs offering Gold or Platinum tier managed services. Managing on-call efficiently requires three components: a clear escalation path (who is first on-call, who is the backup, when does the owner get called), a compensation model that motivates participation without burning out staff, and a handoff process that ensures on-call incidents are fully documented and followed up during business hours. Use PagerDuty ($20/user/month) or OpsGenie (free for small teams, $9/user/month for advanced features) to route after-hours alerts from NinjaRMM and your PSA to the on-call technician's mobile device. Establish a clear threshold for on-call response: Priority 1 tickets (business-wide outages) trigger immediate on-call notification; Priority 2 and below can wait until the next business day unless the client contract specifically includes 24/7 response. Pay on-call technicians a fixed weekly stipend ($100–$250/week) for being available, separate from hourly pay for actual after-hours incidents.
Monthly Client Health Reports
Monthly health reports are the primary retention tool for MSPs — they make your value visible to clients who otherwise only notice your service when something goes wrong. An effective MSP monthly health report includes: Executive Summary (one-paragraph overview of the month's key activities and outcomes), Security Summary (threats blocked by SentinelOne and Huntress with specific counts — 'We blocked 147 malicious URLs and quarantined 3 potential ransomware files this month'), Patch Status (percentage of endpoints fully patched, any missing critical patches and remediation plan), Backup Health (backup job success rate, most recent verified restore date, any backup failures and resolutions), Ticket Summary (total tickets by priority, SLA adherence percentage, top 3 recurring issue categories), and Infrastructure Alerts (any hardware approaching warranty expiration, disk space warnings, or performance anomalies). ConnectWise Manage, NinjaRMM, and most PSA/RMM platforms can generate these reports automatically — configure automated delivery on the 5th of each month so clients receive them consistently without manual effort.
Renewal and Upsell Process
Client renewal should never be a surprise conversation. Structure your renewal process to begin 90 days before contract expiration: at the 90-day mark, review the client's contract for upcoming expiration and send a renewal proposal with any recommended tier upgrades or expanded services; at 60 days, host a QBR that includes the renewal conversation as a natural conclusion; at 30 days, follow up directly if the renewal proposal has not been signed. Upsell opportunities surface during QBRs, monthly reports, and incident reviews. Common MSP upsell triggers: a Huntress-detected Microsoft 365 compromise attempt becomes a pitch for advanced M365 security monitoring; a device warranty expiration report becomes a hardware refresh proposal; a business growth conversation (new employees, new office) becomes a network expansion project. Train yourself to identify every client interaction as a potential upsell signal — not to be pushy, but to proactively surface solutions before problems manifest.
Using NinjaRMM and Datto for Operational Efficiency
NinjaRMM's automation capabilities can dramatically reduce the manual ticket burden that limits MSP scale. Configure NinjaRMM to: automatically create and assign tickets for threshold-based alerts (disk usage over 85%, CPU utilization over 90% for 30+ minutes, failed backup jobs); run automated patch deployment scripts on the 2nd Tuesday of each month for Windows updates and weekly for critical software patches; deploy new software to all managed endpoints remotely without scheduling on-site visits; and run scheduled maintenance scripts (temp file cleanup, disk defragmentation, Windows update cache clearing) overnight so clients start Monday with maintained systems. Datto's automated backup monitoring creates a ticket in your PSA whenever a backup job fails — eliminating the need for manual daily backup reviews. These automations, properly configured, can save each technician 5–10 hours per week in manual monitoring and maintenance tasks — time that can be redeployed to new client onboarding or proactive client communication.
RECOMMENDED TOOLS
NinjaRMM
RMM with powerful automation, patch management, and PSA integration — reduces manual operational burden as your MSP client base scales
Datto
Backup and disaster recovery with automated monitoring — integrates with ConnectWise to create tickets on backup failures without manual review
ConnectWise
PSA with full ticket lifecycle management, SLA tracking, automated health reports, and client portal — the operational backbone for MSPs
Some links above are affiliate links. We may earn a commission if you sign up — at no extra cost to you.
FREQUENTLY ASKED QUESTIONS
How many tickets should I expect per managed endpoint per month?
Industry benchmarks suggest a well-run MSP should generate 0.5–1.0 tickets per managed device per month. If you are managing 200 devices and receiving 300+ tickets per month, your ticket volume is high — investigate whether recurring issues (unresolved root causes, outdated equipment, inadequate patch management) are driving repeat tickets. Reducing ticket volume through proactive maintenance is one of the highest-ROI operational investments an MSP can make.
Should I charge clients for after-hours emergency support?
Depends on your tier structure. Gold and Platinum tier clients should have after-hours support included in their monthly fee — emergency response is a core selling point at those pricing levels. Silver tier clients can be charged an after-hours rate ($150–$250/hour) for emergency support outside business hours, or offered an add-on for 24/7 coverage. Define the boundary clearly in your MSA so there are no disputes when a client calls at 11pm on a Friday.
What is the right documentation standard for a new client onboarding?
Complete documentation for a new client within 30 days means every device is in IT Glue as a Configuration record, all admin passwords are in the password vault, network diagrams are drafted, all key vendor contacts (ISP, VoIP, copier) are recorded, and all software licenses are catalogued. Set a 30-day onboarding checklist with clear ownership for each documentation task. Incomplete documentation is a liability — if you cannot find a client's ISP account number during an outage, every minute of fumbling is a minute against your SLA.