Definitive ConnectorEvery value the connector moves between your CRM and Encompass is a row on the Field mapping tab.
A row
- CRM field: a contact field, a contact custom field, a value typed on the workflow action (loan amount, purpose), the opportunity value, or a fixed value.
- Direction: both ways, into Encompass, or into the CRM.
- Encompass field: any field on your instance, including your custom (CX) fields. Search by ID or name.
- Write to Encompass: On create (only when the loan is created), Always (every change in the CRM is sent), or If empty (only fills a blank field).
- Convert: phone, loan purpose, date, yes/no, number, or US state ("Texas" becomes "TX"). Picking a field suggests the conversion its format needs.
Save mapping checks every row against your Encompass fields and highlights any problem.
The defaults
| CRM field | Encompass field | Direction |
|---|---|---|
| First name | 4000, borrower first name | Both ways |
| Last name | 4002, borrower last name | Both ways |
| 1240, borrower email | Both ways | |
| Phone | 1490, borrower mobile phone | Both ways |
| Street, city, state, postal code | FR0104, FR0106, FR0107, FR0108, the borrower's present address | Both ways |
| Date of birth | 1402 | Both ways |
| Loan amount (workflow action) | 1109 | Into Encompass |
| Loan purpose (workflow action) | 19 | Into Encompass |
| The fixed value "CRM" | 2976, lead source | Into Encompass |
| Opportunity value | 2, total loan amount | Into the CRM |
Restore defaults brings these back (save to keep them).
The property being bought or refinanced
The contact's own address is the borrower's present address. The property in the loan is often a different one, so map your lead's property custom fields to the subject property: street 11, city 12, state 14 (with the US state conversion), zip 15.
The property state is written after the loan officer is assigned, because Encompass checks their license against it. If they aren't licensed in that state, the loan keeps no property state and a note lists where they are licensed.
Which side wins
- When a loan is created, the mapped CRM values go into Encompass.
- After that, Encompass leads for rows that go both ways or into the CRM: each loan update copies them to the contact.
- CRM edits reach the loan only through rows set to Always or If empty. Only values that differ from the loan are written, so nothing bounces back and forth.
- An empty CRM value never clears an Encompass field.
- If the loan is open for editing in Encompass, the change waits and is tried again after 2, 5, 10, 15 and 30 minutes, then hourly, for up to a day. If it still can't be written, a note on the contact says so.
Values a field can't take
Every value is checked against the Encompass field it's going to, using your instance's own field definitions, before anything is sent. A value that doesn't fit is left out, and the rest of the loan still goes through. The value is named in the workflow action's warnings and in a note on the contact.
| Field type | Accepted | Left out and reported |
|---|---|---|
| Number, amount, percentage | 350000, $350,000.00, -1,234.5, 5.25% | 300k, about 350,000, N/A |
| Whole number | 3 | 3.5, 12 months |
| Date | most date formats, from 1900 through 2199 | not a date, 1600-01-01 |
| Phone | 10-digit US numbers, in any common style | international numbers, extensions, words |
| ZIP code | 5 or 9 digits | anything else |
| State | TX or Texas | anything that isn't a US state or territory |
| Yes/No, checkbox | yes/no, true/false, Y/N, 1/0 | anything else |
| Dropdown | one of the field's options (any capitalization) | anything else |
| Text with a length limit | up to the limit | longer text |
- Calculated fields (Encompass fills them itself) can't be written. The mapping won't save a row that writes one; map it into the CRM instead. The field picker marks them "calculated".
- The loan number is always set by Encompass.
- After a loan is created, it's read back. Anything Encompass didn't keep exactly as sent is reported too.
Values going into your CRM aren't refused: your CRM keeps whatever it's given. When you map an Encompass dropdown into a CRM choice field, make sure the CRM field offers the same choices.
Sensitive fields
You can map any field, including Social Security numbers. Values pass through the connector without being stored, and in notes, Social Security numbers, tax IDs and account numbers show only their last four characters.
Need help? Email support@definitiveconnector.com. We reply within 24 hours. Please don't send passwords, client secrets or borrower details such as Social Security numbers.