The industry-specific problem
Weekend leads often arrive while agents are showing homes. By Monday, the prospect may have booked elsewhere. A useful system must know which listing triggered the inquiry, preserve the source's consent record, and avoid contacting a buyer already speaking with an agent.
Step-by-step workflow
- Receive the permitted lead-source webhook in n8n; verify its signature and deduplicate on source plus lead ID.
- Read contact ownership and recent activity in Follow Up Boss CRM. Stop for opt-outs, existing active conversations, or missing calling authorization.
- Queue an eligible call with Vapi. A sub-15-second launch is an operational target, not a guarantee of phone ringing or pickup; Twilio SIP provisioning and carrier latency require separate checks.
- Provide property ID and factual listing context. Anthropic Claude extracts budget, timeline and appointment preference, never inventing listing availability or steering by protected characteristics.
- Write structured notes and an agent task to Follow Up Boss CRM. A voicemail or failed attempt enters a bounded retry policy, not a double-dial spam-filter workaround.
Visual workflow
Listing inquiry → n8n signature/dedup → consent + CRM ownership gate
blocked → agent review
eligible → Vapi qualification → Claude fields → Follow Up Boss task
Specific configuration example
This n8n Code-node fragment consumes a normalized, authenticated event from preceding integration steps. It demonstrates the decision boundary, not a complete API client. Fields are workflow-local mappings, not claimed vendor field names. Upstream credentials, schema validation, permissions, durable reservations and provider operations must be implemented separately. Numeric policy examples are illustrative, not Imperio service terms.
// n8n Code node: normalized, authenticated lead event
const lead = $json;
const canCall = lead.ai_voice_consent === true &&
lead.opted_out !== true && !lead.active_agent_conversation;
return [{ json: {
action: canCall ? "queue_qualification" : "agent_review",
dedupeKey: `zillow:${lead.lead_id}`,
crmPayload: { personId: lead.fub_person_id,
propertyId: lead.property_id, assignedAgentId: lead.agent_id },
callContext: { listingId: lead.property_id, maxAttempts: 1 }
} }];
Outcome to measure
Measure consent-eligible leads reached, median webhook-to-call initiation, and appointments held, not just booked. Illustrative arithmetic: 80 eligible weekend leads × a 10-percentage-point improvement in held-appointment rate = eight extra attended appointments. This is a planning scenario, not an Imperio client result.
Compared with manual work or other tools
Manual follow-up offers rich local judgment but depends on agent availability. A CRM email sequence is simpler and less intrusive, but cannot resolve a buyer's questions in a live conversation. Use voice only where permission and lead value justify it.
Work with Imperio Automation
Ask Imperio Automation to map your brokerage consent records, Follow Up Boss ownership rules and weekend qualification pilot.
Frequently asked questions
Can it call every Zillow lead immediately?
No. Lead-source terms, seller-specific consent, local calling windows and suppression checks must pass first.
Will double dialing bypass iPhone spam screening?
No reliable guarantee exists. Use legitimate caller identity, carrier reputation practices and bounded retries, not bypass claims.
Can it tell a buyer a home is still available?
Only from a current authorized listing source; uncertain status goes to the listing agent.