
Software requests, update nags, lost phones and locked-out Macs all end up with the same few people who know Jamf. Workativ checks the device in Jamf Pro, replies in Microsoft Teams or Slack, and runs the right command once the right person agrees.
Where is Self Service, why does my Mac want an update, who can unlock it: a few people field all of it.
Lost Mode, a remote lock and an erase each fit a different device, and the choice falls to whoever is on call.
Jamf describes it for IT and Security teams, not for staff asking about their own device.
Each answer names the policy, version or app involved. Locks, erases and key requests go to a named approver first.
The reply says whether the app is already in Self Service or needs approval first
The last-updated date is shown, so the reader can judge how old the steps are

Owners are asked in Teams or Slack, and anything that erases a Mac waits for confirmation.
The nudge states the version, the deadline and where to start the update
The manager is told only about Macs still behind on the last day

"Workativ has been with us every step of the way. From our first IT support use case to HR, and soon Procurement. The platform grows with us, and so does the team behind it. It's rare to find a solution that's both powerful and genuinely easy to manage."
IT Operations Leader · NMDC Group


You pick the commands, the groups and the approvers, and every run is on record.

Choose which Mac and mobile questions the agent takes
Decide which Jamf commands it may send, and for whom
Name the approver for locks and erases
Jamf made its assistant for the admins who run the fleet. Workativ is built around the employee holding the device, and around what should happen after they ask.
What matters to IT | ||
|---|---|---|
Who it is for | IT and Security teams, in the Jamf portal | |
What it answers | Fleet questions, what a policy or Smart Group does, compliance checks, app risk | |
Acting on a device | Read-only or read-and-write skills, chosen by the admin | |
How access is decided | Admin SSO limits who can use it | |
Beyond Jamf | The Jamf environment: Jamf Pro and Jamf Protect | |
Employee self-service | Not what Jamf describes it for |
Where every asker already holds an Atlassian account and nothing leaves Jira and Confluence, Rovo may be enough, and its per-person access is a real advantage. Workativ makes sense when askers have no Atlassian account, or when an answer has to end with a request in another system. Plenty of teams would run the two together.
One request can touch Entra ID or Okta for the account, your ITSM for the ticket, and HR for who is joining or leaving.

Mac and iPhone answers from Jamf Pro, with the command sent after approval. Live in 3–5 days.
Frequently asked questions about the Jamf AI agent
A Jamf AI agent takes questions about a Mac, iPhone or iPad from the person who owns it, checks the device in Jamf Pro, and can run a command on it. Workativ's Jamf AI agent works in Microsoft Teams or Slack, acting as a Jamf helpdesk for employees. It asks the right person to approve anything that erases or locks a device, and logs every command.
No. Jamf's AI Assistant is a feature inside the Jamf portal for IT and Security teams, and it is off until an admin opts in. A Jamf AI assistant from Workativ sits in Teams or Slack and is meant for the employee holding the device. IT can keep both: Jamf's for fleet questions, Workativ's for everyone asking in chat.
How to get an app from Self Service, why their Mac keeps asking for an update, whether a new MacBook has finished setting up, and what to do about a lost iPhone. The agent looks up that device in Jamf Pro and replies in everyday language.
Run a policy so an app installs, ask the device to check in, lock a Mac, put a supervised iPhone or iPad into Lost Mode, and erase a device after approval. You switch on only the commands you want, and for which groups of users.
Through an API role and an API client in Jamf Pro, using OAuth client credentials. The role starts with read privileges for computers, inventory and users. Lock and erase privileges are added only if you want those commands in chat.
No. The privilege that reads disk encryption recovery keys is not part of the default role. A request for a key goes to IT with the employee's details, and IT hands it over through its own verified process.
Jamf's Lost Mode applies to supervised mobile devices, so Jamf Lost Mode needs that setup first. It locks the device, shows a message and a phone number on the lock screen, and records the last known location. The command stays pending until the device is online, so the agent tells the employee that. A lost Mac gets a remote lock instead.
Yes. The agent asks the approver you name before sending an erase, tells the employee what will be lost, and records who agreed. If the phone turns up first, the employee can cancel before the command goes out.
No. Jamf's AI Assistant is opt-in and runs inside Jamf. Workativ reaches Jamf Pro through its API, so it works whether or not that assistant is on. If your admins already use the assistant, the two work side by side.
A chatbot gives an answer and the conversation ends there. An agent looks at the device, chooses the command that fits, gets approval when it is needed, and sends it. Workativ's earlier Jamf chatbot page is about the question side, while this page describes the whole agent.
Three to five days for most teams. Creating the API role is quick. The work is choosing which commands to allow, who approves an erase, and testing on a few real Macs and iPhones.
Microsoft Teams and Slack, working the same way. The dashboard lists what people ask about most, which commands ran, how many approvals were granted or refused, and which Macs keep failing the same check. Logs can go to your SIEM.