{"id":1212,"date":"2026-11-14T01:55:55","date_gmt":"2026-11-14T06:55:55","guid":{"rendered":"https:\/\/vight.ai\/blog\/connectwise-psa\/"},"modified":"2026-11-14T01:55:56","modified_gmt":"2026-11-14T06:55:56","slug":"connectwise-psa","status":"publish","type":"post","link":"https:\/\/vight.ai\/blog\/connectwise-psa\/","title":{"rendered":"ConnectWise PSA Explained: Service Desk Workflows for MSPs"},"content":{"rendered":"<p>Month end arrives and the invoice run takes two days instead of two hours. The work happened: a password reset handled over the phone, a server rebooted at 9 pm on a hunch, a client question answered in a text thread. None of it reached a ticket, so none of it reached an invoice.<\/p>\n<p>The gap between work done and work recorded is the thing ConnectWise PSA exists to close, and it&#039;s where most MSPs lose money. Understanding the system means understanding four records (the ticket, the time entry, the agreement and the invoice) and the order in which they get written.<\/p>\n<h2>Table of Contents<\/h2>\n<ul>\n<li><a href=\"#what-connectwise-psa-does-for-an-msp\">What ConnectWise PSA Does for an MSP<\/a><ul>\n<li><a href=\"#who-touches-it-every-day\">Who touches it every day<\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"#core-service-desk-workflows-and-what-each-records\">Core Service-Desk Workflows and What Each Records<\/a><\/li>\n<li><a href=\"#how-a-ticket-moves-through-connectwise-psa\">How a Ticket Moves Through ConnectWise PSA<\/a><ul>\n<li><a href=\"#the-statuses-in-plain-english\">The statuses in plain English<\/a><\/li>\n<li><a href=\"#finding-work-that-has-stopped\">Finding work that has stopped<\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"#where-automation-extends-your-existing-psa\">Where Automation Extends Your Existing PSA<\/a><ul>\n<li><a href=\"#one-tuesday-at-a-four-tech-desk\">One Tuesday at a four-tech desk<\/a><\/li>\n<li><a href=\"#test-the-claim-against-your-own-invoice-run\">Test the claim against your own invoice run<\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"#security-rate-limits-and-permissions-to-check-first\">Security, Rate Limits and Permissions to Check First<\/a><ul>\n<li><a href=\"#throughput-is-the-first-wall\">Throughput is the first wall<\/a><\/li>\n<li><a href=\"#permissions-worth-arguing-about\">Permissions worth arguing about<\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"#plan-the-asio-based-psa-migration\">Plan the Asio-Based PSA Migration<\/a><\/li>\n<li><a href=\"#decide-which-psa-workflow-to-automate-first\">Decide Which PSA Workflow to Automate First<\/a><\/li>\n<\/ul>\n<p><a id=\"what-connectwise-psa-does-for-an-msp\"><\/a><\/p>\n<h2>What ConnectWise PSA Does for an MSP<\/h2>\n<p>ConnectWise PSA, still called ConnectWise Manage by plenty of technicians, is the professional-services-automation system that holds an MSP&#039;s tickets, technician time, agreements and invoices in one database. It&#039;s the back office where three things meet that usually live in three separate tools: intake, work and billing.<\/p>\n<p>Picture the Monday version. A client calls at 8:10 because the overnight backup job failed. A technician remotes in, re-runs the job, checks the cloud copy and has it closed by 8:40. The fix took half an hour. Recording it properly means the right company and contact, the right service board, a note a colleague could follow next time, a time entry against the right agreement, and a status that tells the account manager this client had a backup failure three weeks before a renewal call.<\/p>\n<p>That&#039;s the ledger idea. A PSA is the operations ledger of the MSP, with intake on one side, work in the middle and money on the other, and every line attributable to a client, a person and a contract. A shared hospital chart does something similar, linking reception, the clinician and the bill so nobody re-asks the patient why they came in.<\/p>\n<p>ConnectWise didn&#039;t design the product as a commercial release. The company built it to run its own IT-services business in Tampa, Florida, then sold the technology to other providers. By April 2011, more than <strong>50,000 users at nearly 4,300 MSP and value-added reseller organizations<\/strong> were running it, according to <a href=\"https:\/\/rcpmag.com\/blogs\/scott-bekker\/2011\/04\/connectwise-passes-50k-users.aspx\">RCP magazine&#039;s report on the milestone<\/a>.<\/p>\n<p>The PSA now sits inside a wider suite. <a href=\"https:\/\/www.connectwise.com\/company\/press\/releases\/connectwise-redefines-business-automation-for-technology-solution-providers\">ConnectWise&#039;s 2019 announcement of the Continuum and ITBoost acquisitions<\/a> marks the point where monitoring, NOC and help-desk services, and IT documentation joined the portfolio around it. The PSA still governs the records that decide whether a month closes cleanly: tickets, time and billing.<\/p>\n<p><a id=\"who-touches-it-every-day\"><\/a><\/p>\n<h3>Who touches it every day<\/h3>\n<p>Market share explains why so many habits and integrations are built around this one system. <a href=\"https:\/\/www.channele2e.com\/news\/big-3-rmm-psa-vendors-see-market-share-slip-canalys\">Canalys figures reported by ChannelE2E<\/a> put ConnectWise at <strong>24.3% of the combined RMM and PSA software market in Q2 2024<\/strong>, down from 26.8% in Q2 2023. Share slipped; the installed base is still enormous.<\/p>\n<ul>\n<li><strong>The owner<\/strong> reads margin by agreement and asks why one client consumes twice the hours it pays for.<\/li>\n<li><strong>The service-desk manager<\/strong> owns intake and triage, which means owning the queue, the priorities and the escalations.<\/li>\n<li><strong>The technician<\/strong> lives in the ticket record, writing notes and time as the work happens.<\/li>\n<li><strong>The account manager<\/strong> tracks client health through ticket history rather than a monthly phone call.<\/li>\n<\/ul>\n<blockquote>\n<p><strong>The real test of a PSA:<\/strong> not how many screens it has, but whether the ticket that closed on Monday produces a clean invoice on the 30th.<\/p>\n<\/blockquote>\n<p>Get any link in that chain wrong and the failure shows up weeks later as an unbilled hour, a missed SLA or a renewal conversation you weren&#039;t ready for.<\/p>\n<p><a id=\"core-service-desk-workflows-and-what-each-records\"><\/a><\/p>\n<h2>Core Service-Desk Workflows and What Each Records<\/h2>\n<p>Every service-desk workflow ends in a record somebody downstream depends on. Here&#039;s the chain, row by row.<\/p>\n<p><strong>Service-desk workflows and the records each creates<\/strong><\/p>\n\n<figure class=\"wp-block-table\"><table><tr>\n<th>Workflow<\/th>\n<th>What it records<\/th>\n<th>Who owns it<\/th>\n<th>Where it shows<\/th>\n<\/tr>\n<tr>\n<td>Ticket intake<\/td>\n<td>Ticket with company, contact, service board and priority<\/td>\n<td>Service-desk agent<\/td>\n<td>Board queue<\/td>\n<\/tr>\n<tr>\n<td>Triage and assignment<\/td>\n<td>Owner, status, approved priority and SLA state<\/td>\n<td>Service-desk manager<\/td>\n<td>Board view<\/td>\n<\/tr>\n<tr>\n<td>Technician work<\/td>\n<td>Notes, time entries and resolution<\/td>\n<td>Technician<\/td>\n<td>Ticket record<\/td>\n<\/tr>\n<tr>\n<td>Scheduling and dispatch<\/td>\n<td>Assigned resource and due date<\/td>\n<td>Dispatcher<\/td>\n<td>Schedule view<\/td>\n<\/tr>\n<tr>\n<td>Billing and invoicing<\/td>\n<td>Billable time, agreement and invoice status<\/td>\n<td>Owner or finance lead<\/td>\n<td>Invoice run<\/td>\n<\/tr>\n<tr>\n<td>Reporting<\/td>\n<td>SLA, utilization and margin by agreement<\/td>\n<td>Owner and account manager<\/td>\n<td>Reports<\/td>\n<\/tr>\n<\/table><\/figure>\n<p>Read it as a set of checkpoints rather than a feature list. Skip one and the failure surfaces later and somewhere else. Intake without a contact and a board produces a ticket nobody can route and reports that can&#039;t group it by client. Triage without an approved priority breaks the SLA clock before the work starts. Technician work with notes but no time entries produces a clean-looking ticket and an invoice that&#039;s short by two hours.<\/p>\n<p>Billing is rarely confined to the PSA either. ConnectWise&#039;s WisePay automatic payments documentation shows PSA invoices connecting to a payment gateway and to accounting software such as Xero or QuickBooks Online, with billing terms from ConnectWise Finance or Agreements scheduling the automatic payments. That&#039;s three systems agreeing on one number, and any gap in the ticket record shows up as a reconciliation problem in two of them.<\/p>\n<p>Email is still the biggest intake channel on most desks, which makes silent delivery failures look like missing tickets. <a href=\"https:\/\/molted.email\/blog\/mailbox-audit-log\">Molted Email&#039;s logged sends and blocks<\/a> show how a send log and block list let you prove whether a message ever left the building, which is the difference between &quot;the client never emailed&quot; and &quot;our filter ate it&quot;.<\/p>\n<p>The note field carries most of this evidence, and <a href=\"https:\/\/vight.ai\/blog\/ticket-notes\">what belongs in a ticket note<\/a> decides whether the record still makes sense after the technician who wrote it moves on.<\/p>\n<blockquote>\n<p><strong>Practical rule:<\/strong> the PSA is the system of record for every row. Any integration that writes into it has to match its fields and statuses, not the other way round.<\/p>\n<\/blockquote>\n<p>Pick one ticket from last week and check four things this week:<\/p>\n<ul>\n<li><strong>Company and board<\/strong> are filled in and correct, not defaulted to a holding board.  <\/li>\n<li><strong>Owner and status<\/strong> reflect where the work stands.  <\/li>\n<li><strong>Time entries<\/strong> match the work done, including the phone call that started it.  <\/li>\n<li><strong>Resolution and billing status<\/strong> agree, so a ticket marked Billed appears on the invoice run.<\/li>\n<\/ul>\n<p>A blank field is your first workflow to fix, not your last.<\/p>\n<p><a id=\"how-a-ticket-moves-through-connectwise-psa\"><\/a><\/p>\n<h2>How a Ticket Moves Through ConnectWise PSA<\/h2>\n<p>A ticket isn&#039;t a single event. It&#039;s a sequence of state changes, and each one writes a record someone downstream depends on: the dispatcher watching the queue, the technician picking up the work, the person running invoices at month end. The flow is the same whether the request arrives by phone, email or a monitoring alert.<\/p>\n<p><figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/vight.ai\/blog\/wp-content\/uploads\/2026\/11\/connectwise-psa-ticket-lifecycle.jpg\" alt=\"A flowchart showing the six-step lifecycle of a support ticket within the ConnectWise PSA software platform.\" \/><\/figure><\/p>\n<ol>\n<li><strong>Request arrives.<\/strong> A client emails or calls, and a ticket is created with the company, contact and service board filled in. Get the board wrong and every rule downstream is wrong too, because boards carry their own workflows, SLA targets and reporting context.<\/li>\n<li><strong>Priority and the clock.<\/strong> Priority comes from the board&#039;s approved list rather than a free-text guess, and the SLA timer starts on the board&#039;s own rules. That timestamp is what every SLA report will quote later.<\/li>\n<li><strong>Assignment.<\/strong> The ticket goes to a named technician or into <a href=\"https:\/\/vight.ai\/blog\/ticket-routing\">a triage queue<\/a> that a manager is responsible for clearing.<\/li>\n<li><strong>Work and records.<\/strong> Notes and time entries go on as the work happens, and the status moves forward with it. A note written at 5 pm on Friday is fiction with a timestamp. A ticket waiting on the client or a third party parks in a waiting-style status, which is a different thing from forgotten.<\/li>\n<li><strong>Resolution.<\/strong> The fix is confirmed by the client or by a check, then the ticket is marked resolved. Confirming matters: an unverified fix reopens as a new ticket and muddies your first-time-fix picture.<\/li>\n<li><strong>Money.<\/strong> Billable time flows into the invoice run and the ticket ends as billed. Duplicates get merged into the surviving ticket so the history stays in one place.<\/li>\n<\/ol>\n<p><a id=\"the-statuses-in-plain-english\"><\/a><\/p>\n<h3>The statuses in plain English<\/h3>\n<p>Status lists are configurable per board, so the exact labels vary, but most service boards cycle through a version of the states below. Each one tells a manager where the work stopped and who unblocks it.<\/p>\n\n<figure class=\"wp-block-table\"><table><tr>\n<th>Status<\/th>\n<th>Plain meaning<\/th>\n<\/tr>\n<tr>\n<td>New<\/td>\n<td>Created and not yet picked up<\/td>\n<\/tr>\n<tr>\n<td>Open<\/td>\n<td>Someone is actively working the ticket<\/td>\n<\/tr>\n<tr>\n<td>Stalled<\/td>\n<td>Paused, usually waiting on the client or a third party<\/td>\n<\/tr>\n<tr>\n<td>Resolved<\/td>\n<td>Fix confirmed and work finished<\/td>\n<\/tr>\n<tr>\n<td>Billed<\/td>\n<td>Billable time has been invoiced<\/td>\n<\/tr>\n<tr>\n<td>Combined<\/td>\n<td>Duplicate merged into another ticket<\/td>\n<\/tr>\n<\/table><\/figure>\n<p>The last two catch people out. A ticket marked Resolved but never Billed is revenue sitting in the queue, and a Combined ticket that was not a duplicate loses a client&#039;s history in the merge. Billing accuracy and SLA visibility both live or die on these labels, which is why the status field earns more attention than the subject line.<\/p>\n<p>Here&#039;s a short walkthrough of how the ticket record and the surrounding workflow fit together in practice.<\/p>\n<iframe width=\"100%\" style=\"aspect-ratio: 16 \/ 9\" src=\"https:\/\/www.youtube.com\/embed\/_Snq2or5cDg\" frameborder=\"0\" allow=\"autoplay; encrypted-media\" allowfullscreen><\/iframe>\n\n<p><a id=\"finding-work-that-has-stopped\"><\/a><\/p>\n<h3>Finding work that has stopped<\/h3>\n<p>Free-text search won&#039;t tell you which tickets are dying. Structured search will. ConnectWise&#039;s <a href=\"https:\/\/docs.connectwise.com\/ConnectWise_Automate_Documentation\/070\/250\/010?psa=1\">documented criteria for ticket records<\/a> include ticket ID, date range, ticket body, subject, owner, status, client, associated computer and requestor, with results capped at <strong>250 records<\/strong>. Those are the same fields a manager needs to group work by client, by owner or by device, so a saved search can turn &quot;who is overloaded&quot; from a hallway question into a filter.<\/p>\n<p>One caveat on boards: the board controls which workflow rules and reporting context apply, so a complete ticket filed on the wrong board is still misreported. Reassigning it fixes the rules going forward, not the history already recorded under the old board.<\/p>\n<blockquote>\n<p><strong>Run this today:<\/strong> pull every Stalled ticket older than two business days, and give each one a named owner with a next action.<\/p>\n<\/blockquote>\n<p><a id=\"where-automation-extends-your-existing-psa\"><\/a><\/p>\n<h2>Where Automation Extends Your Existing PSA<\/h2>\n<p>Automation doesn&#039;t replace the PSA. It sits on top, writes into it, and waits for a person wherever money or the record itself changes. That constraint is what keeps the ledger trustworthy.<\/p>\n<p><strong>Manual service-desk tasks, automated extensions and human checkpoints<\/strong><\/p>\n\n<figure class=\"wp-block-table\"><table><tr>\n<th>Manual task<\/th>\n<th>Automated extension<\/th>\n<th>Human checkpoint<\/th>\n<\/tr>\n<tr>\n<td>Call notes written after the call<\/td>\n<td>Transcribed call posted as a structured note and time entry<\/td>\n<td>Technician checks billable time before invoicing<\/td>\n<\/tr>\n<tr>\n<td>Missing diagnostic details on new tickets<\/td>\n<td>Automated follow-up requests details before dispatch<\/td>\n<td>Triage owner confirms priority<\/td>\n<\/tr>\n<tr>\n<td>Unanswered after-hours calls<\/td>\n<td>Voice intake records caller details and urgency and creates a ticket<\/td>\n<td>On-call technician reviews emergencies<\/td>\n<\/tr>\n<tr>\n<td>End-of-day technician notes<\/td>\n<td>Work session turned into step-by-step notes<\/td>\n<td>Technician approves notes before billing<\/td>\n<\/tr>\n<tr>\n<td>Repeat questions about past fixes<\/td>\n<td>Cited search across tickets and documentation<\/td>\n<td>Owner confirms documentation accuracy<\/td>\n<\/tr>\n<\/table><\/figure>\n<p>This is the same event-driven model ConnectWise uses elsewhere in its stack. Its <a href=\"https:\/\/docs.connectwise.com\/ScreenConnect_Documentation\/Get_started\/Administration_page\/Triggers_page\">documentation on triggers<\/a> describes rules that execute an action when a defined event occurs, and in ScreenConnect those triggers can send an email, make a web request, create a session event, or react to a login attempt. Swap the trigger for a ticket status change and the pattern carries into the service desk.<\/p>\n<p><a id=\"one-tuesday-at-a-four-tech-desk\"><\/a><\/p>\n<h3>One Tuesday at a four-tech desk<\/h3>\n<ul>\n<li><strong>6:40 pm.<\/strong> After-hours intake catches a caller whose server is down, records the name, site and urgency, creates a ticket on the after-hours board and summarises it for the on-call technician before the phone call ends.<\/li>\n<li><strong>8:15 am.<\/strong> Triage finds a ticket that says only &quot;printer broken&quot; and asks the client for the error text. The reply lands on the ticket before it moves to a ready-to-work status, so the technician starts with the symptom in hand.<\/li>\n<li><strong>Midday.<\/strong> A support call ends and the transcript is posted as a time entry with the issue, the steps taken and the resolution, against the right agreement.<\/li>\n<li><strong>Mid-afternoon.<\/strong> A technician asks which fix worked on this client&#039;s server last spring and gets an answer that cites the earlier ticket rather than a guess.<\/li>\n<\/ul>\n<p>Vight doesn&#039;t replace the PSA in any of that. It connects to your existing phone system and PSA to post call notes and time entries, sync tickets and clients, and run ticket AI apps, and <a href=\"https:\/\/vight.ai\/integrations\/connectwise\">how the ConnectWise PSA integration works<\/a> covers where the writes land.<\/p>\n<p><a id=\"test-the-claim-against-your-own-invoice-run\"><\/a><\/p>\n<h3>Test the claim against your own invoice run<\/h3>\n<p>ConnectWise reports that its PSA can reduce invoice-preparation time by <strong>50%<\/strong>, according to the company&#039;s <a href=\"https:\/\/www.connectwise.com\/platform\/psa\">PSA product page<\/a>. Take that as a vendor figure with a defined scope, not a promise about your desk. The way to test it is to time one invoice run before you automate anything, then time the same run after, with the same clients and the same agreement types.<\/p>\n<blockquote>\n<p><strong>The rule the table implies:<\/strong> automate the write, keep the approval. Anything that touches a billable hour or an invoice gets a human sign-off.<\/p>\n<\/blockquote>\n<p>If preparation time doesn&#039;t drop, the automation is probably creating records that a person then has to clean up.<\/p>\n<p><a id=\"security-rate-limits-and-permissions-to-check-first\"><\/a><\/p>\n<h2>Security, Rate Limits and Permissions to Check First<\/h2>\n<p>A connection can pass its test on a quiet Tuesday afternoon and still fall over on a Monday morning. Two things cause that: throughput and permissions, and both are invisible in a demo.<\/p>\n<p><a id=\"throughput-is-the-first-wall\"><\/a><\/p>\n<h3>Throughput is the first wall<\/h3>\n<p>Microsoft&#039;s documented ConnectWise PSA connector applies a limit of <strong>100 API calls per connection per 60-second renewal period<\/strong>, per <a href=\"https:\/\/learn.microsoft.com\/en-us\/connectors\/connectwisepsa\/\">Microsoft&#039;s ConnectWise PSA connector reference<\/a>. One intake call that looks up the caller, matches the company, resolves a contact, validates the board, creates the ticket, inserts a note and posts a time entry can chew through a large share of that allowance in a burst.<\/p>\n<p>Apply these fixes in order:<\/p>\n<ol>\n<li><strong>Cache the reference data.<\/strong> Board, status, priority and service-type maps change rarely. Load them per cycle instead of per call.<\/li>\n<li><strong>Create the ticket once, then queue the enrichment.<\/strong> Notes, time entries and links go on after the ticket exists, not in the same synchronous burst.<\/li>\n<li><strong>Back off on HTTP 429 responses<\/strong> with exponential backoff, and let the 60-second window reset before retrying.<\/li>\n<li><strong>Carry a correlation ID or idempotency key.<\/strong> If a write succeeds and the response is lost, the retry must find the original ticket instead of creating a twin.<\/li>\n<\/ol>\n<p>The duplicate ticket problem is the expensive one. It costs technician time to merge, and merged tickets have a habit of losing the original client context.<\/p>\n<p><a id=\"permissions-worth-arguing-about\"><\/a><\/p>\n<h3>Permissions worth arguing about<\/h3>\n<p>The integration account should hold a restricted security role with narrowly scoped permissions for company lookup, service-ticket creation and inquiry, and the relevant table configuration, which is the pattern described in <a href=\"https:\/\/docs.netwrix.com\/docs\/auditor\/10_8\/addon\/connectwise\/overview\">Netwrix&#039;s ConnectWise PSA integration documentation<\/a>. Never hand an automation an administrator login.<\/p>\n<p>Log which automation wrote each ticket or time entry, so an owner can trace an odd record back to its source. On our side, Vight checks member status, permissions, and call and ticket access on every MCP connector request, is SOC 2 compliant, encrypts stored data with AES-256 at rest and TLS in transit, and keeps each MSP&#039;s data separate. Returned call and ticket data is processed by the AI provider the user selects, under that provider&#039;s terms. Ask any vendor for the same detail in writing before you connect it.<\/p>\n<blockquote>\n<p><strong>The question to answer before connecting anything:<\/strong> who can read what the automation reads?<\/p>\n<\/blockquote>\n<p><a id=\"plan-the-asio-based-psa-migration\"><\/a><\/p>\n<h2>Plan the Asio-Based PSA Migration<\/h2>\n<p>Treat a move to the Asio-native PSA like moving house while the shop stays open: the goal is that Monday&#039;s dispatch board looks exactly like Friday&#039;s. ConnectWise says PSA powered by Asio began with selected partners in July 2025, with monthly enhancements through the end of 2025, in <a href=\"https:\/\/www.connectwise.com\/company\/press\/releases\/connectwise-launches-psa-powered-by-asio-and-connectwise-pro\">ConnectWise&#039;s PSA powered by Asio announcement<\/a>. A rollout on a vendor&#039;s calendar means your environment can change under you, so plan as if change is certain rather than hoping for a quiet window.<\/p>\n<p>Two risks belong in the plan from day one. Security posture shifts during any platform move, because API responses and permission models may expose data differently than the version you are leaving, so re-audit what each integration account can read before go-live. Continuity risk is quieter. Ticket context, time entries, billing rules and escalation history can all survive the migration while losing the field mappings your automation writes to.<\/p>\n<p>Inventory before you schedule anything:<\/p>\n<ol>\n<li><strong>List every integration<\/strong> and the board, status and priority mappings it writes to.<\/li>\n<li><strong>Record the API credentials and security roles<\/strong> each one uses, then rotate or narrow them.<\/li>\n<li><strong>Export billing rules and agreement terms<\/strong> so invoice runs can be compared line by line after the move.<\/li>\n<li><strong>Check each legacy integration&#039;s retirement notice.<\/strong> Connectors do get switched off on a vendor&#039;s schedule, and when that happens you lose existing field mappings and rebuild the integration from scratch.<\/li>\n<li><strong>Write a rollback procedure and test it on a non-production board<\/strong>, not in your head.<\/li>\n<\/ol>\n<p>Downtime gets the attention in planning meetings. The costlier failure is the silent kind: a ticket that loses its notes, a time entry that never reaches the agreement, an escalation event that fires into nothing. Nobody sees it until a client asks where their invoice went, and by then the record that would answer them is gone.<\/p>\n<p><a id=\"decide-which-psa-workflow-to-automate-first\"><\/a><\/p>\n<h2>Decide Which PSA Workflow to Automate First<\/h2>\n<p>The first automation is a decision, not a purchase. Set a baseline before you change anything, using measures that show economics rather than activity:<\/p>\n<ul>\n<li><strong>First-touch completeness<\/strong>, or how often a new ticket arrives with enough detail to work.<\/li>\n<li><strong>Time to triage<\/strong> from creation to a named owner.<\/li>\n<li><strong>Documentation lag<\/strong>, the gap between finishing work and recording it.<\/li>\n<li><strong>Billable-time capture<\/strong> against hours worked.<\/li>\n<li><strong>Reopen and duplicate rates<\/strong>, which tell you whether intake is creating noise.<\/li>\n<li><strong>SLA breaches and gross margin by agreement<\/strong>, the two numbers an owner manages on.<\/li>\n<\/ul>\n<p>Then choose one board and one workflow for the pilot. After-hours intake or missing time capture are the usual starting points because both have an obvious before-and-after number.<\/p>\n<p>More integration tends to increase data volume without improving decision quality unless the fields are standardized and exceptions get reviewed. ConnectWise&#039;s <a href=\"https:\/\/www.connectwise.com\/blog\/2025\/11\/announcements-it-nation-connect-global-2025\">2025 platform announcements<\/a> describe migrating hundreds of PSA pages and core services into a shared data layer, with more granular controls at entity, widget, field and content levels. That granularity creates a governance job for someone: define which records automation may create or edit, require human approval for anything billing-impacting, and keep the source evidence behind any AI-written note.<\/p>\n<p>Before you change a board, read the release notes and known issues rather than discovering them mid-pilot. ConnectWise publishes patch-update information, release notes, roadmaps and known-issue records through <a href=\"https:\/\/docs.connectwise.com\/ConnectWise_Business_Knowledge\/ConnectWise_University\/Get_Started_in_the_University\/Using_the_ConnectWise_University\">ConnectWise University<\/a>, documentation that was updated March 24, 2025.<\/p>\n<blockquote>\n<p><strong>Pilot rule:<\/strong> one board, one workflow, one exported baseline, one owner for each required field.<\/p>\n<\/blockquote>\n<p>This week, write the dispatchable-field rule for that board, name an owner for every field on it, and schedule the baseline export. Everything else can wait until you have those three things.<\/p>\n<hr>\n<p>If the record is the thing you care about, start with the workflow that loses the most: after-hours intake or missing time. Vight documents every call, answers your phones, and posts structured notes and time entries against the right ConnectWise PSA ticket, so the invoice run stops depending on what a technician remembers at 6 pm. Visit <a href=\"https:\/\/vight.ai\">Vight<\/a> to see the integration running against a live service board.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Month end arrives and the invoice run takes two days instead of two hours. The work happened: a password reset handled over the phone, a server rebooted at 9 pm on a hunch, a client question answered in a text thread. None of it reached a ticket, so none of it reached an invoice. The [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":1211,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[55,16,62,76,75],"class_list":["post-1212","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-msp-operations","tag-connectwise-psa","tag-msp-service-desk","tag-psa-automation","tag-psa-documentation","tag-ticket-workflow"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>ConnectWise PSA Explained: Service Desk Workflows for MSPs<\/title>\n<meta name=\"description\" content=\"ConnectWise PSA explained for MSPs: what it does, core service-desk workflows, and how call, ticket and documentation automation extends it.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/vight.ai\/blog\/connectwise-psa\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"ConnectWise PSA Explained: Service Desk Workflows for MSPs\" \/>\n<meta property=\"og:description\" content=\"ConnectWise PSA explained for MSPs: what it does, core service-desk workflows, and how call, ticket and documentation automation extends it.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/vight.ai\/blog\/connectwise-psa\/\" \/>\n<meta property=\"og:site_name\" content=\"Vight Insights | AI for MSPs\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-14T06:55:55+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-14T06:55:56+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/vight.ai\/blog\/wp-content\/uploads\/2026\/11\/connectwise-psa-service-desk.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1672\" \/>\n\t<meta property=\"og:image:height\" content=\"941\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Nathan Spitalny\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Nathan Spitalny\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"16 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/connectwise-psa\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/connectwise-psa\\\/\"},\"author\":{\"name\":\"Nathan Spitalny\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#\\\/schema\\\/person\\\/d256cba1d191205aed6403d4604a2794\"},\"headline\":\"ConnectWise PSA Explained: Service Desk Workflows for MSPs\",\"datePublished\":\"2026-11-14T06:55:55+00:00\",\"dateModified\":\"2026-11-14T06:55:56+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/connectwise-psa\\\/\"},\"wordCount\":3285,\"publisher\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/connectwise-psa\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/vight.ai\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/connectwise-psa-service-desk.jpg\",\"keywords\":[\"ConnectWise PSA\",\"MSP service desk\",\"PSA automation\",\"PSA documentation\",\"ticket workflow\"],\"articleSection\":[\"MSP Operations\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/connectwise-psa\\\/\",\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/connectwise-psa\\\/\",\"name\":\"ConnectWise PSA Explained: Service Desk Workflows for MSPs\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/connectwise-psa\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/connectwise-psa\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/vight.ai\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/connectwise-psa-service-desk.jpg\",\"datePublished\":\"2026-11-14T06:55:55+00:00\",\"dateModified\":\"2026-11-14T06:55:56+00:00\",\"description\":\"ConnectWise PSA explained for MSPs: what it does, core service-desk workflows, and how call, ticket and documentation automation extends it.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/connectwise-psa\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/vight.ai\\\/blog\\\/connectwise-psa\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/connectwise-psa\\\/#primaryimage\",\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/connectwise-psa-service-desk.jpg\",\"contentUrl\":\"https:\\\/\\\/vight.ai\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/connectwise-psa-service-desk.jpg\",\"width\":1672,\"height\":941},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/connectwise-psa\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/vight.ai\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"ConnectWise PSA Explained: Service Desk Workflows for MSPs\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/\",\"name\":\"Vight Insights | AI for MSPs\",\"description\":\"AI Automation, MSP Growth Strategies &amp; Smarter IT Operations\",\"publisher\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/vight.ai\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#organization\",\"name\":\"Vight Insights | AI for MSPs\",\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/vight-logo-square.png\",\"contentUrl\":\"https:\\\/\\\/vight.ai\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/vight-logo-square.png\",\"width\":800,\"height\":800,\"caption\":\"Vight Insights | AI for MSPs\"},\"image\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#\\\/schema\\\/person\\\/d256cba1d191205aed6403d4604a2794\",\"name\":\"Nathan Spitalny\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g\",\"caption\":\"Nathan Spitalny\"},\"sameAs\":[\"http:\\\/\\\/127.0.0.1\"],\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/author\\\/user\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"ConnectWise PSA Explained: Service Desk Workflows for MSPs","description":"ConnectWise PSA explained for MSPs: what it does, core service-desk workflows, and how call, ticket and documentation automation extends it.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/vight.ai\/blog\/connectwise-psa\/","og_locale":"en_US","og_type":"article","og_title":"ConnectWise PSA Explained: Service Desk Workflows for MSPs","og_description":"ConnectWise PSA explained for MSPs: what it does, core service-desk workflows, and how call, ticket and documentation automation extends it.","og_url":"https:\/\/vight.ai\/blog\/connectwise-psa\/","og_site_name":"Vight Insights | AI for MSPs","article_published_time":"2026-11-14T06:55:55+00:00","article_modified_time":"2026-11-14T06:55:56+00:00","og_image":[{"width":1672,"height":941,"url":"https:\/\/vight.ai\/blog\/wp-content\/uploads\/2026\/11\/connectwise-psa-service-desk.jpg","type":"image\/jpeg"}],"author":"Nathan Spitalny","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Nathan Spitalny","Est. reading time":"16 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/vight.ai\/blog\/connectwise-psa\/#article","isPartOf":{"@id":"https:\/\/vight.ai\/blog\/connectwise-psa\/"},"author":{"name":"Nathan Spitalny","@id":"https:\/\/vight.ai\/blog\/#\/schema\/person\/d256cba1d191205aed6403d4604a2794"},"headline":"ConnectWise PSA Explained: Service Desk Workflows for MSPs","datePublished":"2026-11-14T06:55:55+00:00","dateModified":"2026-11-14T06:55:56+00:00","mainEntityOfPage":{"@id":"https:\/\/vight.ai\/blog\/connectwise-psa\/"},"wordCount":3285,"publisher":{"@id":"https:\/\/vight.ai\/blog\/#organization"},"image":{"@id":"https:\/\/vight.ai\/blog\/connectwise-psa\/#primaryimage"},"thumbnailUrl":"https:\/\/vight.ai\/blog\/wp-content\/uploads\/2026\/11\/connectwise-psa-service-desk.jpg","keywords":["ConnectWise PSA","MSP service desk","PSA automation","PSA documentation","ticket workflow"],"articleSection":["MSP Operations"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/vight.ai\/blog\/connectwise-psa\/","url":"https:\/\/vight.ai\/blog\/connectwise-psa\/","name":"ConnectWise PSA Explained: Service Desk Workflows for MSPs","isPartOf":{"@id":"https:\/\/vight.ai\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/vight.ai\/blog\/connectwise-psa\/#primaryimage"},"image":{"@id":"https:\/\/vight.ai\/blog\/connectwise-psa\/#primaryimage"},"thumbnailUrl":"https:\/\/vight.ai\/blog\/wp-content\/uploads\/2026\/11\/connectwise-psa-service-desk.jpg","datePublished":"2026-11-14T06:55:55+00:00","dateModified":"2026-11-14T06:55:56+00:00","description":"ConnectWise PSA explained for MSPs: what it does, core service-desk workflows, and how call, ticket and documentation automation extends it.","breadcrumb":{"@id":"https:\/\/vight.ai\/blog\/connectwise-psa\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/vight.ai\/blog\/connectwise-psa\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/vight.ai\/blog\/connectwise-psa\/#primaryimage","url":"https:\/\/vight.ai\/blog\/wp-content\/uploads\/2026\/11\/connectwise-psa-service-desk.jpg","contentUrl":"https:\/\/vight.ai\/blog\/wp-content\/uploads\/2026\/11\/connectwise-psa-service-desk.jpg","width":1672,"height":941},{"@type":"BreadcrumbList","@id":"https:\/\/vight.ai\/blog\/connectwise-psa\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/vight.ai\/blog\/"},{"@type":"ListItem","position":2,"name":"ConnectWise PSA Explained: Service Desk Workflows for MSPs"}]},{"@type":"WebSite","@id":"https:\/\/vight.ai\/blog\/#website","url":"https:\/\/vight.ai\/blog\/","name":"Vight Insights | AI for MSPs","description":"AI Automation, MSP Growth Strategies &amp; Smarter IT Operations","publisher":{"@id":"https:\/\/vight.ai\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/vight.ai\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/vight.ai\/blog\/#organization","name":"Vight Insights | AI for MSPs","url":"https:\/\/vight.ai\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/vight.ai\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/vight.ai\/blog\/wp-content\/uploads\/2026\/11\/vight-logo-square.png","contentUrl":"https:\/\/vight.ai\/blog\/wp-content\/uploads\/2026\/11\/vight-logo-square.png","width":800,"height":800,"caption":"Vight Insights | AI for MSPs"},"image":{"@id":"https:\/\/vight.ai\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/vight.ai\/blog\/#\/schema\/person\/d256cba1d191205aed6403d4604a2794","name":"Nathan Spitalny","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/850f7fc4c9dff63a9b775252efe7c5b5bf78f8a543e3791de6c9775be5539970?s=96&d=mm&r=g","caption":"Nathan Spitalny"},"sameAs":["http:\/\/127.0.0.1"],"url":"https:\/\/vight.ai\/blog\/author\/user\/"}]}},"jetpack_featured_media_url":"https:\/\/vight.ai\/blog\/wp-content\/uploads\/2026\/11\/connectwise-psa-service-desk.jpg","_links":{"self":[{"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/posts\/1212","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/comments?post=1212"}],"version-history":[{"count":1,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/posts\/1212\/revisions"}],"predecessor-version":[{"id":1214,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/posts\/1212\/revisions\/1214"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/media\/1211"}],"wp:attachment":[{"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/media?parent=1212"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/categories?post=1212"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/tags?post=1212"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}