Feature guide
Mortgage CRM with Encompass Integration
Encompass runs roughly half of US retail mortgage origination volume — by some estimates above 55% market share. If your mortgage CRM does not talk to Encompass, your LO is re-keying borrower data into both systems or your processor is doing it for them. Neither scales. This page covers five mortgage CRMs that integrate with Encompass — Approvr included — and is honest about which integrations are real two-way sync vs. one-way push, a distinction that matters more than most marketing pages admit.
The five CRMs we'd actually consider
Ranked on fit for Encompass integration. Pricing as of May 2026.
| # | CRM | Rating | Best for | Starting price | Notes |
|---|---|---|---|---|---|
| 1 | Surefire CRM | ★★★★★ | Retail Encompass shops needing first-party sync | Custom (enterprise) | ICE-owned; first-party two-way Encompass sync |
| 2 | Jungo | ★★★★★ | Salesforce shops with deep Encompass-via-Salesforce integration | $59/user/month | Deep, but requires Salesforce admin |
| 3 | ApprovrOur pick | ★★★★★ | Broker shops wanting real two-way Encompass sync without custom dev | $97/month | Two-way sync with Custom Field ID mapping at setup |
| 4 | BNTouch | ★★★★★ | Retail LOs needing Encompass push for milestone updates | $148/user/month | One-way push; not full two-way sync |
| 5 | Total Expert | ★★★★★ | Enterprise Encompass retention engine | Custom (enterprise) | Deep two-way for enterprise; implementation fees apply |
Why Encompass sync depth matters more than 'has Encompass integration'
Most mortgage CRMs claim Encompass integration. Few say what kind. The distinction lands in three specific workflows. One-way push vs. two-way sync. One-way push: when the LO updates the CRM, certain fields write to Encompass. Two-way sync: when an Encompass milestone fires (case status changes, condition added, document uploaded), the CRM also updates. Most 'Encompass-integrated' CRMs are one-way push only. That is fine for marketing automation, but breaks down on operations — your CRM dashboard shows stale milestone data because Encompass changed it five minutes ago and the CRM does not know. Custom Field ID mapping. Every Encompass instance has different Custom Field IDs — the field where Broker A stores 'borrower employer' is not the same field where Broker B stores it. Integration that works out of the box past basic borrower fields requires Custom Field ID mapping at setup. CRMs that do not support mapping force shops to do their custom development inline. Milestone-event triggers. When Encompass moves a file from 'Started' to 'Pre-Approved,' that event should be able to trigger CRM automation: send a milestone message to the borrower, schedule a Realtor call, attach a document request. CRMs that lack milestone-event triggers reduce Encompass sync to a data mirror rather than an active workflow input. The CRMs in this list differ meaningfully on all three dimensions.
What to look for in Encompass integration
Five capabilities define real Encompass integration. Real two-way sync on borrower data and milestone events. Not just a CRM-to-Encompass push, but a bidirectional sync where Encompass-side changes reflect in the CRM within minutes. Ask the vendor explicitly: 'When an underwriter adds a condition in Encompass, when does it show in the CRM?' Two-way platforms say 'within 5 minutes.' One-way platforms say 'on next manual refresh' or 'never.' Custom Field ID mapping at setup. The integration should support mapping 15-40 Custom Fields during onboarding, not require the broker to write custom development. ICE Marketplace certified integrations typically support this; non-certified integrations often do not. ICE Marketplace certification. Preferred but not required. Marketplace-certified integrations have been tested against Encompass behavior and are supported by ICE's partner relationship. Non-certified integrations can be excellent — Approvr's is — but Marketplace listing is a credibility signal. Milestone-event triggers for automation. CRM automations should fire on Encompass events: case status changes, condition adds, document uploads, fund dates. If your CRM cannot trigger on Encompass events, you are paying for the integration twice — once for the sync, once for the automation that would normally fire from it. eFolder and eDocs awareness. Documents in Encompass live in two places: eFolder references and the eDocs vault. Real integration handles both.
Frequently asked questions
See Approvr in the workflow you actually run
- Waitlist members get the $97 Starter or $247 Pro rate locked in for life — even if prices rise later, you keep your original rate as long as your subscription stays active.
- Every waitlist member gets a one-hour personalized onboarding call to migrate contacts, set up pipelines, and configure their first automations.