From Lead to Listing: A 5‑Step Ace AI / Action‑Plan Recipe That Doubles Speed‑to‑Contact

Why does speed-to-contact matter so much in real estate?

Speed-to-contact is the gap between the moment a lead hits your CRM and the moment you make first contact. Research from the Harvard Business Review found that companies contacting web leads within an hour are seven times more likely to have a meaningful conversation than those who wait even 60 minutes. In real estate, where the same buyer has submitted inquiries on three competing portals, minutes matter more than hours.

The problem is not motivation — it is workflow. Most agents have no automated gate that fires the right message at the right moment. Action plans inside Follow Up Boss solve part of that, but they require manual enrollment. An AI layer that reads the lead, scores the urgency, drafts a personalized first message, and enrolls the right sequence in one step is what moves the needle.

What is the 5-step lead-to-listing recipe?

Each step below maps to a concrete action inside Follow Up Boss, with Ace AI handling the parts that slow agents down. The steps run in order; skipping any one breaks the loop.

1. Score the lead the moment it arrives
2. Send a personalized first message within 5 minutes
3. Enroll the 10-day speed-to-lead follow-up sequence
4. Advance the pipeline stage automatically
5. Scan every outgoing message for compliance before sending

The recipe takes about 20 minutes to wire once. After that it runs on every inbound lead without you touching a keyboard.

Step 1: Score the lead the moment it arrives

Lead scoring is only useful when it is fast enough to influence your first action. Ace AI writes a composite score and engagement tier directly into Follow Up Boss custom fields as soon as a contact is created or updated — no manual tagging, no waiting for the next batch run.

The current scoring fields written to FUB custom fields include:

• Ace Score — composite engagement score (0–100)
• Ace Tier — Hot / Warm / Cool / Cold banding from the score
• Ace Status — pipeline status auto-updated from activity (New, Contacted, Engaged, Active Client, Closed, Nurturing, Dormant)
• Ace Velocity Score — engagement velocity (0–100) derived from event volume in 7-day and 30-day windows
• Ace Response Time — minutes to first response after lead creation
• Ace Preferred Channel — SMS, email, or call, weighted by recency
• Ace Days Since Inbound — days since the contact last reached out

These fields are available on the free tier. The Ace Trove paid tier adds deeper intelligence fields: AI-classified lead type (Buyer, Seller, Investor, Buyer-Seller), property profile synthesized from IDX search data, buyer readiness (Ready Now / Actively Looking / Researching / Passive), and an AI-generated lead summary with a recommended next action — all written back to FUB so every agent on the team sees the same picture on the contact card.

The practical outcome: when a Zillow lead hits your pipeline at 11 PM, Ace has already scored it, classified it as a buyer, and noted the preferred channel before your alarm goes off.

Step 2: Send a personalized first message within 5 minutes

The 5-minute window is the gold standard for new lead contact — the Ace AI speed-to-lead tracker treats anything beyond 15 minutes as a high-priority gap. That standard is encoded directly in the ai_engine_get_speed_to_lead_status tool (mcp-server/src/aiEngineTools.ts), which returns the contact's status in the speed-to-lead window plus the recommended next action.

Getting a personalized message out in that window without copy-pasting a template is the hard part. Two approaches work in practice:

• Ace in FUB chat: Open the contact, type "draft a first-touch SMS for this buyer lead" — Ace reads the contact's source, property search data, and score before writing the message. You review, tap send.
• MCP connector (Pro): Connect Claude Desktop or ChatGPT to your Follow Up Boss data via the Ace MCP endpoint at https://followupace.com/mcp (or the SSE endpoint at https://followupace.com/api/mcp/sse/). With 200+ MCP tools available, you can draft, review, and log the message from any AI client — agentic workflows can even do this without opening FUB at all.

Personalization signals to include in that first message: the property address or search area Ace extracted, the source (Zillow, Realtor.com, website form), and the time of day. A message that references what the lead was actually looking at converts dramatically better than a generic "Thanks for reaching out."

For teams on a Zillow speed-to-lead workflow, Ace's zillow_speed_to_lead_check tool checks where a contact stands in that window and surfaces the recommended action, so the first-touch message is aligned with what the lead actually needs.

Step 3: Enroll the 10-day speed-to-lead follow-up sequence

A single first message is never enough. Research consistently shows it takes multiple touches across multiple channels before a new lead responds. The question is not whether to follow up — it is whether the sequence is already built and ready to fire.

Ace's enroll_speed_to_lead composite tool (in mcp-server/src/composites.ts) builds a contact's 10-day speed-to-lead playbook in a single call: it drafts the first message and lays out the full 12-touch follow-up sequence with timing and channel rotation. You supply your existing FUB action plan ID and the contact's personId; Ace handles the enrollment via POST /actionPlansPeople — the same endpoint Follow Up Boss exposes for action plan writes.

The sequence covers the first 10 days because that is when the highest percentage of conversions happen. After day 10, contacts move to a longer-term nurture cadence.

For teams that want Ace Trove recipes to handle this automatically — enrolling the correct FUB action plan based on the lead's buyer readiness tier — the Ace Trove recipe catalog includes an "Active Buyer" recipe that enrolls the appropriate plan via POST /actionPlansPeople when buyer readiness is "Ready Now" or "Actively Looking."

What should a 10-day real estate follow-up sequence include?

The channel mix matters. Leads who prefer SMS respond poorly to email-only sequences. Ace's Ace Preferred Channel field tells you which channel to lead with for each contact — that signal should drive how you order your action plan steps.

Step 4: Advance the pipeline stage automatically

