01
Section
Problem
Foundation
Viewing requests need to stay attached to the listing and the preferred time.
Use Cases
Property Inquiries
Track viewing requests and property interest with clarity.
Property inquiry workflows need structured data so agents can answer faster and keep listings moving.
At a glance
What EnterestOS keeps visible
Always visible
Tracked
Who responded
Tracked
What needs a reply
Tracked
What is waiting
Tracked
What is completed
Tracked
Which projects are active
Tracked
What changed recently
02
Section
Solution
Priority
EnterestOS keeps the property context visible while the team handles the viewing request.
03
Section
Before EnterestOS
Lifecycle
Showing requests arrive with no clear status, so agents have to hunt through email and notes.
04
Section
After EnterestOS
Closure
The listing, time preference, and contact details stay tied to one submission record.
05
Section
Workflow
Visibility
The lifecycle remains easy to scan.
Reply ↓ Waiting ↓ Done
06
Section
Steps to Set Up
Visibility
Keep the current property page and add tracking after submit.
- Create a project for the listing or agent brand.
- Connect the inquiry form or upload a screenshot.
- Generate the integration prompt.
- Wire the submit handler in your app or builder.
- Submit one inquiry and confirm it lands in the Inbox.
07
Section
Form Structure
Visibility
Property forms usually need the listing, preferred time, and contact information.
export function ViewingRequestForm() {
return (
<form>
<input name="propertyAddress" />
<input name="preferredDate" />
<input name="phone" />
<input name="email" />
<textarea name="message" />
<button type="submit">Book viewing</button>
</form>
);
}08
Section
trackResponse() Call
Visibility
Track the inquiry after the submit succeeds.
await enterestos.trackResponse({
type: 'property_inquiry',
payload: { propertyAddress, preferredDate, phone, email, message },
});09
Section
Best Practices
Visibility
Keep the property context visible and the workflow small.
- Keep the listing title in the payload.
- Do not hide the submission behind a status the team cannot scan.
- Use Waiting for external follow-up.
- Keep Done for closed viewings.
010
Section
Result
Visibility
The agent can see the request, reply with confidence, and keep the showing moving.
011
Section
Common Questions
Visibility
The submission should stay tied to the listing.
- Should I generate custom fields? Only if they help route the inquiry.
- What if the form has select options? Capture the visible options when the user can choose them.
- What if the showing is booked later? Move it to Waiting until it is confirmed.