FlowVeo
Back to portfolio

Unsatisfied Completion Rescue: Scheduled Airtable Scan → Linked Callback Ticket + Client SMS

Followup
Make.comAirtableQuo

Problem: Completions that came back unsatisfied needed a human to notice, create a callback service ticket, link it to the original, notify the client, and open a tracking opportunity, which often lagged by days and let callbacks slip entirely.

Solution: Built a Make.com scenario (16. Callback Generation) that runs every 5 minutes and searches Airtable for unsatisfied Completion Records. For each hit, a Has Linked Service Ticket filter decides whether to Skip (already handled) or continue to Get Service Ticket, then branches on Ticket Found: unmatched records route to Skip while matched records flow into Get Client, Get Vendor, Create Callback Service Ticket, Link Callback Ticket back to the original with an idempotency update, parse the client Phone number, send SMS to Client via Quo, create a Log Communication record, create a $0 Opportunity Ticket for tracking, and run a final Update Callback Ticket → Dispatched status write.

Result: Every unsatisfied completion now spawns a linked callback ticket, a tracking opportunity, and a client SMS automatically within 5 minutes, closing the gap where callbacks previously slipped through.