Otto's device suggestions on a ticket
On a ticket whose computer PDQ Connect manages, Otto suggests a fix in one click: a restart, an update to the app the ticket names, or a related vulnerability's fix. Nothing runs until you press it.
When a ticket's computer is one PDQ Connect manages (the ticket's own device, or a computer PDQ matches to the requester), Otto looks at what PDQ knows about it and, when something could be behind the problem, says so above the ticket's Devices panel: "LIB-204 hasn't restarted in 12 days. Restart it?" or "Google Chrome is 3 versions behind. Deploy the update?".
Otto only suggests. Nothing happens until you press the button, which does exactly what the same button in the Devices panel does, with PDQ Connect's checks: what your PDQ API key may do, and school hours for a restart. The request and its result are noted on the ticket. You see suggestions when you can act on devices (the permission to edit assets); others don't see them at all.
What Otto looks for#
| Suggestion | When | The button | | --- | --- | --- | | Restart | The computer needs a restart and hasn't restarted in 3 days or more. | Restart. During school hours it reads Restart during school hours: one computer may still be restarted then, by you, since the ticket is often why. | | Deploy update | The ticket names an app (all of its name, or all but the publisher: "Chrome" for Google Chrome) that's at least one version behind, and PDQ has one package that clearly updates it. | Deploy update | | Deploy fix | An exploited or weaponized vulnerability with a recommended fix, related to the ticket (below). | Deploy fix | | Low disk | Less than 10% of the disk is free. | None: a heads-up for the technician. |
Otto shows the three most useful at a time, fixes first. Dismiss (the X) hides one on this ticket for good; it doesn't hide it on other tickets.
What Otto sees is the last PDQ sync: a computer restarted since then still shows until the next sync. Vulnerabilities are read about once a day.
How Otto decides a vulnerability is related#
Everything above is decided from PDQ's data and the ticket's words, without AI. Only for an exploited vulnerability in an app the ticket doesn't name does Otto ask AI one question: could it be related to what the ticket describes? It sends the ticket's subject and description and each vulnerability's CVE and app, nothing else. If it isn't sure, or doesn't answer, Otto says nothing.
That question isn't asked when your account turns off AI for tickets (Admin › Tickets › General). The suggestions that need no AI still show.
Was this article helpful?
Related articles
- PDQ ConnectConnect PDQ Connect organizations to bring your Windows devices into schoolAssets with what PDQ knows about each, and deploy packages, fix vulnerabilities and reboot from a device or a ticket.
- Automate PDQ Connect with workflowsRun a workflow when PDQ Connect finds a new computer, a restart that has waited, a low disk, an app that's behind or an exploited vulnerability, and deploy, restart or open a ticket in response. Ready-made templates included.
- Ask Otto about your dataOpen Otto, start from a suggestion or a quick action, ask good questions, and turn the answer into a list, a report or an export. What it can see, what it can't do, and what admins control.
Updated October 20, 2026