Homebot Integration with Follow Up Boss

What Is Homebot and Why Does It Matter for FUB Users?

Homebot is a home valuation and equity intelligence platform. It sends monthly personalized reports to homeowners showing their current estimated home value, equity position, and local market trends. Agents and lenders use it to stay top-of-mind with past clients and spot potential sellers before they list.

For Follow Up Boss users, the integration value is straightforward: Homebot tells you when a homeowner is paying attention to their home's value. That behavioral signal — a report open, a significant equity milestone crossed — is far more actionable than a contact sitting cold in your CRM with no activity.

Without an integration, those signals stay locked inside Homebot. With one, they flow directly into FUB as tags, notes, tasks, or action plan triggers, putting warm seller leads at the top of your call list automatically.

How Does the Homebot + Follow Up Boss Integration Work?

The integration works through Zapier or Homebot's webhook feature. Homebot fires an event when a homeowner takes a notable action. Zapier catches that event and performs one or more actions inside Follow Up Boss — no custom code required. Direct webhook delivery to FUB's inbound webhook endpoint is also an option for teams who prefer to skip Zapier middleware.

Common Homebot events that can trigger FUB actions:

• Report opened — homeowner viewed their monthly valuation email
• Equity milestone reached — homeowner's estimated equity crossed a notable threshold
• Home value increased significantly — large appreciation since last report
• Consultation requested — homeowner clicked to request a call or meeting

Each of these can map to a FUB action: update a contact field, apply a tag, create a task, or enroll the contact in an action plan designed for warm seller outreach.

Step-by-Step: How to Set Up Homebot with Follow Up Boss

This setup takes roughly 20–30 minutes. You will need a Homebot account with webhook or Zapier access, a Follow Up Boss account, and a Zapier account (free tier works for basic triggers).

1. In Homebot, find your integration settings. Navigate to Settings → Integrations. Look for the Zapier connection or a Webhooks section. Enable the integration and note the available trigger events.
2. Create a new Zap in Zapier. Set the trigger app to Homebot and select the event you want to act on — for example, "Report Opened" or "Equity Milestone Reached." Connect your Homebot account and test the trigger to confirm a sample payload arrives.
3. Set Follow Up Boss as the action app. In the Zap action step, choose Follow Up Boss. Common action types include: "Create or Update Person" (to log the activity on the existing contact), "Add Note," "Create Task," or "Add Tag."
4. Map the Homebot fields to FUB fields. At minimum, map the homeowner's email address so Zapier can match the Homebot contact to the correct FUB record. Then map any additional data — property address, estimated value, event type — to FUB notes or custom fields.
5. Set the FUB action plan or tag. Add a tag such as "Homebot Active" or "Seller Radar — Report Opened," then enroll the contact in a seller nurture action plan if your account has one configured.
6. Test with a real contact. Trigger a sample event in Homebot and confirm the contact updates correctly in FUB before turning the Zap on for your full database.

What FUB Actions Should I Map to Each Homebot Event?

Not every Homebot event warrants the same urgency. The table below maps common events to recommended FUB actions so your follow-up effort is proportional to the signal strength.

How Does Ace AI's Seller Radar Complement Homebot?

Homebot and Ace's Seller Radar solve different but complementary problems. Homebot tells you when a specific homeowner is engaging with their valuation report. Ace Seller Radar tells you which contacts across your entire FUB database are most likely to sell — whether or not they're in Homebot.

Ace runs a nightly account-wide propensity scoring pass (verified: chat-app/workers/inProcessScheduler.js:146). The propensity model combines five factors:

• Tenure — how long the homeowner has lived in the property (35% weight)
• Estimated equity — modeled from a conservative mortgage paydown calculation (30% weight)
• FHFA appreciation data — regional home price index trends (15% weight)
• Area risk signals — local market conditions (8% weight)
• CRM seller tags — any seller intent signals already in FUB (12% weight)

The scores surface in the Seller Radar embed dashboard (available on Pro plan). This means you can cross-reference: contacts who both opened their Homebot report and have a high Ace seller propensity score are your highest-priority calls. Homebot identifies the hand-raisers; Ace tells you which hand-raisers are genuinely ready to list.

Note: estimated equity is modeled, not observed lien data. It is labeled "(est.)" in the Ace interface and should be treated as a directional signal rather than an appraisal-grade figure.

Learn more about the Ace Trove and how it layers intelligence on top of your FUB data.

How Do Ace Score Fields Help Me Prioritize Homebot Leads?

Every Follow Up Ace account, including the free tier, receives seven Ace Score fields that populate nightly on all FUB contacts. These fields give you a second data dimension alongside Homebot engagement signals so you can rank your callback list by actual readiness, not just recency of a report open.

