Create runover support ticket and update tracker row
Create runover support ticket and update tracker row
Your runover rows in the tracker lack reasons and delay customer follow-up. Coordinators can collect reasons using an auto-created ticket and a short form link, then notify customers the same day.
Workflow preview:
Zap details:
Overview
When runovers exceed their estimates, missing reason details create downstream customer confusion and manual rework for dispatch coordinators. This flow files a support ticket from each new runover row, writes the ticket ID back to your tracker, and surfaces unsent cases to ops so coordinators can gather reasons and notify customers the same day.