"We integrate with Encompass" is not an integration scope.

Five are supported by the LOS Sync add-on: Encompass from ICE Mortgage Technology, Calyx Point, Byte, LendingPad and Velocity. The sync pushes contact data out to create the loan file, and brings the loan number, milestone values and co-borrower contacts back to create or update the Loan record. Field mapping is customer-configurable, which means it is also customer-maintained — when the origination system changes, somebody has to update the map.

More setup than most teams expect, and it is worth starting early. The lender creates an API user in Encompass carrying the vendor’s partner client ID, plus a persona that can reach the Windows client and mobile. Three fields have to be removed from that persona’s "not accessible" list — Borrower Last Name, Borrower Email and the loan identifier. Users are validated against that persona before every API call, so persona membership is the real access control: add a processor to it and their files sync, remove them and the sync stops for them alone.

No, and this is a common misunderstanding. The Encompass integration moves data, not files — documents in the origination system are not uploaded into the CRM by it. Borrower documents are handled separately through DocsBar or Floify, and both attach to the contact record rather than the loan. That detail matters when you design reporting or plan a migration: the paper trail sits on the person, the pipeline sits on the loan.

Confirm it for your own tenant before you promise anyone real-time updates. The vendor’s own sources disagree — the LOS Sync page states every fifteen minutes, while another vendor article describes it as approximately hourly. The difference decides whether a borrower gets a milestone text within the quarter hour or within the hour, which is exactly the kind of promise a sales process makes casually.

Not a native one. Zapier reaches the platform through the generic Salesforce connector, which is also why no Zapier documentation lists Jungo objects. In practice that means anything touching the Loan record or other package objects is built rather than clicked together — and if you are using the Leads App, the lead volume it processes drives your own Zapier bill as a separate line nobody usually forecasts.

Yes — that is ordinary Salesforce integration work. Where a maintained connector exists we use it; where one does not we build against the API with authentication, error handling, retry logic and monitoring. We also use middleware where the volume or the number of endpoints justifies it, rather than accumulating point-to-point connections that each need their own maintenance.

Whoever you decide, and it needs deciding. Field maps drift, credentials expire, origination systems get upgraded and picklists get edited. We hand over documentation and monitoring, and where there is no internal admin we keep that capacity available; the support page covers the arrangement.