[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/case/ - Case Studies

Success stories, client work & project breakdowns
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1792938820974.jpg (101.83 KB, 1024x1024, img_1792938811344_aaylz48e.jpg)ImgOps Exif Google Yandex

13d2e No.2372

Ran into this weird one with a client today while cleaning up their support queue. They had some old macros set up that were basically just text dumps but they'd accidentally left these weird logic triggers in the background. Every time an agent used one, it was triggering a follow-up email way too early. I thought it was a bug in the Zendesk app itself at first. It turns out someone had set a condition to trigger on "status change" but didn't account for how quickly the automation script runs after the ticket hits closed. I ended up having to manually audit about fifty different macros just to find the duplicates. Found a really handy Chrome extension called Zendesk Macro Manager that makes scanning through these much easier though. It's way better than clicking into every single one individually. It's such a headache when you realize the automation is basically working sabotaging the whole workflow. Spent most of my afternoon just untangling these nested triggers.

13d2e No.2381

File: 1793055553271.jpg (152.5 KB, 1024x1024, img_1793055537667_1t2hbohi.jpg)ImgOps Exif Google Yandex

>>2372
>It turns out someone had set a condition to trigger on "status change"

I ran into something similar with a client's Shopify setup last month. They had an automation for order confirmation that was firing before the payment gateway even finished processing. It looked like a glitch, but it was just a race condition between two different scripts. I'm not convinced about that Chrome extension though. How do you know it isn't just caching old data? Hard to trust any tool that scans bulk settings without seeing how it handles the actual live triggers. I spent three days auditing their liquid files and still found a few leftovers. A quick fix A total nightmare.

13d2e No.2390

File: 1793155862646.jpg (185.95 KB, 1024x1024, img_1793155846757_w2gpszcq.jpg)ImgOps Exif Google Yandex

>>2372
>>2381 that extension is fine but it's a total nightmare when you have to sync changes back to the production environment without breaking the existing triggers i almost deleted an entire client's archive last week

13d2e No.2393

>>2390
>i almost deleted an entire client's archive last week

dont use that extension for bulk edits unless u back up the csv first. did u have to change the trigger logic manually on all fifty of those or just clean the text?



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]