Core: Showings & Listings
Showing scheduling, buyer consultation booking, open house registration, feedback capture, listing inventory, and brokerage configuration. Free. On one database.
The showing carries the buyer. The standard enforces itself.
Schedule & Capture
4 featuresThe showing carries the buyer’s context
A 2 PM Saturday showing carries the buyer’s preferences, their lender’s preapproval confirmation, and their showing history. Three prior showings rejected for small backyards; this one has a half-acre lot.
Feedback triggers on departure
The buyer leaves at 2:47 PM and a feedback request triggers automatically. By 3:15 PM the seller sees the feedback in their portal and the deal record updates. If the buyer loved it, the agent advances the stage to offer preparation from the same screen.
Open House Sign-In
Digital sign-in on tablet or phone creates contacts in the CRM tagged with the listing, the event, and the source. No clipboard. No CSV export.
Buyer Consultation Booking
Clients book buyer consultations and listing appointments into available slots. Auto-confirmations and reminders. Synced with the agent’s calendar across the team.
Listing Inventory
3 featuresListings as structured records
A listing enters as a structured record — address, bedrooms, status, photos — connected to the same data spine as the CRM, the scheduling engine, and the proposal builder. Not a custom field. Not a separate feed.
Showing Access Control
Digital lockbox codes with time windows and auto-expire rules. Buyers get access for their showing slot only, with a full entry audit trail — know exactly who entered and when.
Listing Catalog as Spine
The listing catalog feeds the website, the proposal, the social post, and the portal syndication feed from one record. Update once; every surface reflects it.
Brokerage Governance
3 featuresThe broker sets the standard once
Commission structures, brand standards, and disclosure checklists push from headquarters to every office. The managing broker creates a standard; every location receives it. They can use it. They cannot change it.
Enforced, not emailed
The emailed PDF that nobody verifies is replaced by enforced configuration. Multi-office policy enforcement the booking and listing engines actually read.
Disclosure Checklists
Required disclosures per transaction type and jurisdiction, distributed locked to every office and surfaced before closing.
The showing knows the buyer’s budget.
A showing schedules for 2 PM on Saturday. The appointment carries the buyer’s preferences, their lender’s preapproval confirmation, and their showing history — three prior showings, all rejected for small backyards. This showing has a half-acre lot. The buyer leaves at 2:47 PM and a feedback request triggers automatically. By 3:15 PM the seller sees the feedback in their portal and the deal record updates. Open house sign-ups create contacts in the CRM tagged with the listing, the event, and the source.
The managing broker sets the standard. Every office follows.
A listing enters as a structured record — address, bedrooms, status, photos — connected to the same data spine as the CRM, the scheduling engine, and the proposal builder. For brokerages, commission structures, brand standards, and disclosure checklists push from headquarters to every office. The managing broker creates a standard. Every location receives it. They can use it. They cannot change it. The emailed PDF that nobody verifies is replaced by enforced configuration.
A showing completes in Bookings — feedback logs on the buyer's deal record in Deals. If the buyer loved the property, the agent advances the deal stage to offer preparation. A data connection between Bookings and Deals that currently requires the agent to manually update two separate systems happens automatically.