Case Study
Case Study: MSP Ticket, Alert & Onboarding Automation
We built a connected set of automations for a managed service provider: a sales pipeline that hands signed clients into the PSA, ticket triage with RMM and documentation context, RMM alert grouping with an approved runbook, Microsoft 365 starter and leaver automation and monthly license reconciliation. Technicians now start tickets with context attached, and engineers only see what needs a decision.
- Business type
- Managed service provider for small and mid-sized businesses
- Team involved
- Owner, service manager, dispatcher, technicians, account manager
- Systems connected
- PSA, RMM, documentation platform, Microsoft 365 tenants, distributor, CRM, n8n
- Delivery
- Scrum, 1-week sprints, about 8 weeks to full launch
The challenge
Where the practice started
The dispatcher read every ticket, looked up the contact and devices by hand and asked users for missing details, so the first technician touch often came after the first reply.
RMM alerts created a ticket each, including duplicates for the same device, and the team had stopped reading many of them closely.
Starters and leavers were handled from an old checklist. Leavers sometimes kept licenses for weeks, and access outside Microsoft 365 was not tracked.
License counts were reconciled against billing a few times a year, and new client details were retyped from the CRM into the PSA after signing.
Goals
What the project had to change
- Every new client lands in the PSA with clean company, contact and site data.
- Tickets reach technicians with client, device and documentation context attached.
- Duplicate and self-cleared alerts stop creating tickets, and high-risk alerts reach the on-call engineer first.
- Every leaver loses access and licenses on the leaving date, with a record of each step.
- Licenses are reconciled with billing before every invoice run.
What we built
What we built, as one connected system.
Sales pipeline and PSA hand-off
We connected web forms, assessment requests and referral emails to one CRM pipeline with follow-ups and a weekly source report, and signed deals now create the company, contacts and site in the PSA.
Service detailsTicket triage
New tickets get an internal note with the matched contact, devices, recent alerts and documentation links, plus suggested type, priority and board. Vague tickets get a short request for details; security keywords go straight to an engineer.
Service detailsRMM alert handling
Duplicate alerts are grouped, self-cleared conditions are closed with a log, a short approved runbook runs for common alerts and high-risk patterns page the on-call engineer.
Service detailsStarters and leavers
Client requests become role-based checklists; Microsoft 365 changes are staged for technician approval and leavers are locked down on the date, with every step on the ticket.
Service detailsLicense reconciliation
Before each invoice run, tenant licenses, distributor subscriptions and PSA agreement quantities are compared and exceptions listed for the account manager.
Service detailsArchitecture
How the MSP's workflows connect
- Input
- Logic and services
- AI step
- Data
- People
- Output
How it flows
- 1 The CRM, PSA and RMM feed one self-hosted n8n instance.
- 2 Five workflows classify tickets, look up documentation, stage Microsoft 365 changes and reconcile licenses.
- 3 Technicians accept suggestions and approve staged changes; engineers handle security and privileged access.
- 4 Every action is logged, and a weekly summary shows the measures the MSP agreed to track.
How it behaves
How the system behaves day to day
What clients see
- Faster, better-informed first responses from the help desk
- One form for starters and leavers and a confirmation of what was done
- Invoices that match their real license use
What the team sees
- Tickets with context attached and suggestions to accept
- One ticket per real alert problem, with history
- Staged tenant changes to approve and exception lists before billing
What the automation does
- Enriches, groups, stages and reconciles on schedule
- Runs only approved actions with scoped credentials
- Logs every step and alerts the service manager if anything fails
Edge cases and fallbacks
- A ticket mentions a possible breach
- Automation stops and the on-duty engineer is alerted with the ticket context.
- A runbook script fails
- No retries; one ticket opens with the script output.
- A leaver holds an admin role
- Removal goes to a named engineer and is never automated.
- Tenant access expires for one client
- That client is marked not reconciled and the account manager is told.
- n8n or the PSA API is down
- Tickets and alerts fall back to the normal queue, and the service manager gets an alert.
Integrations
What we connected
ConnectWise PSA
PSATickets, companies, contacts, agreements and opportunities for triage, hand-off and reconciliation.
ConnectWise PSA REST API with a developer client ID, and REST callbacks for ticket events.
NinjaOne
RMMAlerts, devices and scripted remediation.
NinjaOne Public API (OAuth 2.0) and its webhook configuration.
IT Glue
DocumentationClient documentation, configurations and role templates.
IT Glue REST API with an API key.
Microsoft 365 (Microsoft Graph)
Identity and productivityUsers, groups, licenses and session revocation for starters and leavers.
Microsoft Graph with least-privileged application permissions per tenant.
Pax8
DistributionSubscription quantities for license reconciliation.
Pax8 Partner API with OAuth client credentials.
HubSpot
CRMContacts, companies, deals and pipeline stages.
HubSpot CRM REST API, including the Pipelines API.
Microsoft Teams and Slack
Chat and alertsApprovals, alerts and the help desk chatbot channel.
Bot and incoming webhook APIs.
n8n
Automation platformRuns every workflow, self-hosted or on n8n Cloud.
Your own n8n instance; we hand over every workflow.
How we delivered it
Week by week, one workflow at a time.
Delivery timeline
Typical time to launch: about 8 weeks, then support
-
01
Discovery
Week 1
We sat with the dispatcher and technicians, mapped ticket, alert, onboarding and billing steps, agreed API scopes and wrote the first runbook.
-
02
Design and access
Week 2
Integration accounts with least-privilege scopes, priority matrix and labels, role templates, SKU mapping and the self-hosted n8n server.
-
03
Sprint 1: ticket triage
Week 3
Built triage and shadow-ran it with suggestions written to a log; demo and sign-off.
-
04
Sprint 2: RMM alerts
Week 4
Triage went live on one board. Built alert grouping and self-clear checks in decide-only mode.
-
05
Sprint 3: starters and leavers
Week 5
Alert grouping went live. Built the request form, checklists and staged Graph changes in a test tenant.
-
06
Sprint 4: license reconciliation
Week 6
Onboarding went live for one client. Built the reconciliation and ran it beside the manual billing check.
-
07
Sprint 5: CRM pipeline
Week 7
Reconciliation went live. Built the CRM pipeline and PSA hand-off, and enabled the first runbook actions.
-
08
UAT and handover
Week 8
The team ran acceptance tests on every workflow, then we switched everything on, handed over run books and trained the team.
-
09
Support
Ongoing
Weekly check-ins during stabilisation, then monthly care.
Who does what
What the team does, and what automation does.
Automation does
- Matches tickets to clients and attaches device and documentation context
- Groups duplicate alerts and closes self-cleared ones with a log
- Runs the short approved runbook and re-checks devices
- Builds starter and leaver checklists and stages tenant changes
- Reconciles licenses with distributor and PSA quantities
- Creates signed clients in the PSA from the CRM
The team does
- Accept or correct ticket suggestions
- Work persistent alert tickets
- Approve staged Microsoft 365 changes
- Approve license and billing adjustments
- Follow up leads and write proposals
Engineer or vCIO decides
- Leads every security incident and decides containment
- Approves privileged access changes
- Owns the runbook and adds new automated actions
- Agrees agreement and spend changes with clients
Compliance handled
Privacy, consent and safety, built in.
Least privilege for every integration
Each workflow uses a dedicated account with the narrowest scopes available, following joint CISA and partner guidance for MSPs.
Source: www.cisa.govLogs kept at least six months
Every automated action is written to a retained log, in line with the same guidance.
Source: www.cisa.govSecurity stays with people
NIS2 sets a 24-hour early warning for significant incidents in the EU, so security tickets bypass automation and reach an engineer at once.
Source: eur-lex.europa.euLeast-privileged Graph permissions
License changes use LicenseAssignment.ReadWrite.All rather than broad directory write access.
Source: learn.microsoft.comProcessor terms for client data
Ticket text and staff data sent to the AI provider and n8n host are covered by GDPR Article 28 processor contracts.
Source: gdpr-info.euOutcomes
What changed for the practice
- Tickets now reach technicians with the contact, devices and documentation already attached.
- Duplicate and self-cleared alerts no longer create tickets, and high-risk alerts reach the on-call engineer first.
- Leavers lose access and licenses on their leaving date, with every step recorded on the ticket.
- Licenses are reconciled with billing before every invoice run instead of a few times a year.
- New clients arrive in the PSA with clean data straight from the signed deal.
What we track
The measures the practice watches.
First technician touch
Time from ticket creation to first technician action, by board.
Suggestion acceptance
Share of triage suggestions accepted unchanged.
Alert to ticket ratio
Alerts received versus tickets created, and runbook actions that fixed the issue.
Leaver completion
Leavers fully locked down by their leaving date.
License exceptions
Exceptions found and resolved before each invoice run.
Pipeline
Leads by source, proposals sent and deals signed.
Cost estimate
What a project like this costs
-
Discovery and design
Process mapping, API scopes, runbook and the backlog for all five workflows.
$1,000 – $2,000
-
Ticket triage module
Matching, lookups, classifier, notes and routing.
$700 – $1,700
-
RMM alert module
Grouping, self-clear checks, runbook and paging.
$800 – $2,000
-
Starter and leaver module
Form, checklists, staged Graph changes and logging.
$800 – $2,000
-
License reconciliation module
Data pulls, matching and exception lists.
$500 – $1,300
-
CRM pipeline module
Source capture, stages, follow-ups and PSA hand-off.
$700 – $1,600
-
Integrations
PSA, RMM, documentation, Microsoft Graph and distributor connections.
$200 – $400
-
Testing, UAT and launch
QA, acceptance testing, launch and training.
$300 – $1,500
-
Total project estimate
$5,000 – $12,500
Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: five workflows at our fixed per-workflow range. Every MSP gets its own fixed quote after a free call.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- n8n: Free self-hosted Community edition on the MSP's server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
- PSA, RMM and documentation: Each vendor's own plan, which the MSP already pays.
- AI model usage: Pay-per-use model fees for ticket classification, usually small at MSP volumes.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
Tools we built
Free tools we built and use every day.
The Make It Flow platform
Website audits, monitoring and reports
- Email Deliverability Check FreeMX, SPF, DKIM, DMARC, MTA-STS and BIMI with ready DNS fixes
- DNS Health Check FreeNameservers, SOA, CAA, MX, TXT records and DNSSEC validation
- Website Security Scan FreeSSL, security headers, cookies and exposed file checks
- Website Monitoring Scheduled re-scans, score emails and 5-minute uptime alerts
- White-Label Reports PDF reports with your logo, name and color, and shareable links
- Bulk Website Audit Audit up to 100 URLs at once by pasting a list or uploading CSV
Free website tools for practices
Services in this case study
MSP CRM & managed-services sales pipeline
Capture every prospect from web forms, referrals, assessments and calls into one MSP CRM pipeline, with follow-ups, proposal reminders and a clean hand-off into the PSA once the agreement is signed.
From $1,000 · About 4 weeks Details
PSA ticket triage & enrichment
Classify every new ticket by type, client, contract and priority, attach device and user context from the RMM and documentation, ask the user for missing details and route it to the right board.
From $1,000 · About 4 weeks Details
RMM alert grouping & safe first response
Group duplicate RMM alerts into one ticket, close self-cleared conditions with a log, run only pre-approved remediation scripts and escalate high-risk patterns straight to the on-call engineer.
From $1,000 · About 4 weeks Details
Microsoft 365 user onboarding & offboarding
Turn starter and leaver requests into role-based checklists, prepare Microsoft 365 or Google Workspace changes for technician approval, revoke sessions and licenses on time and record every step on the ticket.
From $1,000 · About 4 to 5 weeks Details
Microsoft 365 license reconciliation & billing checks
Compare license assignments in each tenant and your distributor with active users and PSA agreement quantities every month, list unassigned seats and billing gaps, and prepare adjustments for approval.
From $1,000 · About 4 weeks Details
Engineer or vCIO decides
-
Email Security Audit: How MSPs Should Check Client DomainsEmail Deliverability · 11 min read
-
Support Ticket Triage and Release Notes: A Workflow for Software CompaniesAutomation · 10 min read
-
User Onboarding and Offboarding Workflow for MSPs and IT TeamsAutomation · 9 min read
-
Automate DMARC Report Monitoring: Free Tools and Alert RulesAutomation · 9 min read
-
DMARC Explained: Policies, Alignment and a Safe Rollout PlanEmail Deliverability · 8 min read
-
SPF PermError Too Many DNS Lookups: How to Fix the 10 LimitEmail Deliverability · 8 min read
-
What Are AI Agents? A Plain-English Guide for Small BusinessesAutomation · 10 min read
-
Website Monitoring Guide: What to Watch After Your Site LaunchesGuides · 8 min read
Free 20-minute call
Want this built for your it support & msp?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
Sources we checked
Rules and product facts on this page come from these pages, checked in November 2026. This is general information, not legal advice; confirm the rules that apply to your practice with your own adviser.
- CISA and partners: Protecting Against Cyber Threats to MSPs and their Customers (AA22-131A)
- Directive (EU) 2022/2555 (NIS2), Annex I and Article 23
- GDPR Article 28 (processors)
- EU AI Act, Article 50
- FTC: CAN-SPAM Act compliance guide
- UK PECR regulation 22
- W3C WCAG 2.2
- Microsoft Graph: user assignLicense
- Microsoft Graph: user revokeSignInSessions
- Autotask REST API home
- HaloPSA guides (API and webhooks)
- NinjaOne Public API operations
- Datto RMM API
- N-able N-central REST APIs
- IT Glue API
- Hudu API documentation
- Pax8 Partner API: subscriptions
- ConnectWise Marketplace: HubSpot ConnectWise CRM integration
- n8n pricing
- n8n self-hosting
- Google autocomplete phrasing checked for keywords (msp automation, msp crm, psa ticketing, rmm alert, msp qbr, it helpdesk chatbot, microsoft 365 offboarding)