• 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?

Cameron Weston

Green Pea
Nov 11, 2026
6
5
Awards
3
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!
 
  • :light:
Reactions: Jeff Kershner
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.
 
  • Like
Reactions: Cameron Weston
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.
 
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.
This is actually extremely helpful and insightful @DealDeskCoach Thanks for sharing your wisdom/experience.
 
  • Like
Reactions: Dhruven
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.
Great! What does your ai automation pipeline look like? And can I ask what tools you are using?
 
Great! What does your ai automation pipeline look like? And can I ask what tools you are using?
Happy to share. Think of it as three layers: something that answers, something that routes, and someone who owns the outcome.

For us, that's Vapi on voice...n8n for routing and escalation... and our CRM as the source of truth. Honestly, the tools are the easy part. What made it work was deciding ownership and escalation rules before we automated anything.

What are you running on now?
 
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.
Quick response times and real-time tracking make all the difference when the stakes are high—similar to how seamless live updates on platforms like Vivatbet keep you right on top of fast-moving action without missing a beat.
Not fancy but it makes sure every missed call has a name next to it.
https://vivatbet.ie/en/line/weather
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!
That n8n/Make to Google Sheets workflow is a clean, zero-cost way to enforce accountability, though pairing it with an instant automated SMS ("Sorry we missed your call, someone from our team is calling you right back") helps lock the lead in before they dial the next dealership. Adding a quick Slack or Teams webhook alert for anything still marked "N" after 15 minutes usually gets faster manager eyes on it than email reminders alone.
 
  • Like
Reactions: Cameron Weston
Adding one thing to the auto-text idea since a few people suggested it: make sure opt-outs carry over.

1. A missed-call text goes to someone who didn’t ask to be texted. If that number opted out before, that’s a compliance risk.
2. A good practice might be to only allow the admin team to take a number off DNC. Once someone says stop, they stay opted out until they submit a new lead.

On ownership: we send leadership a monthly report by manager. Texts, calls, appointments set.

What are you using for call tracking today?
 

✨ AI Highlights

A dealer professional proposes a low-cost automation workflow using tools like Zapier, Google Sheets, and n8n to log and assign missed calls, sparking a discussion about why the logging itself is the easy part. Experienced contributors stress that clear ownership, shift-change handoffs, escalation rules to a named backup, and CRM integration are what actually prevent missed calls from becoming lost leads. One multi-store operator shared a working three-layer stack using Vapi, n8n, and a CRM with AI handling after-hours callbacks, while others flagged compliance risks around auto-texting opted-out numbers.

Replies Views 11 730 Started Last Reply