Monitorbase + Bonzo: Integration Guide

What Is MonitorBase?

MonitorBase is an always-on monitoring platform built for mortgage professionals. It watches your past clients and prospects for signals, property activity, credit behavior, market indicators, that suggest someone may be ready to transact. When a signal crosses a threshold that matters, MonitorBase fires an alert. 

The core idea is simple: instead of manually tracking hundreds or thousands of past clients and hoping they call you back when they're ready, MonitorBase does the watching for you. Your database becomes an active pipeline rather than a static list.

What makes it powerful in Bonzo is the integration layer. The moment an alert fires, Bonzo picks it up and turns it into automated action — routing the contact into a pipeline, triggering an SMS or email campaign, and surfacing a call task for your team. No manual handoff. No leads falling through the cracks.

Two Ways to Access MonitorBase Through Bonzo

You may have arrived at this integration from one of two directions:

Bonzo users with a MonitorBase subscription — You'll connect using your MonitorBase API key and access the alert types included in your MonitorBase plan (more below). 

MMI One members — MonitorBase monitoring is included as part of your MMI One seat. Base Alerts are active from day one, and Opportunity Intelligence Alerts are available as a paid upgrade when you're ready. Your alert access and billing are managed through MMI One. 

To learn more, click the link below:
MMI One: MonitorBase Alert Types

How Alerts Work in Bonzo

When MonitorBase detects relevant activity, it sends an alert to Bonzo, which routes it into the MonitorBase Opportunity Intelligence Alerts pipeline and assigns it to the appropriate loan officer.

Pipeline Stages

The pipeline includes a stage for each alert type:

Each stage is connected to a campaign. When an alert arrives and routes a contact to a stage, the attached campaign starts automatically — no manual assignment needed.

8 campaigns ship with the integration:

• Property Listing (Base Alert) - Get ahead of the purchase or relocation conversation before anyone else
• Property Listing (Base Alert) - HELOC, cash-out refi, debt consolidation — "Your equity has reached a point where you have options"
• MI Removal (Base Alert) - "You could save $$$ monthly by removing MI" — easy savings for the borrower, easy conversation for you
• Instant Inquiry (OI) - Know within minutes if a contact pulls credit elsewhere. A high-urgency campaign fires automatically so you can reach them before anyone closes.
• Cash Out (OI) - Present a specific consolidation strategy using their full liability picture
• Homebuyer (OI) - Catch purchase intent early, before they've talked to another lender
• Rate & Term (OI) - The bread-and-butter refi conversation, triggered at exactly the right moment
• HELOC (OI) - Fast close, strong equity play — and establishes permissible purpose for future monitoring

To learn more about these alert types and campaigns, click below
MonitorBase Alert Types

You can always adjust campaigns before sending. Simply go to the Campaigns tab, find the MonitorBase campaigns, update messaging to match your brand and compliance guidelines, and toggle them on.

Where to Find the Pipeline

• SuperUser setup: The pipeline is created under the Shared pipelines tab and applies to the entire organization.
• Team Lead setup: The pipeline is scoped to that team. If a SuperUser has already set up the org-level integration, Team Leads will also see the pipeline in their Shared tab.

Setting Up the Integration

Connecting MonitorBase to Bonzo

1. Sign into Bonzo as a SuperUser or a Team Lead with access to System Integrations.
2. Go to Settings → System Integrations → MonitorBase.
3. Enter your MonitorBase API key and click Connect.

Once connected, three configuration areas appear on the MonitorBase integration page:

Preferences — Fallback User & Alert Types

This is where you choose your Fallback User and confirm which alert types you're listening for. Routing is based on email: when an alert fires, MonitorBase sends the originating user's email in the payload, and Bonzo uses that to route the alert to the correct owner. If that user no longer exists in Bonzo, the alert goes to the Fallback User instead. Set this before allowing your team to push large volumes of contacts.

Settings — Webhook Endpoint

Shows the webhook URL MonitorBase uses to send alerts into Bonzo. You typically won't need to edit this, but it's useful for troubleshooting or confirming the endpoint with support.

Logs — Confirming Everything Is Working

Each alert request from MonitorBase appears here with a status code. A 200 means the alert was received and processed successfully. Any 4xx or 5xx code indicates an issue. After your first connection, push a small test group of contacts and check Logs once alerts start coming in — consistent 200s mean your webhook is healthy. For failing entries, capture the details and include them in a support ticket. Your MonitorBase CSM can also send test alerts on request.

Enrolling Contacts

Once connected, the MonitorBase tab inside Bonzo is your command center for monitoring activity and enrollment status.

The first time a user visits this tab, they may be prompted to accept MonitorBase's Terms of Service. Each user who should receive alerts must complete this once — until they do, their contacts won't appear as eligible for monitoring.

Enrollment Statuses

Eligible — Contacts ready to be pushed into monitoring. These have all required information, belong to a user who has accepted ToS, and pass eligibility rules. This is your starting point. You can push contacts individually or in bulk (depending on permissions).

Pending — Contacts you've pushed that MonitorBase is currently processing. No action needed here — once processing finishes, contacts either move to Monitored or Failed.

Failed — Contacts that couldn't be enrolled, with a reason shown for each. Common causes are missing or invalid data. Options: fix the underlying data and re-push, or raise a support ticket if the error isn't clear.

Pro Tip: If you see failures due to "Address Not Found," try selecting those contacts and using Bonzo's Enrich feature to spend tokens on address enrichment, then re-push. This resolves most address-related failures.

Ineligible — Contacts that can't be pushed yet. Common reasons: the assigned user hasn't accepted ToS, or the contact is missing a first or last name. Fix the blocking condition and the contact moves to Eligible.

Roles & Permissions

SuperUser vs. Team Lead

Functionally, the integration behaves the same for both roles — the differences are scope and where settings live.

For SuperUser: 

For Team Lead: 

What Permissions Control

MonitorBase-specific permissions govern:

• Viewing the MonitorBase tab and activity
• Pushing individual contacts
• Bulk-pushing larger groups
• Editing monitor types (alert types beyond defaults)
• Managing the Eligible, Pending, Failed, and Ineligible lists

To assign permissions:

• SuperUser: Go to the Users tab → bulk select users → Manage Permissions → toggle MonitorBase permissions on or off.
• Team Lead: Go to the Team Members tab → select team members → open permissions → enable or disable MonitorBase access.

You can centralize enrollment with one "power user" managing pushes for the team, or give each loan officer control over their own contacts — it depends on how centralized you want management to be.

Getting Help

• For test alerts or integration troubleshooting, contact your MonitorBase CSM.
• For billing or upgrade questions, contact your account team.
• For issues visible in Logs (non-200 status codes), capture the log details and submit a support ticket.

Once the integration is live, contacts are enrolled, and campaigns are toggled on, the day-to-day runs itself. MonitorBase watches your database. Bonzo handles the follow-up. Your team focuses on conversations instead of list management.

The organizations that get the most out of this treat enrollment as an ongoing habit — every new closed loan is a candidate for monitoring, and every eligible contact not yet enrolled is a gap in coverage. The larger your monitored pool, the more the system surfaces.

For troubleshooting, test alerts, or questions about upgrading to Opportunity Intelligence, start with your MonitorBase CSM.