Mojo Dialer + Follow Up Boss: Integration Best Practices

What is Mojo Dialer and why do Follow Up Boss teams use it?

Mojo Dialer is a cloud-based power and triple-line dialer built specifically for real estate prospecting. It lets agents call through lists — expired listings, FSBOs, circle prospecting — at speed, with built-in voicemail drop, local presence caller ID, and lead list management. Follow Up Boss (owned by Zillow Group) is the team inbox, pipeline, and CRM where those conversations are tracked and closed.

The two tools solve different problems. Mojo accelerates dial volume during prospecting sessions. Follow Up Boss stores the relationship history, routes inbound leads, runs action plans, and gives team leaders visibility into pipeline. Used in isolation, each is powerful. Integrated properly, they create a prospecting-to-close loop where no conversation falls through the cracks.

How does the Mojo Dialer Follow Up Boss integration work?

Mojo has a native Follow Up Boss integration that pushes call records, outcomes, and new contact data directly into FUB without middleware. Setup requires your FUB API key, which you generate from your FUB account settings under "Admin > API." Once the connection is live, Mojo can:

• Create new FUB contacts from numbers you dial that aren't already in your CRM
• Log each call as a note on the existing contact record with timestamp and duration
• Push the call outcome (Answered, Left Voicemail, Not Home, etc.) as a note tag or stage update
• Trigger FUB action plans based on those outcome codes

The integration is unidirectional on the core data path — Mojo pushes into FUB, not the other way. For pulling existing FUB contacts into a Mojo dial session, you export a smart list from FUB as a CSV and import it into Mojo. This two-step workflow is standard practice for high-volume dialers.

Step-by-step: setting up Mojo Dialer with Follow Up Boss

1. Generate your FUB API key. In Follow Up Boss, go to Admin > API Keys and create a new key with read/write access. Copy it immediately — you won't see it again.
2. Connect Mojo to FUB. Inside your Mojo account, navigate to Settings > Integrations > Follow Up Boss. Paste the API key and click Connect. Mojo will confirm the connection by pulling your team member list.
3. Map your call dispositions. Mojo call outcomes (e.g., "Appointment Set," "Callback Requested," "Not Interested") should map to FUB stages or tags. Define this mapping in Mojo's integration settings so every outcome lands in the right FUB field.
4. Export your FUB smart list as a dial list. In FUB, filter contacts by stage, last contact date, or custom field, then export to CSV. Import that file into Mojo as a call list for your next prospecting session.
5. Build FUB action plans triggered by Mojo notes. In FUB, create action plans with a trigger like "Note tag contains 'Callback Requested'" to auto-assign follow-up tasks or send texts after Mojo logs the outcome.
6. Test end-to-end. Make a test call from Mojo to a dummy contact. Verify that the call log appears in FUB within two minutes and that any action plan fires correctly.

What call outcomes should you map to FUB stages?

Stage mapping is where most teams leave value on the table. A generic "called" note adds little signal. Structured outcome mapping lets FUB's smart lists and action plans do the heavy lifting after each session.

How do you build a Mojo dial list from Follow Up Boss smart lists?

The smartest prospecting sessions start with a well-filtered FUB smart list rather than a raw imported spreadsheet. Before each Mojo session:

1. Open FUB Smart Lists and create a filter: Stage = "New Lead" AND Last Activity > 7 days ago AND Phone exists
2. Sort by Lead Score or last inbound date so your hottest leads are dialed first
3. Export to CSV — FUB includes the contact's name, phone, email, and any custom fields you've mapped to CSV columns
4. Import into Mojo as a new call session with the date in the list name (e.g., "FUB Cold 2026-06-26") so you can match Mojo session reports back to FUB filters later

Refresh this list daily. Contacts that converted to appointments should be removed from your dial lists via FUB stage updates — the integration prevents double-dialing if you use FUB stage as your filter.

Common Mojo + FUB integration problems and how to fix them

Even a well-configured integration breaks occasionally. These are the most common failure modes:

• Calls not appearing in FUB: Usually an expired or revoked API key. Regenerate the key in FUB and re-enter it in Mojo's integration settings.
• Duplicate contacts created: Mojo creates a new FUB contact when it can't match the phone number exactly. Standardize your phone format (digits only, no dashes) in both tools. FUB deduplication is phone-number-first.
• Action plans not triggering: FUB action plans respond to stage changes, not just note logs. Make sure your Mojo outcome mapping is updating the FUB stage field, not just adding a note text.
• Timezone mismatches on call timestamps: Mojo logs in the account's timezone. FUB displays in the user's timezone. If you're seeing off-by-hours discrepancies, confirm both accounts are set to the same timezone in their respective settings pages.

How can AI layer on top of Mojo + FUB call data?

Once Mojo is logging call outcomes into FUB, those notes become data that AI can act on. Follow Up Ace's agentic layer reads the contact's full FUB conversation history — including Mojo-logged call notes — to generate contextual follow-up messages, update contact scoring, and flag contacts whose engagement pattern has changed.

Specifically, Ace tracks Ace Velocity Score and Ace Days Since Inbound fields (verified in chat-app/shared/aceIntelligenceFieldsConfig.js) that reflect how actively a contact is engaging across all touchpoints including calls. A contact you've dialed three times with no answer will show increasing days-since-inbound and a cooling velocity score — useful signal for deciding when to shift from calls to a different channel.

Ace Trove also surfaces contacts in a "Hot" or "Warm" tier based on Ace Score (0–100), so your Mojo dial lists can be prioritized by AI-predicted readiness rather than just chronological order. See the AI lead scoring guide for a deeper look at how these tiers work.

Best practices checklist for Mojo + Follow Up Boss teams

• Refresh your FUB export before every dial session — never dial from a list older than 24 hours
• Map every Mojo disposition to a specific FUB stage, not just a note
• Build one action plan per disposition that fires a text, email, or task automatically
• Use FUB smart lists to remove appointment-set contacts from future dial sessions the same day
• Review your Mojo session report weekly and compare to FUB pipeline movement to confirm the integration is logging accurately
• Keep your FUB API key rotation policy on a 90-day cycle and update Mojo immediately
• For teams using compliance features, note that Mojo's call recording is separate from FUB's activity feed — store recordings per your state's call recording disclosure laws