A client calls the help desk, a tech fixes their Outlook profile in nine minutes, and the call ends. In Autotask there's a phone-call note on the contact saying an inbound call happened at 10:14 and lasted nine minutes. There's no ticket, no time entry, and nothing that says what was wrong or what fixed it. The phone system is "integrated with Autotask." It just isn't integrated with the part of Autotask you bill from.
That's the real answer to "how do I integrate my phone system with Autotask?": first decide what you need the integration to write, then pick the approach that writes it. There are three ways MSPs do this today, and they put very different things on the ticket.
The short answer
- CTI and call journaling (screen pop, caller lookup, a call log entry) tells you who called and when. It doesn't tell you what happened, and it rarely creates a time entry.
- An Autotask-native phone platform can put summaries and time entries on the ticket, but you're replacing your phone system to get it.
- A layer over your current phone system pulls the recorded call, links it to the right ticket, and writes the note and time entry, without changing phones.
Whichever you choose, the hard part isn't the connection. It's getting each call onto the right ticket.
Option 1: CTI and call journaling
This is what most people mean by phone integration. When the phone rings, the system looks up the number in Autotask and pops the contact or company. When the call ends, it writes a journal entry.
The catch is what that journal contains. In a June 2026 3CX community thread, an MSP running 3CX with Autotask listed the variables 3CX's CRM journaling exposes: call type, number, name, agent, duration and date/time. There's no transcript or summary in that list, and journaling fires at the end of the call, before any summary could exist. Asked whether there's an official or community Autotask integration, 3CX's staff replied, "No not that I know of," and pointed the poster toward an upcoming MCP approach instead.
The community Autotask template that does exist has a history of breaking. In an earlier 3CX thread, caller lookup and ticket creation worked, but call journaling threw a format exception that nobody in the thread resolved, and a 3CX MVP said the template "would require modifications to make it work with v18." The template notes also say it "does not offer contact creation as of yet."
CTI is still worth having. A screen pop saves the tech a lookup, and a call log is better than nothing when you're arguing about a disputed invoice. But it won't fix unlogged time, because a journal entry with a duration isn't a time entry on a ticket, and it's the time entry that reaches the invoice and your margin reports. (We walked through why short phone work is where time goes missing in MSP time tracking.)
Option 2: switch to a phone platform built around Autotask
Some phone providers build the Autotask connection into the phone system itself, with the screen pop, notes and sometimes time entries handled by the phone platform. The catch is that these are full phone platforms, not add-ons: you get the Autotask features by moving your phones to them.
If you look at one, test its ticket output on your own calls. The bigger question is whether you want to move phones at all. If your clients' numbers, your call flows and your techs' habits all live in Teams, RingCentral or 3CX, a phone migration is a project with its own risk. It makes sense if you were switching anyway. It's a lot to take on just to get better ticket notes.
Option 3: a layer over the phone system you already have
The third approach leaves the phone system alone. A separate service pulls each recorded call from the phone system, transcribes it, works out which client and ticket it belongs to, and writes into Autotask through the API.
This is how Vight works. It connects to phone systems including 3CX, Microsoft Teams, RingCentral, Zoom Phone, Dialpad and Cytracom, and to Autotask through an API user. For each call it posts a summary (the issue, what was tried, the fix) as a ticket note and logs a time entry, and it can create a ticket from a call that doesn't have one. An optional panel inside the Autotask ticket screen shows the calls linked to that ticket. The tradeoff: it works from recordings, so your phone system has to record the calls you want documented, and nothing appears on screen while the phone is still ringing.
The part every option has to get right: which ticket?
A call summary on the wrong ticket is worse than no summary, because now someone trusts it. So whatever you evaluate, ask how it decides where a call goes.
Matching on the caller's number gets you the contact, but a contact can have three open tickets, and the person calling isn't always the person on the ticket. Vight's Autotask matching, for example, works in steps: it looks for Autotask ticket numbers spoken on the call (the T20261012.0001 format), checks recent tickets for contacts with the caller's number, and then compares the call summary with the technician's recently active tickets. If nothing fits, the call stays unlinked rather than landing on a guess. Whatever tool you look at, ask the vendor to show you what it does with a call that doesn't match anything.
Autotask details that trip up phone integrations
These apply whatever tool you use:
- Use a proper API user. Autotask integrations authenticate as an API user with the API User (system) security level and an API tracking identifier. The 3CX community template, by contrast, has had trouble fitting Autotask's authentication.
- Tickets need a company and a priority. Autotask's REST API won't accept a ticket without a company, which matters when the caller's number isn't in Autotask yet. Autotask also requires a priority on every ticket, and the tenant default ships blank. If ticket creation fails silently, check that first.
- Notes post as the API user unless you allow impersonation. If you want a note credited to the tech who took the call, allow impersonation for ticket notes on the API user's security level and on your techs' security level.
- Watch the API budget. Autotask allows each database 10,000 API requests an hour, shared by every tool connected to it. A phone integration that polls heavily competes with your RMM, documentation and quoting tools.
Which should you pick?
If you only want screen pops and a call log, CTI from your current phone system is enough, provided you test the journaling on your phone system's current version. If you're replacing your phone system anyway, put the Autotask-native platforms on the shortlist and test their ticket output. If you're keeping your phones and the problem is calls that never become notes or time entries, a layer over the phone system fixes that without a migration.
Before you buy anything, it's worth measuring the gap: pull a week of calls from your phone system and count how many have no matching ticket or time entry in Autotask. Our phone-to-PSA gap check walks through it. For what AI can and can't do inside Autotask itself, see Autotask AI, and for the ticket side of Autotask, how the Autotask ticketing system works.
If you'd like to see your own calls come through as Autotask notes and time entries, book a demo.
FAQ
Does Autotask have a built-in phone system integration?
Autotask doesn't include a phone system. Phone integrations are built by phone vendors and third parties against Autotask's API.
Does 3CX integrate with Autotask?
Through a community CRM template that does caller lookup and call journaling. Its journal holds call metadata (number, agent, duration, time), not a summary or transcript, and users have reported errors with it on newer 3CX versions. In June 2026, 3CX staff said they knew of no official Autotask integration.
Can phone calls create time entries in Autotask?
Yes, if the integration writes a time entry to the ticket. A call journal or phone-call note with a duration isn't a time entry, so it won't reach billing. Ask any vendor whether it creates a time entry, on which ticket, and with what description.
What's the difference between CTI and call documentation?
CTI connects the call to the right contact while it happens (screen pop, click to dial, a call log). Call documentation records what happened on the call (the issue, the steps, the fix) on the ticket after it ends. Most MSPs need the second to fix billing and ticket quality.