Loading
Because most property enquiries arrive outside office hours, and the response is a form submission that lands in an inbox. By the time somebody reads it on Monday, the applicant has booked two viewings elsewhere.
Speed is most of the game here, and a form is the slowest possible mechanism.
The widget answers from what you actually hold — availability, price, tenure, viewing arrangements — citing the record, and captures the applicant as a lead in Flow with the property attached and a source recorded.
Routing sends it to the negotiator who owns that property rather than to a shared queue with no clock.
It will not book a viewing into a diary or negotiate on an offer. It captures, answers and hands over.
And it will not describe a property beyond what you have recorded. Where a detail is absent, it says so.
The enquiry is already an owned lead with the conversation on it, so the follow-up starts from context rather than from a form.
Duplicate matching means a returning applicant joins their existing record instead of becoming a second lead with a second owner.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Yes, in Flow, with the property, the source and the conversation attached.
No. It captures and hands over; the diary is a person's.
It says so rather than filling the gap.
Half an hour on your own numbers is usually enough to say whether Pulse is the right place to start.