You’re running lead ads, leads are arriving — Ads Manager proves it — but your phone stays silent. This is one of the most-reported frustrations with Meta lead ads, and it has real causes with real fixes. Work through them in order, then decide whether the native alerts are worth relying on at all.
First, Understand What “Working” Looks Like
Calibrate expectations before debugging, because several “broken” reports are actually the system working as designed. Meta’s native new-lead alerts:
- appear inside Meta Business Suite (the bell) and as push notifications from the Business Suite mobile app;
- go only to individual accounts with sufficient Page roles and leads access;
- tell you a lead exists — they don’t contain the lead. You still open Leads Center to see the answers;
- never reach email addresses of your choosing or shared inboxes. That feature doesn’t exist natively — the full picture is in our email-notifications guide.
If your complaint is “alerts don’t reach my office inbox / my sales rep’s plain phone” — that’s not a malfunction, that’s the ceiling. Skip to the permanent fix. If alerts used to appear in the app and stopped, keep reading.
Fix 1: Confirm Role + Leads Access
The alert chain starts with permissions. You need a Page role that includes lead access — and on Business-portfolio Pages, lead permissions are granted separately by an admin. If customized lead access is enabled, even admins must be explicitly assigned. Quick test: can you open Leads Center and see the leads? If not, no notification setting will save you — fix access first. (This same cause produces the leads-not-showing-up family of problems.)
Fix 2: Check Notification Settings in Business Suite
Inside Meta Business Suite, open Settings → Notifications (both on desktop and in the mobile app — they’re tracked separately) and confirm lead-related notifications are enabled for your account. App updates and Meta’s periodic UI reshuffles have a documented habit of resetting or relocating these toggles, which is the most common “it used to work” explanation.
Fix 3: Check the Phone Itself
Obvious but routinely the answer: OS-level notification permissions for the Business Suite app, Do Not Disturb / Focus modes, battery-optimization settings that kill background apps (aggressive on many Android builds), and being signed into the wrong Facebook profile in the app. Uninstall/reinstall of the Business Suite app has fixed enough stubborn cases to be worth the two minutes.
Fix 4: Send a Test Lead, Watch the Whole Chain
Stop testing with real ad spend. Use Meta’s Lead Ads Testing Tool to fire a test submission at your actual form, then watch: does it land in Leads Center? Does the app alert fire? If the test lead arrives but no alert does, you’ve isolated a notification problem (Fixes 1–3). If alerts fire for the test but you’re still missing real leads, your problem is elsewhere — likely campaign-side.
Fix 5: If Alerts Came from an Integration, Check Its Connection
If “notifications” for you meant a Zapier email, a CRM alert, or another tool’s push — and those stopped — the near-certain cause is an expired Meta authorization. These fail silently: the integration reports itself healthy while receiving nothing. Reconnect the Facebook account inside the tool, then export the missed window from Leads Center before the 90-day expiry claims it.
The Permanent Fix
Here’s the honest conclusion after all five fixes: even fully working native alerts are a weak link in a revenue process. They’re app push notifications competing with every other notification on one person’s phone, containing no lead details, reaching no shared inboxes, with no record you can audit later — and they break again every time roles, apps, or Meta’s UI shuffle.
The businesses that never think about this problem again all make the same move: route the lead itself to the people who act on it, through a channel that’s monitored:
- Full-detail email to up to five verified addresses — owner, rep, office inbox — in seconds: Facebook Lead Ads to email.
- A plain SMS to the on-call phone with the key fields and a tap-to-call number — no app required: SMS notifications.
- A row in the shared sheet as the durable record: Google Sheets delivery.
PipeLeads does all three from one five-minute setup, keeps a per-lead delivered/retrying/failed record, and — because the weak link is always the connection — monitors your Meta authorization and warns you before it expires instead of letting your alerts die silently. Native notifications become what they should have been all along: a backup.