The problem
Disclosure: the agency is affiliated with Agentificial. This is not an arm's-length client, and we flag that so you can weigh it.
On 21 September 2026 the Meta lead integration was working, but all six lead-handling workflows were still in draft. 69 of 119 contacts had no opportunity and every contact was unassigned: leads landing and rotting.
On 24 September 2026 a second defect showed up. Meta reported 140 leads delivered between 11 and 24 September; the CRM had captured 28.
What we built
- Seven workflows published in mechanics-only form (Calendly bridge, intake, booked, no-show, call-outcome routing, nurture, closed-won): ownership, opportunities, stage movement, tagging and internal alerts are live.
- Lead-facing email steps were left out on purpose. The agency's sending domain fails DMARC and SPF alignment, and that fix sits on the agency's side.
- A Calendly bridge using an inbound webhook and the appointments API, with no middleware.
- Data clean-up: 34 mismatched picklist values fixed and the lead-form qualifier field reconciled (82 stored values, 0 off-list).
- A monitor that compares leads delivered by Meta with leads captured by the CRM.
Result
- Funnel audit, 24 September 2026: 0 of 28 live leads had ever been emailed, texted or called.
- Meta delivered 140 leads against 28 captured: roughly 80% lost between ad platform and CRM.
- Re-subscribing the Facebook page did not fix it. On 25 September 2026 Meta showed 4 leads and the CRM 0.
- Monitor read on 1 October 2026, last three days: Meta 8 leads, CRM 0. Status: breach.
Scope and limits
- Unresolved. The remaining fix is a re-authorisation in Meta Business Settings that the agency holds. The gap was still open at the last monitor read.
- No bookings, closes or revenue are attributed to our workflows. The agency's existing booking and close performance is its own.
- Lead-facing messages stay off until the sending-domain authentication is fixed.