• This thread is just the tip of the iceberg.The people ahead of the curve aren't Googling for answers — they're already in here, having the conversations you haven't found yet. DealerRefresh is free.Get the full picture →

Missed calls: How are you guys handling callbacks at your store?

Nov 11, 2026
2
0
Awards
1
First Name
Cameron
Hey ya'll :)

After lurking for a bit and reading some posts in other dealer forums, I've noticed that missed calls seem to be the biggest recurring complaint from dealers and marketing.
This got me thinking and I feel like logging the missed calls is the straightforward part, but the hard part is knowing WHY it was missed and who takes ownership of calling back.

I feel like an automation flow (like n8n or zapier or Make, etc.) could solve this pretty easily.

Here's a pretty simple setup that costs basically $0:
1. Have your call tracking send a missed call report every 10 minutes or something
2. Send that email into a google sheet with zapier or make (free plans work). One new row per missed call.
3. Add 2 columns: owner and called back Y/N. sales calls go to the BDC lead, service and parts calls go to that dept manager
4. Anything still "N" after 30 MIN gets a reminder to the owner.

Not fancy but it makes sure every missed call has a name next to it.

Curious how ya'll are handling this now? With AI and automation tools so accessible, I'm curious to hear about the flows or systems you guys have created to handle this. Thanks!
 
The sheet is the easy part. Where it breaks is ownership, especially on a Saturday when the BDC has gone home. Somebody needs to own every missed sales call, and the desk needs to check the list at shift changes. I'd also look at why the calls are being missed in the first place. If they're ringing to somebody who's out on a demo, fix the routing. A missed call returned quickly is still an opportunity. Wait until tomorrow and you may have lost it.
 
Vendor disclosure up front — I work at ASN Software, we build the DMS/CRM a lot of independent stores run on. Your instinct is right: logging is the easy half. Two things I'd add from watching this break in real stores:

1. The sheet becomes a second system nobody opens. The callback needs to live where the customer record already lives — in the CRM — so the next person who touches that customer sees the missed call, why it was missed, and who owns it, without opening a separate sheet.

2. The owner needs a backup. Your 30-minute reminder is good, but when the owner is out, on another call, or off that day, the row just sits at 'N.' The rule that actually closes the loop is: if the owner hasn't called back in X minutes, it escalates to a named second person automatically — nobody's inbox, a name.

One more piece worth adding: text the caller back right away, even before the callback. A quick 'sorry we missed you, what's the best time to reach you?' keeps a lot of them from calling the next store while they wait. The callback still belongs to a human — the text just buys you the time to make it.

Good setup for $0 though — the owner column is the part most stores never get to.
 
The sheet is the easy part. Ownership is where it breaks.
What works across our 10 stores is that every missed call routes to one department by the line it came in on, with a 15 minute callback SLA and a named owner per shift. If it isn't called back in 30, it escalates to the manager.
We also had AI call back after hours to qualify and book, so humans start the morning with appointments instead of a list.
 

✨ AI Highlights

A dealer forum member proposes a low-cost automation workflow using tools like Zapier or Make to handle missed call callbacks, involving call tracking reports fed into a Google Sheet with ownership and callback status columns. The thread invites discussion on how dealerships assign accountability for missed calls across BDC, sales, service, and parts. The core insight is that logging missed calls is easy, but defining ownership and follow-through is the real operational challenge automation could help solve.

Replies Views 3 151 Started Last Reply