Skip to content

Shipped build · Real estate

Facebook leads land in the CRM. Every morning, the agent starts calling.

Watch it work

Shipped build · recorded walkthrough

Results

First seven days in production.

~2,500
calls placed
30%
pickup rate
12%
booked into appointments

What it does

  • Runs every morning at 10am, Monday–Saturday
  • Checks line concurrency before every single call — at the limit, waits 5 seconds and takes the next lead
  • Books into the closer's Google Calendar: checks availability, creates, updates, deletes
  • "Call me in 5 minutes" → next call schedules itself
  • Call ends → lead moves to the correct CRM stage

How it’s engineered

Cron-driven, not event-lucky

The pipeline runs whether anyone is watching or not.

Pre-dial concurrency guard

Call quality survives volume.

Calendar through an MCP server

Booking is a first-class tool, not a webhook chain.

Every outcome writes back to the CRM

Pipeline state is always true.

The system

Facebook leads land in the CRM; a cron job at 10:00 Monday–Saturday feeds a pre-dial concurrency guard in front of the voice platform, with outcomes branching to Google Calendar booking over MCP, an automatic callback re-schedule loop, or a CRM stage update.

facebook leadcrmcron · 10:00 mon–satconcurrency guardpre-dial check · wait 5s at limitvoiceplatformbookedgoogle calendar · mcpcallbackre-schedules next attemptdonecrm stage update

Stack

  • n8n
  • Retell
  • MCP
  • Google Calendar
  • CRM

Next build: Instagram agent →

Want a system like this?

Tell us your version of this problem.