Mapping Enquiry Fields to Salesforce
Portal enquiries carry more than a name and a message. Mapping decides where each piece lands.
What's available to map
- Enquirer name, email and phone
- Listing reference and property address
- Enquiry message
- Source portal
- Enquiry type — general enquiry or inspection request
Standard or custom objects
Enquiries usually become Leads, but they can map to a custom object if your agency models properties or enquiries its own way.
The listing reference is what ties an enquiry to a property. Skip it and you have a lead nobody can connect to a listing — the main thing email-to-lead gets wrong.
Duplicate enquirers
The same person often enquires on several properties. Decide whether that's one Lead with multiple enquiries or separate Leads per property — either works, but choosing deliberately avoids a messy database later.
Send a genuine enquiry through each portal after mapping. Portals format their payloads differently, and a mapping right for one can be wrong for the other.
Xero
Real Estate
Equifax