The pre-consolidation free fields (retired June 2026 — see the update note above; the current free set is Ace Win Score + Ace Churn Risk per aceIntelligenceFieldsConfig.js):

• Ace Score (0–100) — overall engagement and lead quality score
• Ace Tier — Hot / Warm / Cool / Cold / Dormant classification
• Ace Status — current lifecycle status label
• Ace Response Time — how quickly this contact typically responds
• Ace Velocity Score — rate of engagement change over time
• Ace Days Since Inbound — days elapsed since last inbound contact action
• Ace Preferred Channel — the communication channel this contact responds to most

A practical workflow: create a FUB smart list filtered to contacts tagged "Homebot Active" with an Ace Tier of Hot or Warm and an Ace Score above 70. That list represents contacts who are both engaging with their home value data and scoring high on CRM activity — your warmest seller pipeline.

See the full picture of how Ace layers on FUB in our Agentic overview.

Troubleshooting Common Homebot + FUB Integration Problems

Most integration issues fall into three categories: contacts not matching, webhooks not firing, and duplicate records. Here is how to address each.

Contacts not matching between Homebot and FUB

Zapier matches records by email address. If the email in Homebot differs from the email in FUB (for example, a contact used a different alias), no match is found and Zapier may create a duplicate. Fix this by auditing your Homebot export against FUB and standardizing email addresses before enabling the Zap at scale.

Webhook events not arriving in Zapier

Zapier polls or waits for a test event during setup. If no real homeowner opens a report during your test window, Zapier will not detect a sample payload. Use Homebot's "Send Test Webhook" feature (if available) or temporarily add yourself as a test contact, open your own report, and verify the Zap catches it.

Duplicate contacts appearing in FUB

This happens when Zapier's "Create or Update Person" step creates a new record instead of updating the existing one. Always map the email field explicitly and verify the FUB Zapier action is set to "update if exists." Use FUB's built-in deduplication tool after the first test run to merge any duplicates created during setup.

Missing field mappings after a Homebot update

Homebot occasionally updates its webhook payload structure. If your Zap stops populating certain FUB fields, re-test the trigger step in Zapier to refresh the available fields, then re-map any that changed. Set a calendar reminder to audit the Zap quarterly.

Does Ace AI Work Alongside Homebot for Compliance?

Yes. When you draft outreach to Homebot-identified seller leads inside Follow Up Ace, Ace's built-in compliance scan checks your messages for Fair Housing language violations before they send. The scanForComplianceViolations() function (verified: chat-app/utils/complianceGuard.js:293) reviews message content in real time.

This is particularly relevant when sending equity-based outreach — language like "great neighborhood for families" or references to school quality can trigger Fair Housing concerns. Ace flags these before they reach the contact. Learn more on the Compliance page.

Can I Use Ace's AI Tools to Write Seller Outreach for Homebot Leads?

Ace includes 215 MCP tools (verified: mcp-server/src/index.ts:206, 3818) that work directly inside Follow Up Boss. Two are especially useful for seller pipelines built from Homebot data:

• pipeline-health-check (verified: index.ts:4198) — scans your seller pipeline for stalled contacts and surfaces who needs attention
• lead-nurture-optimizer (verified: index.ts:4230) — recommends next-best actions for contacts at each stage

Ace connects via Claude at followupace.com/mcp or ChatGPT via SSE at followupace.com/api/mcp/sse/. Once connected, you can ask your AI assistant to draft a personalized follow-up message for a contact who opened their Homebot report and has a high Ace Score, then run the compliance scan before sending — all without leaving your workflow.

Explore the full set of agentic AI capabilities available inside FUB.

What Plan Do I Need for Seller Radar and Voice Features?

Ace's features are available across three plan tiers (verified: embed.js:708). The seven Ace Score fields populate on all plans including free. Seller Radar and voice chat require the Pro plan.

For teams running a large database, the Ace Trove adds a second dimension: account-wide data enrichment, warehouse analytics, and deeper automation, starting at $49/month for up to 5,000 contacts (Starter tier, verified: accountAiBillingConfig.js:64-70).

Key Takeaways

• The Homebot + FUB integration runs through Zapier or a direct webhook — no custom code required.
• Map Homebot events (report opened, equity milestone, consultation request) to FUB tags, notes, tasks, and action plans proportional to signal strength.
• Ace's Seller Radar complements Homebot by scoring your entire contact database nightly — not just those enrolled in Homebot.
• Free predictive fields (Ace Win Score and Ace Churn Risk) help you rank Homebot leads by real win probability, not just by home-value curiosity.
• Ace's compliance scan checks seller outreach for Fair Housing language before it sends — relevant for equity-based messaging.
• Seller Radar and voice chat require the Pro plan; the seven Ace Score fields are free on all accounts.