customer_support · workflow

IPSY doubles ticket alerts and scales customer empathy with Zapier automation

IPSY needed an immediate way to flag allergy-related support tickets to avoid delayed responses and potential harm, and lacked a method to escalate urgent weekend issues without requiring staff to be online 24/7.

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 · Daily Zendesk keyword scan
Zapier scans Zendesk for keywords daily to surface allergy-related tickets.
Tools used
ZapierZendesk · partnerGoogle Sheet · partnerGoogle Form · partner
Outcome

IPSY now surfaces 20–30 allergy-related tickets per day, doubled proactive alerts, misses zero Reddit issues, and can deliver AI-drafted empathetic emergency responses over weekends without staff being continuously online.

Results
Time saved20–30 tickets per day
Volume100%
Source

https://zapier.com/customer-stories/ipsy

How we source this →

Grounding & classification
Source type: vendor customer story
27 fields verified against source quotes.
content generationform submissionsupport ticketmetric backednamed customerproduction runtime claimedsource backedtools describedvendor confirmedworkflow describedecommerceemployee productivityresponse time reductionthroughput increasevendor customer storycustomer supportticket triageescalation workflowmonitor detect alert