Pipeline hygiene is invisible work that most agents skip, which means team leaders have no visibility into where deals actually are. Ace's Ace Status field auto-advances through stages — New, Contacted, Engaged, Active Client, Nurturing, Dormant — based on actual activity signals, not manual updates.

This matters for three reasons:

• Smart list segmentation: FUB smart lists built on the customAceStatus field automatically surface who is in each stage without agents manually re-tagging contacts.
• Pipeline health reporting: The Ace Trove's pipeline-health-check tool (in mcp-server/src/index.ts) performs an account-wide analysis of active slip alerts, accountability gaps, and high-intent contacts — it can only work accurately if stages are current.
• Re-engagement recipes: When a contact's status drops to Dormant, the Ace Trove recipe catalog includes a re-engagement recipe that suggests enrolling your "Re-Engagement" action plan via POST /actionPlansPeople.

The key habit to build: treat every FUB action plan stage change as something Ace should know about. Log notes, send from FUB, and keep activity inside the CRM — that is the data Ace reads to keep scores and statuses current.

Step 5: Scan every outgoing message for compliance before sending

Speed is only an asset if what you send is legally safe. Fair Housing violations and licensing-rule breaches can come from well-intentioned messages — phrases that steer toward or away from neighborhoods, language that implies discriminatory intent, or unlicensed claims. The pressure of responding fast makes these errors more likely, not less.

Ace's scanForComplianceViolations() function (in chat-app/utils/complianceGuard.js) scans message text against Fair Housing and licensing rules before anything goes out. In the MCP surface, the scan_message_for_compliance tool (registered in mcp-server/src/index.ts via COMPLIANCE_TOOL_DEFINITIONS) exposes this check to Claude Desktop or ChatGPT — so if you are drafting messages from any AI client, compliance runs on every draft automatically.

For teams running agentic workflows where messages are drafted without human review of every word, this gate is not optional. Learn more about how Ace handles real estate compliance guardrails.

How do these five steps work together?

The power of the recipe is in the handoffs. Each step produces an output that the next step consumes:

1. Score produces a tier (Hot / Warm / Cool) and a preferred channel.
2. First message uses the tier and channel to write the right opening touch at the right moment.
3. Sequence enrollment uses the buyer readiness field to pick the correct action plan — active buyer vs. passive researcher vs. long-term nurture.
4. Stage advancement tracks which contacts responded and which went dark, automatically creating segments for re-engagement recipes.
5. Compliance scan runs at every drafting step — first touch, follow-up #3, re-engagement message — so speed never comes at the cost of legal exposure.

What does this recipe require in Follow Up Boss?

The five-step recipe uses Follow Up Boss natively. What Ace adds is the intelligence layer on top. Here is what each plan tier gives you:

Steps 1 through 3 of this recipe are usable on the free tier with manual action plan enrollment. Step 4 (auto stage advancement) and Step 5 (MCP compliance scan in agentic workflows) benefit from Pro. Teams that want the Ace Trove buyer readiness and lead summary fields to drive sequence selection need the Ace Trove add-on, which starts at $49/month for accounts with up to 5,000 contacts.

How do I set up the recipe for the first time?

1. Connect Ace to Follow Up Boss — sign up at followupace.com and complete the FUB OAuth flow. Ace creates the custom fields in your FUB account automatically.
2. Build your action plans in FUB — create an "Active Buyer (10-Day)" plan and a "Re-Engagement" plan with the steps from the table above. Note the action plan IDs (visible in the FUB URL when you open the plan).
3. Configure the Ace Trove recipes — in the Ace admin dashboard, map the buyer readiness tiers to your action plan IDs. "Ready Now" and "Actively Looking" map to the active buyer plan; "Passive" maps to the re-engagement plan.
4. Test with a live lead — create a test contact, watch the Ace Score and Ace Status fields populate, use AI chat to draft a first message, then manually enroll the action plan using the contact's personId and your plan ID.
5. Wire the MCP connector (Pro) — point Claude Desktop or ChatGPT at https://followupace.com/mcp. Verify the enroll_speed_to_lead and scan_message_for_compliance tools appear in your tool list. Run a dry-run compliance scan on a sample message.

What are the most common mistakes agents make with lead response?

The biggest mistakes are not about effort — they are about system design:

• No action plan enrolled at lead creation. The first message goes out, then nothing. The lead responds on day 3 and no one is tracking it. Sequence enrollment must be automatic, not manual.
• Generic first-touch messages. "Hi, thanks for reaching out!" signals to the lead that you did not read their inquiry. Personalization requires reading the contact record before writing — Ace does this automatically when you use AI chat.
• Treating all leads the same cadence. A buyer who toured three properties last week and a buyer who clicked a Facebook ad for the first time need different sequences. Ace's buyer readiness field is precisely the signal to use here.
• Ignoring the preferred channel. If a lead only responds to texts, an email-heavy sequence is wasted effort. The Ace Preferred Channel field — derived from actual engagement events — tells you where to focus.
• Letting pipeline stages go stale. Stale stages mean re-engagement outreach goes to contacts who already bought, and hot leads sit in "New" indefinitely. The Ace agentic workflows that run pipeline health checks depend on stages being current.

Further reading

• Zillow Speed-to-Lead Playbook — how Ace handles Zillow-specific lead timing and qualification
• Ace Trove overview — buyer readiness scoring, lead summaries, and the full recipe catalog
• Agentic workflows — automating the full pipeline with Claude Desktop or ChatGPT via MCP
• Fair Housing compliance guardrails — how Ace scans outgoing messages before they send
• Guides — step-by-step walkthroughs for common FUB workflows