Homeflow Inbound Enquiries: Difference between revisions
From Standout Property Manager Wiki Help
imported>Standout documentation update (Update Standout help for Communications Centre, portal integrations, Customer Portal and Reports Centre changes through 5 September 2026) |
imported>Standout documentation update (Update Standout help for Sales Progression 2.0 and retain recent Communications Centre, portal, Customer Portal and Reports Centre documentation through 6 September 2026) |
(No difference)
| |
Latest revision as of 08:45, 6 September 2026
Homeflow Inbound Enquiries
Homeflow is integrated into the Communications Centre as a secure push source.
Create the connection
Open Administration → Feeds/Portals → Inbound portal enquiries, choose Homeflow and select the fixed Standout branch.
When the connection is created, Standout generates a one-time HTTPS callback URL. Give the complete URL to Homeflow when they configure Standout as the CRM destination.
Example shape:
POST https://standout.example.com/api/v1/enquiries/portal/homeflow/CONNECTION_ID/ONE_TIME_SECRET
Only a hash of the callback secret is retained. If the URL is lost or compromised, use Regenerate callback; the previous URL stops working immediately.
Push only
Homeflow does not use the normal portal polling scheduler and has no Sync now action. Leads arrive when Homeflow POSTs them to the callback.
The receiver accepts JSON and form-encoded submissions and understands Homeflow-style lead/contact/property structures. The complete original payload is retained for audit and future field mapping.
Normal processing
Homeflow leads use the same Communications Centre pipeline: duplicate suppression, property matching, enquiry classification, unambiguous contact matching, branch routing and assignment to the property's active negotiator where possible.
See Inbound Enquiries and Communications Centre.
