Missed-call alerts in Salesforce: turn every missed seller call into a callback
A seller calls one of your marketing numbers, nobody picks up, and the seller hangs up. Almost nobody leaves a voicemail: in Invoca's 2021 data, only 2% of unanswered callers did. So unless something tells a rep right away, that paid lead is gone, and the next investor on the seller's list gets the deal. This guide is for ops leads and acquisitions managers on Salesforce: what has to be in place first, how the automation works, who should get the alert, and how to know it's working.
First, your phone system has to write every call to Salesforce, missed ones included, with the direction, the result and the number that was called. Then a record-triggered Flow on that call creates a callback task for the lead's owner, or a queue if there's no owner, sends an alert to the rep and a Slack channel, and escalates to a manager if the callback isn't logged in time. Measure missed calls without a callback every day.
What has to be in place first?
A missed-call alert is only as good as the data under it. Before you build anything, check three things:
- Missed calls reach Salesforce. Most phone systems investor teams use connect to Salesforce, but some only log calls that were answered. Make a test call, let it ring out, and see whether a call record shows up on the lead, with a direction (inbound) and a result (missed or no answer).
- The call lands on the right seller. The integration should match the caller's number to an existing lead or contact. If the caller is new, something has to create a lead, or the missed call has nowhere to live.
- The number they called is captured. That's what tells you the source and market. Each marketing number should map to one campaign. See lead sources in Salesforce.
If any of those fail, fix the integration first. More on that side in dialers in Salesforce and the RingCentral integration guide.
In the org I run, calls create leads and every marketing number sends a missed-call alert to Slack. Everything below assumes the same starting point.
How the automation works
One record-triggered Flow does most of the work. In plain words:
| Step | What happens |
|---|---|
| 1. Trigger | A call activity is created where the direction is inbound and the result is missed or no answer. |
| 2. Find the seller | Use the lead or contact the call is linked to. If there isn't one, create a lead with the source and market of the number that was called. |
| 3. Check for an open callback | If the seller already has an open callback task, update it instead of creating another one. Sellers often call two or three times in a row. |
| 4. Create the callback task | Assigned to the lead's owner, due within your time limit, with the number they called in the subject. |
| 5. Alert | A notification to the owner's phone, and a message to the acquisitions channel in Slack for that market. |
| 6. Stamp the lead | Record the time of the last missed call, so it can be measured and reported. |
| 7. Escalate | A scheduled path checks again after your time limit. If the callback task is still open, it alerts the manager and can move the lead to a shared queue. |
Slack alerts from a Flow need Salesforce and Slack connected through Salesforce's Slack app, with the right permission set on the users involved. Without that, a Zap or your phone system's own Slack integration can post the message, but then you have one more thing to monitor.
When a notification turns out to be noisy, ops should be able to switch it off without editing the Flow. I build that with a configuration object, a settings record that turns individual alerts on or off.
Who should get the alert?
- The seller's owner, if the seller already has one and that person is working today.
- A shared queue and channel, if the seller is new or the owner is out. One channel per market, so people only see calls they can act on.
- The manager, only on escalation. If managers get every alert, they stop reading them.
Alert fatigue is real. If the Slack channel gets so busy that people mute it, the alert stops working. Keep the message short (seller name, number called, link to the record) and send it to as few people as can act on it.
What about calls after hours?
A callback task due at 11:40 p.m. is due before anyone sees it, and it makes your speed-to-lead numbers look worse than they are. For calls outside business hours:
- Set the callback task due at the start of the next business morning.
- Flag the lead as an overnight lead, so the morning team calls those first. The org I run uses an overnight flag for exactly this.
- Route it to the morning queue rather than a rep who may not be on shift.
- If you work markets in different time zones, use the seller's local time.
Should you send an automatic text back?
A short text after a missed call ("Sorry we missed you, we'll call you right back") can keep a seller from dialing the next investor on their list. A few cautions:
- Check your consent and opt-out handling with whoever advises you on TCPA. Not legal advice, but the stakes are real: statutory damages are $500 per violation, up to $1,500 if willful.
- Business texting in the US runs through 10DLC registration, which your texting tool handles. Make sure your number is registered before you automate anything.
- Stop the text if the seller has opted out on any record.
- The text doesn't replace the call. Keep the callback task and the clock.
What usually goes wrong
- The integration only logs answered calls, so missed calls never reach Salesforce.
- Calls from new numbers create nothing, so the sellers you most want to catch are the ones that slip.
- Three calls, three tasks. Without step 3 above, reps get a pile of tasks for one seller and start ignoring them.
- Alerts go to someone who left. See the admin handover plan for everything that keeps pointing at a former user.
- The Slack channel is muted. Ask the team. Honestly.
- Nobody tests it. It worked the day it was built, and then a picklist value changed. A test call once a week catches that. More in monitoring Salesforce automations.
How do you know it's working?
One daily report and one weekly test:
- Missed calls yesterday, by number and market, with how many got a callback within your time limit, and how many got none at all. The "none at all" column should be zero.
- Time from missed call to callback, by rep, measured from the next business morning for overnight calls.
- A test call every week to one of your numbers, left to ring out, to see the task and the alert appear.
To put a dollar figure on what missed calls cost you each month, use the missed call cost calculator. For the research on response times, see my lead response statistics.
Questions
How do I get missed-call alerts in Salesforce?
Make sure your phone system logs missed calls to Salesforce with the direction, result and number called. Then build a record-triggered Flow on those call records that creates a callback task, alerts the owner and a Slack channel, and escalates if the task isn't done in time.
Can Salesforce send missed-call alerts to Slack?
Yes. Flow has Slack actions once Salesforce and Slack are connected through Salesforce's Slack app and users have the right permission set. Teams without that connection often post alerts through a Zap or their phone system's own Slack integration.
Can Salesforce text a missed caller back automatically?
Yes, if your texting tool is connected to Salesforce, a Flow can send a short text after a missed call. Check consent and opt-out handling with whoever advises you on TCPA, make sure your number is 10DLC registered, and keep the callback task too.
What happens if the caller isn't in Salesforce yet?
Something has to create a lead from the call, with the source and market of the number they dialed. If nothing does, the missed call has no record to attach to, and the alert never fires for the sellers you most want to catch.
How do I stop duplicate callback tasks when a seller calls several times?
Before creating a task, have the Flow check whether the seller already has an open callback task. If so, update that task (and its due time) instead of creating a new one.
Why aren't missed calls showing up in Salesforce?
Usually because the phone integration only logs answered calls, the call is logged under a user without access to the record, or the caller's number doesn't match any record. Make a test call, let it ring out and check what gets created.
How fast should a missed seller call be returned?
As fast as you can. In Harvard Business Review's 2011 study, firms that contacted a lead within an hour were nearly seven times as likely to qualify it as firms that waited longer. Set a time limit with your team and escalate when it's missed.
Related guides
Sources
Checked in October 2026. Salesforce and vendor features change with each release, so check the linked page before you rely on a detail.
- Speed to lead and follow-up statistics for real estate (this site). Invoca 2021 voicemail figure and HBR 2011 response-time figures, each with its source
- Salesforce Ben: Slack actions in Salesforce Flow. Sending Slack messages from Flow, and the Slack app and permission set it needs
Want to know how many calls you're missing?
Missed-call handling is one of the first things the fixed-price CRM Revenue Audit (USD 1,500) checks, with the likely cost and a fix plan, plus up to three quick fixes done. It's for teams already on Salesforce. On another CRM? Book a free call and we'll talk about a move.
Book a free callSee the Revenue AuditOr just ask one question about your setup: email · WhatsApp · LinkedIn
