Palo Alto Networks saves $150,000 a year with AI Zap workflows in Slack
Hundreds of Palo Alto Networks employees needed to provision demo accounts, login codes, license resets, and access approvals for Prisma Browser, all arriving via Slack phrased differently each time. A traditional script could not handle the variation, and manual processing was not viable at enterprise scale.
A traditional scripted approach failed because employees phrased the same requests differently every time, which the script could not parse.
The AI Zap workflow serves 3,000+ internal users, eliminated one FTE saving $150,000 per year, and reduced follow-up questions by 20% via personalized bot responses.
Palo Alto Networks is now productizing the chat interface into Prisma Browser for customers.
Frequently asked questions
What did this team achieve with this AI workflow?
The AI Zap workflow serves 3,000+ internal users, eliminated one FTE saving $150,000 per year, and reduced follow-up questions by 20% via personalized bot responses.
What tools did this team use?
Zapier, Slack, Azure.
What results were reported?
annual cost savings from FTE elimination: $150,000/year; Follow-up questions reduction: 20%; Internal users served: 3,000+; User adoption growth: adoption grew from 3,000 to 5–7,000 users (source-reported, not independently verified).
What failed first in this deployment?
A traditional scripted approach failed because employees phrased the same requests differently every time, which the script could not parse.
How is this it support AI workflow structured?
Employee types Slack request → AI interprets intent → Account provisioning across systems → License assignment → Route access approvals → Personalized bot response.