Reply speed for property leads
For property sales teams in Egypt and the Gulf: reply to new leads within minutes during working hours, set a clear rule for nights, and measure it weekly.
The ad keeps spending, Ads Manager keeps counting leads, and your sales team sees nothing. Here is why it happens and how to catch it the same day.
Lead ads usually stop syncing for one of five reasons: an expired or revoked connection, a changed Facebook password or page role, a new form the integration was never told about, a permission removed from the page, or a billing or account problem at the tool in the middle. None of these stop the ad, so the leads pile up inside Meta while your team sees silence. The fix is to compare what Meta received with what your CRM received, and to alert someone when a form that normally gets leads goes quiet during working hours.
When someone submits a lead form on Facebook or Instagram, Meta stores the lead and, if a tool is subscribed, sends a short notification to that tool through a webhook. The tool then asks Meta for the full lead using an access token tied to a person and a page. Only then does the lead appear in your CRM or inbox.
That chain has several links: the page subscription, the token, the person who granted it, the page role of that person, the form itself and the tool that receives it. Any one breaking is enough to stop leads, and the ad itself keeps running because, from Meta’s point of view, the leads were collected successfully.
Silence looks normal. A form that gets five leads on a quiet Tuesday and zero on a broken Tuesday looks the same from the sales floor. Salespeople assume marketing paused the campaign; marketing sees leads in Ads Manager and assumes sales has them. Each side is right about what it can see.
In our experience, the gap is usually found when a manager compares the Ads Manager lead count with the CRM at the end of the week, or when a customer calls asking why nobody contacted them. By then some of those leads have already spoken to a competitor.
The reliable signal is not an error message, because often there is none. It is a form that normally gets leads and has had none for longer than usual during working hours.
A good quiet-form alert has three properties:
Wasla does this per form: the Channels settings show each form’s leads in the last 7 days and its last lead, and the owner and team leads are alerted when a form goes quiet. Reconnecting takes a Facebook sign-in, and your settings and existing leads stay as they are.
Usually because the connection between the page and the CRM broke: an expired or revoked access token, a person who lost their page role, a new form that was never mapped, a lead-access permission change, or a problem at a connector in the middle. The ad keeps collecting leads inside Meta meanwhile.
Not immediately. Meta keeps submitted leads for a limited period, and you can download them from Meta Business Suite or Ads Manager and import them. Recover them quickly, because they are only kept for a while and the customers are waiting.
Compare per-form lead counts in Meta and in your CRM, and set an alert for when a form that normally gets leads has none for longer than usual during working hours.
It can. Access tokens tied to your account may be invalidated, and you then need to reconnect the page in the tool you use.
Yes. Wasla tracks each connected lead form, counts only working hours, uses each form’s own pace, and alerts owners and team leads when a form goes quiet.
Checked 17 November 2026. Prices and features of other products change; check their sites before deciding.
Start a 14-day trial, connect your lead forms and see the last lead per form. No card needed.