{"id":1129,"date":"2026-11-06T06:58:05","date_gmt":"2026-11-06T11:58:05","guid":{"rendered":"https:\/\/vight.ai\/blog\/autotask-ai\/"},"modified":"2026-11-06T06:58:05","modified_gmt":"2026-11-06T11:58:05","slug":"autotask-ai","status":"publish","type":"post","link":"https:\/\/vight.ai\/blog\/autotask-ai\/","title":{"rendered":"Autotask AI: What Cooper Copilot Reads, and the Call It Never Sees"},"content":{"rendered":"<p>A client calls at 4:40 on a Thursday because their scanner stopped sending to email. Your tech spends twenty minutes on the phone, finds the expired app password on the scan-to-email account, fixes it, and moves on to the next call. The ticket in Autotask says &quot;Scanner issue &#8211; resolved.&quot; No time entry. Two weeks later the same thing happens at the same client, and whoever picks it up clicks Smart Ticket Summary and gets back a neat paragraph about a scanner issue that was resolved.<\/p>\n<p>That&#039;s the catch with Autotask AI. The AI built into Autotask is real and useful, but it reads the ticket. If the ticket is thin, the summary is thin. This post covers what Autotask&#039;s own AI does today, what it can&#039;t see, and how to decide what to add on top of it.<\/p>\n<h2>What &quot;Autotask AI&quot; means right now<\/h2>\n<p>When people search for Autotask AI they usually mean one of two things Kaseya ships inside Autotask PSA:<\/p>\n<p><strong>Cooper Copilot.<\/strong> Autotask&#039;s help documentation describes three tools: Smart Ticket Summary, Smart Writing Assistant and Smart Resolution Summary (<a href=\"https:\/\/autotask.net\/help\/Content\/3_Features\/7_ServiceDesk\/WorkTickets\/Cooper_Copilot.htm\">Autotask help: Cooper Copilot<\/a>).<\/p>\n<ul>\n<li><strong>Smart Ticket Summary<\/strong> gives a short read of a ticket: key details, actions taken and next steps. Per Kaseya&#039;s FAQ, it draws on the description, ticket notes, time entries, issue type, sub-issue type and impacted devices.<\/li>\n<li><strong>Smart Writing Assistant<\/strong> turns a tech&#039;s shorthand in a note or time entry into client-facing text (&quot;Summarize Notes (Client-Facing)&quot;).<\/li>\n<li><strong>Smart Resolution Summary<\/strong> generates a resolution from the ticket information, notes and time entries, with an option to refine it.<\/li>\n<\/ul>\n<p><strong>Digital Specialist for Ticket Triage.<\/strong> Kaseya&#039;s AI page says Autotask assesses each ticket, classifies issue type and priority, identifies required skills and routes it to a technician (<a href=\"https:\/\/www.datto.com\/products\/autotask-psa\/ai\/\">Datto: AI-powered service desk with Autotask PSA<\/a>). The Autotask 2026.3 release added triage workflow rules on the Ticket Triage settings page and a Suggestion Preview Drawer, so the service desk can review and act on AI recommendations without leaving the triage queue (<a href=\"https:\/\/www.kaseya.com\/blog\/autotask-2026-3-release\/\">Kaseya: What&#039;s new in Autotask 2026.3<\/a>).<\/p>\n<p>Two practical details matter before you plan around either one:<\/p>\n<ol>\n<li><strong>Edition.<\/strong> Kaseya&#039;s Cooper Copilot FAQ says it is included with the Ultimate edition or equivalent bundles, and lower tiers need an upgrade (<a href=\"https:\/\/ww1.autotask.net\/help\/Content\/KB_Autotask\/CooperCopilot\/COOPERCOPILOT.htm\">Cooper Copilot FAQ<\/a>). Check your contract before you build a workflow on it.<\/li>\n<li><strong>Data handling.<\/strong> The same FAQ says your data is not used to train a model, but ticket data may be processed by third-party AI providers, and there is no dedicated AI audit log. If you have clients with strict data terms, that belongs in your client-facing AI policy.<\/li>\n<\/ol>\n<h2>The part nobody puts in the comparison: what Autotask AI reads<\/h2>\n<p>Every Cooper Copilot feature works from what is already in the ticket. Kaseya says so directly: summary quality depends on the description, notes and time entries that were entered, and a ticket with little information gets a limited summary.<\/p>\n<p>Two consequences follow, and neither shows up in the feature lists.<\/p>\n<p><strong>Internal notes are left out.<\/strong> Autotask&#039;s help page states that internal notes are not used for Ticket Summaries. Some MSPs keep the real technical detail (the registry key, the admin portal setting, the thing you don&#039;t want the client reading) in internal notes on purpose. If that&#039;s your habit, Smart Ticket Summary is summarizing the client-safe version of the ticket, not the one your next tech needs.<\/p>\n<p><strong>The phone call isn&#039;t in the ticket.<\/strong> None of Kaseya&#039;s Cooper Copilot or triage pages mention phone calls, recordings or transcripts. For an MSP service desk that&#039;s a big gap, because the call is where the diagnosis happens. The tech asks what changed, hears that the client &quot;only reset the router,&quot; walks them through the fix, and then writes one line, or nothing, because the next call is already ringing. We wrote about that leak in <a href=\"https:\/\/vight.ai\/blog\/msp-time-tracking\/\">MSP time tracking<\/a>: the time and the detail drop out at the phone, not at the timer.<\/p>\n<p>So the question for an Autotask shop isn&#039;t &quot;should we turn on Cooper Copilot?&quot; If you&#039;re on Ultimate, turn it on; it&#039;s already in your contract. The question is whether the tickets it reads are worth summarizing. AI that rewrites notes can&#039;t recover a conversation nobody wrote down.<\/p>\n<h2>Where an add-on fits, and where it doesn&#039;t<\/h2>\n<p>Autotask&#039;s AI makes the most of the record. An add-on earns its place when it adds to the record itself, from sources Autotask doesn&#039;t see. Here is how to split the job.<\/p>\n\n<figure class=\"wp-block-table\"><table><tr>\n<th>Job<\/th>\n<th>Autotask&#039;s built-in AI<\/th>\n<th>What an add-on has to bring<\/th>\n<\/tr>\n<tr>\n<td>Summarize a long ticket<\/td>\n<td>Smart Ticket Summary, from description, notes and time entries<\/td>\n<td>Nothing, unless the notes were never written<\/td>\n<\/tr>\n<tr>\n<td>Clean up a tech&#039;s shorthand<\/td>\n<td>Smart Writing Assistant<\/td>\n<td>Nothing<\/td>\n<\/tr>\n<tr>\n<td>Draft a resolution<\/td>\n<td>Smart Resolution Summary<\/td>\n<td>Nothing, if the work was logged<\/td>\n<\/tr>\n<tr>\n<td>Get the phone call into the ticket<\/td>\n<td>Not covered on Kaseya&#039;s pages<\/td>\n<td>Phone system integration, transcription, matching the call to the right ticket<\/td>\n<\/tr>\n<tr>\n<td>Log time for calls<\/td>\n<td>Not covered<\/td>\n<td>A time entry created from the call, under the right resource<\/td>\n<\/tr>\n<tr>\n<td>Triage and routing<\/td>\n<td>Digital Specialist for Ticket Triage<\/td>\n<td>Only if it covers something specific you need<\/td>\n<\/tr>\n<\/table><\/figure>\n<p>The last row is worth taking seriously. If you&#039;re already paying for Autotask&#039;s triage, a second triage tool that touches the same fields will fight it. Pick one owner per field.<\/p>\n<h2>How Vight works with Autotask<\/h2>\n<p>Vight is an add-on built for the call row of that table. It connects to Autotask through an API user (<a href=\"https:\/\/www.datto.com\/integrations\/vight-ai\/\">listed on Datto&#039;s integration directory<\/a>) and does the following, per our <a href=\"https:\/\/vight.ai\/autotask\">Autotask setup guide<\/a>:<\/p>\n<ul>\n<li><strong>Calls become ticket notes and time entries.<\/strong> Vight pulls each recorded call from your phone system (3CX, Microsoft Teams, RingCentral, Zoom Phone, Dialpad and others), transcribes it, links it to the right Autotask ticket, posts the summary as a note and creates a time entry.<\/li>\n<li><strong>Call-to-ticket matching uses what the call actually contains.<\/strong> It checks ticket numbers spoken on the call (T20261012.0001 style), the caller&#039;s phone number against the contact&#039;s recent tickets, and then the technician&#039;s recently active tickets. A call that fits none of them stays unlinked rather than landing on the wrong ticket.<\/li>\n<li><strong>Ticket agents run on Autotask tickets:<\/strong> title rewrite, categorization, duplicate merging, sentiment and P1 alerts.<\/li>\n<li><strong>A panel inside the Autotask ticket screen.<\/strong> Through Autotask&#039;s ticket insight, techs see the ticket&#039;s call history and summaries without leaving Autotask, and can ask Vight about the ticket in a chat that cites its sources.<\/li>\n<li><strong>Calls nobody answers.<\/strong> The AI voice agent can take calls after hours or as a front desk and open the ticket in Autotask with the caller&#039;s details.<\/li>\n<\/ul>\n<p>To be clear about the gaps: Vight&#039;s own ticket triage, which emails the requester for missing details, runs on ConnectWise and HaloPSA, not Autotask. On Autotask, Kaseya&#039;s Digital Specialist is the triage tool to evaluate.<\/p>\n<p>The two fit together. When Vight posts a real call summary and a time entry, Cooper Copilot has something to summarize.<\/p>\n<h2>Setup details that trip up Autotask shops<\/h2>\n<p>These come from wiring AI tools into Autotask and apply to any add-on, not just ours.<\/p>\n<p><strong>Set a default priority before anything files tickets.<\/strong> Autotask requires a priority on every ticket and the tenant-wide default, which sits on the ticket category, ships blank. Any integration that creates tickets (a voice agent, a call that opens a new ticket, an RMM alert) gets rejected until it knows which priority to use. In Vight that&#039;s the &quot;Priority for new tickets&quot; setting; other tools have their own version. If an integration &quot;can&#039;t create tickets in Autotask,&quot; check this first.<\/p>\n<p><strong>Decide whose name goes on AI notes.<\/strong> By default, notes written through the API are credited to the API user. If you want a note a tech posts from an add-on credited to that tech, Autotask needs impersonation turned on: allowed for Ticket Notes on the API user&#039;s security level, and &quot;Allow impersonation of resources with this security level&quot; on your technicians&#039; level. Notes written purely by AI should stay on the API user so nobody mistakes them for a human&#039;s work.<\/p>\n<p><strong>Count your API budget.<\/strong> Autotask allows 10,000 external API requests per hour per database, and that count covers every integration together: your RMM, documentation tool, quoting tool, billing sync and any AI add-on. Autotask starts adding half a second of latency to each request at 50% of the threshold and a full second at 75%, and suspends API access temporarily at the limit (<a href=\"https:\/\/autotask.net\/help\/DeveloperHelp\/Content\/APIs\/REST\/General_Topics\/REST_Thresholds_Limits.htm\">Autotask REST API thresholds<\/a>). When you evaluate an AI tool, ask how it behaves near that line. A tool that backfills two years of tickets at full speed can slow down every other integration you run. Vight&#039;s backfill, for example, checks the hour&#039;s usage before each batch and waits while half or more of it is used.<\/p>\n<p><strong>Use webhooks where you can.<\/strong> Polling every queue to find changes burns requests. Autotask supports webhooks for tickets and ticket notes, but an administrator must first tick &quot;Can create Webhooks&quot; on the API user&#039;s security level (under the Other section). Without it, any tool falls back to polling.<\/p>\n<p><strong>Turn on the insight per ticket category.<\/strong> Insights in the Autotask ticket screen don&#039;t show up just because the vendor provisioned one. Each ticket category has an Insights tab, and the add-on has to sit under Visible Insights. If one board shows the panel and another doesn&#039;t, that&#039;s usually why.<\/p>\n<h2>How to decide<\/h2>\n<p>Run this check on your own Autotask data before you buy anything:<\/p>\n<ol>\n<li>Pull 20 tickets from last week that started with a phone call.<\/li>\n<li>For each one, ask the tech who took it what the call covered, and compare that with the ticket.<\/li>\n<li>Count the tickets where the ticket alone would let another tech pick up the issue cold, and the ones with a time entry that matches the call.<\/li>\n<\/ol>\n<p>If most tickets pass, Cooper Copilot on clean records may be all the AI you need, and your next step is checking whether your edition includes it. If most fail, a summarizer won&#039;t fix it, because there is nothing to summarize. Fix the input first: get calls into the ticket as notes and time, then let any AI, Kaseya&#039;s or anyone else&#039;s, read a complete record.<\/p>\n<p>If you&#039;d like to see how calls land in an Autotask ticket as notes and time entries, <a href=\"https:\/\/vight.ai\/demo\">book a Vight demo<\/a> and bring a ticket from that sample.<\/p>\n<h2>Frequently asked questions<\/h2>\n<p><strong>Does Autotask have AI built in?<\/strong><br>Yes. Autotask PSA includes Cooper Copilot (Smart Ticket Summary, Smart Writing Assistant and Smart Resolution Summary) and the Digital Specialist for Ticket Triage. Kaseya&#039;s FAQ says Cooper Copilot is included with the Ultimate edition or equivalent bundles.<\/p>\n<p><strong>What data does Cooper Copilot use?<\/strong><br>The ticket description, ticket notes, time entries, issue and sub-issue type and impacted devices. Autotask&#039;s help says internal notes are not used for Ticket Summaries.<\/p>\n<p><strong>Can Autotask AI summarize phone calls?<\/strong><br>Kaseya&#039;s Cooper Copilot and triage pages don&#039;t mention phone calls, recordings or transcripts. To get call content into an Autotask ticket, you need an integration that connects your phone system to Autotask, such as <a href=\"https:\/\/vight.ai\/autotask\">Vight<\/a>.<\/p>\n<p><strong>Will an AI add-on hit Autotask&#039;s API limit?<\/strong><br>It can. Autotask allows 10,000 requests per hour per database, shared across all integrations, and adds latency from 50% of that limit. Ask any vendor how its tool paces requests and whether it uses webhooks instead of polling.<\/p>\n<p><strong>Should I use Autotask&#039;s triage or a third-party one?<\/strong><br>Pick one owner for each field. If you already use the Digital Specialist for Ticket Triage, a second tool setting the same issue type and priority fields will create conflicts. Add-ons are most useful for work Autotask&#039;s AI doesn&#039;t cover, like getting calls into tickets.<\/p>\n<p>Related reading: <a href=\"https:\/\/vight.ai\/blog\/autotask-ticketing-system\/\">Autotask ticketing system: how intake to integrations work<\/a>, <a href=\"https:\/\/vight.ai\/blog\/connectwise-ai\/\">ConnectWise AI: what it does today<\/a>, and <a href=\"https:\/\/vight.ai\/blog\/ticket-triage\/\">ticket triage for MSPs<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A client calls at 4:40 on a Thursday because their scanner stopped sending to email. Your tech spends twenty minutes on the phone, finds the expired app password on the scan-to-email account, fixes it, and moves on to the next call. The ticket in Autotask says &quot;Scanner issue &#8211; resolved.&quot; No time entry. Two weeks [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1129","post","type-post","status-publish","format-standard","hentry","category-msp-operations"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Autotask AI: What Cooper Copilot Reads, and the Call It Never Sees<\/title>\n<meta name=\"description\" content=\"What Autotask AI (Cooper Copilot and ticket triage) does today, what data it reads and misses, and how to add AI to Autotask without breaking 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\/autotask-ai\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Autotask AI: What Cooper Copilot Reads, and the Call It Never Sees\" \/>\n<meta property=\"og:description\" content=\"What Autotask AI (Cooper Copilot and ticket triage) does today, what data it reads and misses, and how to add AI to Autotask without breaking it.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/vight.ai\/blog\/autotask-ai\/\" \/>\n<meta property=\"og:site_name\" content=\"Vight Insights | AI for MSPs\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-06T11:58:05+00:00\" \/>\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=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/autotask-ai\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/autotask-ai\\\/\"},\"author\":{\"name\":\"Nathan Spitalny\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#\\\/schema\\\/person\\\/d256cba1d191205aed6403d4604a2794\"},\"headline\":\"Autotask AI: What Cooper Copilot Reads, and the Call It Never Sees\",\"datePublished\":\"2026-11-06T11:58:05+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/autotask-ai\\\/\"},\"wordCount\":2031,\"publisher\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#organization\"},\"articleSection\":[\"MSP Operations\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/autotask-ai\\\/\",\"url\":\"https:\\\/\\\/vight.ai\\\/blog\\\/autotask-ai\\\/\",\"name\":\"Autotask AI: What Cooper Copilot Reads, and the Call It Never Sees\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/#website\"},\"datePublished\":\"2026-11-06T11:58:05+00:00\",\"description\":\"What Autotask AI (Cooper Copilot and ticket triage) does today, what data it reads and misses, and how to add AI to Autotask without breaking it.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/autotask-ai\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/vight.ai\\\/blog\\\/autotask-ai\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/vight.ai\\\/blog\\\/autotask-ai\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/vight.ai\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Autotask AI: What Cooper Copilot Reads, and the Call It Never Sees\"}]},{\"@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":"Autotask AI: What Cooper Copilot Reads, and the Call It Never Sees","description":"What Autotask AI (Cooper Copilot and ticket triage) does today, what data it reads and misses, and how to add AI to Autotask without breaking 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\/autotask-ai\/","og_locale":"en_US","og_type":"article","og_title":"Autotask AI: What Cooper Copilot Reads, and the Call It Never Sees","og_description":"What Autotask AI (Cooper Copilot and ticket triage) does today, what data it reads and misses, and how to add AI to Autotask without breaking it.","og_url":"https:\/\/vight.ai\/blog\/autotask-ai\/","og_site_name":"Vight Insights | AI for MSPs","article_published_time":"2026-11-06T11:58:05+00:00","author":"Nathan Spitalny","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Nathan Spitalny","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/vight.ai\/blog\/autotask-ai\/#article","isPartOf":{"@id":"https:\/\/vight.ai\/blog\/autotask-ai\/"},"author":{"name":"Nathan Spitalny","@id":"https:\/\/vight.ai\/blog\/#\/schema\/person\/d256cba1d191205aed6403d4604a2794"},"headline":"Autotask AI: What Cooper Copilot Reads, and the Call It Never Sees","datePublished":"2026-11-06T11:58:05+00:00","mainEntityOfPage":{"@id":"https:\/\/vight.ai\/blog\/autotask-ai\/"},"wordCount":2031,"publisher":{"@id":"https:\/\/vight.ai\/blog\/#organization"},"articleSection":["MSP Operations"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/vight.ai\/blog\/autotask-ai\/","url":"https:\/\/vight.ai\/blog\/autotask-ai\/","name":"Autotask AI: What Cooper Copilot Reads, and the Call It Never Sees","isPartOf":{"@id":"https:\/\/vight.ai\/blog\/#website"},"datePublished":"2026-11-06T11:58:05+00:00","description":"What Autotask AI (Cooper Copilot and ticket triage) does today, what data it reads and misses, and how to add AI to Autotask without breaking it.","breadcrumb":{"@id":"https:\/\/vight.ai\/blog\/autotask-ai\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/vight.ai\/blog\/autotask-ai\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/vight.ai\/blog\/autotask-ai\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/vight.ai\/blog\/"},{"@type":"ListItem","position":2,"name":"Autotask AI: What Cooper Copilot Reads, and the Call It Never Sees"}]},{"@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":"","_links":{"self":[{"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/posts\/1129","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=1129"}],"version-history":[{"count":0,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/posts\/1129\/revisions"}],"wp:attachment":[{"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/media?parent=1129"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/categories?post=1129"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vight.ai\/blog\/wp-json\/wp\/v2\/tags?post=1129"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}