The leads are there. Nobody saw them.
You run a lead ad on Facebook and Instagram. The campaign dashboard shows a healthy number of submissions. Then, a week or two in, someone opens Meta Business Suite, downloads the leads as a CSV and discovers that most of them were never phoned. By the time they are, half do not remember filling anything in.
Sometimes there is a zap in place that sends leads to a Google Sheet. It worked for a while, then the page token expired, and nobody noticed the sheet had stopped growing.
Why these leads slip through
Lead forms are convenient for the person filling them in precisely because they never leave the app. That same convenience means the lead never touches your website, your inbox or your CRM unless you build the bridge.
- Leads are stored in Meta's Leads Center, which nobody on the sales side checks daily.
- The integration that was set up relies on one person's login, and it breaks when their permissions change.
- Leads are sent to a shared inbox or sheet with no owner, so everyone assumes someone else called.
- Form fields are minimal, so leads arrive without enough context for a salesperson to prioritise.
- Pre-filled details mean some people submit by accident, and the team loses faith in the whole channel.
What an unworked lead costs
You have paid for the lead whether or not anyone calls. Interest in a lead form drops fast, because the person tapped a button between other things on their phone. A lead contacted the same day is a very different conversation from one contacted next week.
There is a second cost: when follow-up is patchy, the channel looks like it does not work, and the budget moves elsewhere, even though the problem was never the ads.
| Where the lead sits | Who notices | Likely outcome |
|---|---|---|
| Meta Leads Center only | Nobody, until a CSV export | Contacted late or never |
| Shared Google Sheet | Whoever happens to look | Duplicated or missed calls |
| CRM with an owner and a task | The owner, straight away | Contacted while interest is fresh |
How we fix the routing
- We connect to Meta's lead retrieval through a webhook on a system user token that belongs to the business, not a person, so it does not break when someone leaves.
- Each new lead is created in your CRM (HubSpot, Pipedrive, Salesforce, Zoho or a custom system) with the campaign, ad set, ad and form it came from.
- An assignment rule gives the lead to a named person based on territory, service or a simple rotation, and creates a call task.
- The lead gets an immediate text or email through Twilio or your email platform, confirming you have their request and what happens next.
- If the task is not marked as contacted after a set period, the owner is reminded, then a manager is alerted. You choose the periods.
- Duplicate detection merges a lead with an existing contact rather than creating a second record.
- A daily health check confirms leads are still arriving and alerts someone if the connection goes quiet.
We also review the form itself. Adding one qualifying question or switching to the higher-intent form type can cut accidental submissions, which the team will thank you for.
What your team sees afterwards
A salesperson gets a notification on their phone with the lead's name, what they asked about and which ad they came from. They call, log the outcome, and the task closes. If nobody picks it up, the reminders do the chasing instead of a manager discovering a stale spreadsheet.
Because every lead now has an outcome recorded, you can see which lead ads produce real conversations, which feeds straight back into your ad decisions.
Is this happening to you?
- You have downloaded a CSV of lead ad submissions and found people nobody called.
- Your lead ad integration relies on one person's Facebook login.
- Leads go to a sheet or inbox with no single owner.
- Sales complain that lead ad leads are poor, but nobody tracks contact speed.
- You do not know when the integration last stopped working.