it_support · workflow
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.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Employee types Slack request
Employees type requests in plain language.
Tools used
ZapierSlack · partnerAzure
Outcome
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.
What failed first
A traditional scripted approach failed because employees phrased the same requests differently every time, which the script could not parse.
Results
Volume20%
Cost replaced$150,000/year
Grounding & classification
Source type: vendor customer story
25 fields verified against source quotes.
agentic workflowconversational aichat transcriptfailure mode describedmetric backednamed customerproduction runtime claimedtools describedworkflow describedsoftwarecost reductionemployee productivityresponse time reductionvendor customer storyback office opsit supportautonomous resolutioninbox to system