What to Do the Moment a Sales Call Becomes a No-Show

Snapshot

• Client: Coaching sales team booking calls through Close CRM
• Problem: No-shows sat unnoticed until a manual pipeline review, days after the missed call
• Solution: A Slack alert fired directly off the Close call disposition, the moment a call is marked missed
• Stack: Close CRM, Slack, Zapier

The Problem

A booked call is worth something right up until the moment nobody shows up for it. What happens in the hour after that determines whether it's a lost lead or a recovered one — and for a long time, nothing happened in that hour at all.

The sales team booked calls through Close. When a prospect didn't show, the setter or closer would mark the call disposition as a no-show and move on to the next thing on their list, because that's what the workflow asked of them. Nothing told anyone else that it had happened.

The only way a no-show surfaced was a manual pipeline review — someone scrolling through Close, filtering for missed dispositions, usually once every few days. By the time that review happened, the lead was cold. The moment where a same-day text or call-back would have actually worked had already passed.

Worse, no-shows didn't feel urgent in the moment they happened, because there was no visible cost to letting one sit. A missed call looked the same as a completed one in the day-to-day view — just another row. It took a dedicated review to even notice the pattern, and dedicated reviews are the first thing that gets skipped on a busy week.

Close's own advice on this is to prevent no-shows in the first place — better reminders, confirmation texts, tighter scheduling friction. That's right, as far as it goes, and worth doing. It doesn't cover what to do the moment a call is marked missed anyway, which is where every no-show that gets through prevention actually lands. Prevention and recovery are different problems, and only one of them was covered.

Recovery Windows Don't Wait for a Report

The fix wasn't a better report. A better report still requires someone to open it. The fix was making the no-show visible the instant it happened, in a place the team was already looking.

Close already knows the moment a call gets marked as a no-show — that's the disposition being set, a real event, not a status buried in a filtered view. The only thing missing was something listening for it and saying something out loud.

The Build: Disposition-Triggered Alert, Nothing Else in the Chain

Trigger on the disposition, not a schedule

The Zap fires the instant a call in Close gets marked "no-show." Not on a nightly digest, not on a weekly pipeline review — on the event itself, as it happens.

One message, enough to act on

The Slack alert carries what the team needs to move immediately: the prospect's name, the booked time, the setter or closer who owned the call, and a direct link to the Close record. No digging required before someone can send a follow-up.

Posted where the team already works

The alert lands in the team's active Slack channel, not a separate dashboard nobody opens on their own initiative. Visibility didn't depend on anyone remembering to go check something.

Deliberately narrow scope — and why that's the actual decision worth copying

This build does one thing. It doesn't try to auto-send a follow-up text, auto-reschedule, or auto-score the lead. Those are reasonable next steps, but bolting them on here would have meant guessing at a recovery sequence before anyone had data on what actually worked. Ship the alert, watch what the team does with it, automate the next step once the pattern is clear — not before. Most no-show automation ideas fail by trying to skip straight to the auto-follow-up. The alert alone did more with less risk — and it's the one part of this build most people would be tempted to skip past on the way to something fancier.

What Changed Once No-Shows Stopped Waiting for a Review

Recovery happened in the window that mattered

Same-day follow-up went from occasional to default, because the team found out about a no-show while it was still worth acting on — not three days into the lead going cold.

No-shows stopped hiding in the pipeline

A missed call used to look identical to any other row until someone specifically filtered for it. Now it announces itself the moment it happens. Nobody has to know to go looking.

The manual review stopped being necessary

The pipeline scrub that used to catch no-shows days late still exists as a backstop, but it's no longer load-bearing. The team isn't depending on it to surface anything urgent.

It surfaced a pattern nobody had visibility into before

With no-shows visible in real time instead of batched into a periodic review, the team could finally see which time slots produced the most misses. They could see which lead sources did too. That signal was there the whole time — it just never surfaced with enough immediacy for anyone to notice it.

The same principle — catch the event in real time instead of waiting for a scheduled review — is what made it possible to fix attribution surviving the setter call on a different part of this team's pipeline.

Why This Matters

The cost of a no-show isn't the missed 30 minutes. It's the days between the miss and someone noticing, during which the lead has every reason to go cold and no reason to come back on their own.

You don't need a sophisticated recovery sequence to fix that. You need the event that already exists in your CRM to say something the moment it happens, instead of waiting to be found in a report.

Ask yourself:

• How long does it take your team to find out about a no-show right now — minutes, or days?
• Does a missed call look any different from a completed one in your day-to-day view?
• What in your pipeline depends on someone remembering to go looking for a problem, instead of the problem announcing itself?