Which CRM Integrations Are Supported? kvCORE vs Follow Up Boss vs LionDesk (Guide)

The agent is only as useful as its connection to your CRM. This is what we integrate with, how the setup works, and what's standard vs custom.

First-class integrations (5-7 day build)

These CRMs have dedicated integration modules. Setup is fast, behavior is well-tested, edge cases are handled.

kvCORE (Keller Williams, eXp, many independents)

• Read: contacts, lead source, stage, custom fields, lead routing rules
• Write: activity log, lead stage transitions, SmartPlan triggers, custom-field updates
• Triggers: new lead from any kvCORE source (Zillow, Realtor.com, website, signup), stage change, SmartPlan completion
• Tested at scale: 50K+ contacts, 200+ daily lead touches

Follow Up Boss (FUB)

• Read: contacts, lead source, stage, tags, action plans, custom fields
• Write: activity log, stage updates, action plan pauses/resumes, tag application/removal
• Triggers: new lead, stage change, "no activity in N days," tag added
• The integration is bi-directional in real time (most CRMs poll; FUB pushes via webhook)

LionDesk

• Read: contacts, lead source, campaign membership, custom fields
• Write: activity log, campaign enrollment, lead status updates, drip campaign triggers
• Triggers: new lead, campaign completion, status change, manual agent action
• Email + SMS sends via LionDesk's existing infrastructure (so deliverability inherits your existing setup)

Real Geeks (website + CRM bundle)

• Read: leads from the website forms, behavior events (listing-page views, search alerts)
• Write: activity log, lead notes, behavioral triggers
• The agent has visibility into what the lead is browsing on your site, which makes the nurture sequences dramatically more relevant

Sierra Interactive

• Read: contacts, lead source, behavioral data, e-Alert subscriptions
• Write: activity log, e-Alert customization, lead stage
• Triggers: new lead, e-Alert engagement, listing-page view

Compass

• Read: contacts, lead source, custom Compass-specific fields
• Write: activity log, lead notes
• Note: Compass has historically had a more closed API; we work within their supported endpoints

Custom integrations (5-10 day build)

Any CRM that exposes a REST API or webhook endpoint can be supported. The build takes longer because the integration module has to be written specifically for that CRM's data model.

CRMs we've built custom integrations for in the past 6 months:

• BombBomb (video email) — for video-touch nurture sequences
• Vyral (drip + marketing) — for buyer/seller drip campaigns
• CINC (Commissions Inc.) — for lead routing + nurture
• Marketo (enterprise marketing automation) — for agents running serious funnel ops
• HubSpot — surprisingly underused in real estate but works fine

If your CRM isn't on either list, ask. Most can be supported.

What "integrate" actually means

The agent has 4 capabilities against your CRM:

1. Read. Pull contact info, lead source, prior touches, behavioral signals, custom fields. Used to inform what the agent drafts (a hot lead from Zillow gets a different nurture sequence than a cold sphere contact).

2. Write activities. Log every agent action — emails sent, SMS sent, calls placed, notes added. Your CRM becomes the single source of truth for what the agent did on your behalf.

3. Trigger sequences. Enroll a contact in a drip campaign, fire an action plan, start a follow-up cadence. The agent decides which sequence based on the lead's behavior + temperature.

4. Update fields. Move lead stage, add tags, set custom fields (e.g., "agent_vibe: warm," "next_action: schedule_search_update").

The agent doesn't touch:

• Your contact database directly (no merging, no bulk edits)
• Your templates (no modifying stored email templates)
• Your integrations with other tools (no breaking your Mailchimp sync, etc.)

Setup steps (standard CRM)

The CRM integration setup is part of Day 1 of the deploy:

1. You grant OAuth access from your CRM (we provide the link, you click "authorize").
2. You map the data fields the agent should read/write (most defaults are correct; you can adjust).
3. You define which triggers the agent should listen for (most use the defaults).
4. We run a sandbox test (the agent pulls 10 sample contacts, drafts a sample email, sends it to a test lead).
5. You approve; production cutover on Day 5.

Total time on your side: 30-45 minutes spread across the deploy.

Sample triggers and actions

Three concrete examples of what the integration does:

Example 1: New Zillow lead comes in.

• Trigger: FUB fires webhook "new_lead" with source=zillow.
• Agent action: pulls lead details (name, search criteria, viewed listings), checks sphere for warm connections, drafts Day-1 welcome email + 3-touch 14-day sequence, sends Day-1, schedules the rest.
• Time to action: ~30 seconds.

Example 2: Lead goes quiet for 21 days.

• Trigger: nightly FUB check finds lead with no activity in 21 days.
• Agent action: drafts a re-engagement email referencing the original search criteria (now updated with 3 new listings that match), sends, marks lead as "re-engagement_in_progress" in CRM.
• Time to action: next morning's batch run.

Example 3: Listing goes live.

• Trigger: kvCORE fires "listing_active" webhook.
• Agent action: pulls the listing details, drafts the MLS description (if listing-copy workflow deployed), drafts a sphere-warming email for past clients in the listing's zip code + neighborhood, schedules the send for peak open-rate time.
• Time to action: ~1 minute.

Troubleshooting

Three issues that come up most often:

"The agent isn't seeing my leads." Usually an OAuth scope issue — your CRM was authorized with read-only scope, the agent needs read+write. Re-authorize from the dashboard.

"The agent's notes are showing up in the wrong format." Field mapping mismatch. The agent writes to a custom field but your CRM expects a different field name. Map check in the dashboard takes 2 minutes.

"The agent triggered a sequence but I didn't get a notification." Notification preferences. By default, the agent sends you a daily summary at 7am. If you want real-time notifications, toggle that in the dashboard.

Data security

The integration uses OAuth 2.0 — your CRM password is never shared with us. Scopes are limited to what the agent needs (read contacts, write activities, trigger sequences). You can revoke access at any time from your CRM's connected apps page.

We don't:

• Sell your data
• Train AI models on your data
• Share your data with other customers

You can request a full export of all data the agent has stored at any time.

What's next

If your CRM is on the first-class list, book a 30-minute consult and we'll walk through what the integration would look like for your setup.

If your CRM isn't on the list, ask — we can probably support it.

If you want to read more, the lead nurture sequences post walks through how the agent uses your CRM data to personalize every touch.