These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Real Estate CRM
- Features
- Property Listings
Property Listings
Maintain consented listing details and keep the property context clear when preparing a viewing.
OverviewListed Properties×
Real Estate CRM · Property Listings
New
Listed Properties
Properties
| Property code | Street address | Property type | Asking price USD | Owner consent | Listing status | |
|---|---|---|---|---|---|---|
| PC-366 | J-7 | PT-180 | 360 | OC-781 | Listed | |
| PC-740 | E-15 | PT-909 | 20 | OC-484 | Listed | |
| PC-218 | H-5 | PT-320 | 570 | OC-353 | Listed | |
| PC-480 | U-21 | PT-696 | 240 | OC-465 | Listed | |
| PC-999 | G-7 | PT-328 | 470 | OC-320 | Listed |
6 of 6 records
PC-366Properties · PRP-80637
ListedStreet addressJ-7
Property typePT-180
Asking price USD360
Owner consentOC-781
What you can do
Identify the property behind the viewing
A property record keeps the address, property type and USD asking price together with a property code. App Administrator maintains those details and the recorded owner consent. The property code gives the team a stable reference when similar addresses or unit descriptions would otherwise make a viewing ambiguous.
The listing state distinguishes a Draft from a Listed property and records later conditions such as under offer, Sold or Withdrawn. Sales Manager can inspect that context when reviewing a viewing record. The opportunity and listing have separate meanings: a customer conversation moving forward does not itself establish that the listing has changed state.
A property visit identifies both the selected property and the viewing reservation. The reservation identifies its property, agent and opportunity. These relationships keep the physical viewing connected to the commercial conversation, while the visit records the address, asking price and feedback submitted for review.
How the work is organized
- Listing maintenance. App Administrator maintains the property code and address, checks the asking price and records the consent information used by the brokerage.
- Viewing context. Sales Manager inspects the listing alongside the selected reservation and opportunity. The property reference should identify the actual place visited, including the correct unit where addresses are similar.
- Separate commercial states. A listing’s state and an opportunity’s stage are distinct records. Review the evidence for each change instead of treating a Won opportunity as an automatic Sold update.
What to agree during setup
Agree a property-code convention and how the team records addresses for buildings with multiple units. Identify the person responsible for keeping owner consent current and the evidence the brokerage uses to support that entry. The recorded text should be understandable to the people preparing and reviewing viewings.
Decide how asking-price changes reach App Administrator. If an external listing source supplies the details, set up that handoff and its review responsibility. Keep the USD asking price distinct from the opportunity’s expected value. The visit’s asking-price entry should have an agreed meaning so the reviewer can interpret the figure discussed with the customer.
Check the handoff on an actual case
Prepare a hypothetical townhouse listing with its property code, address and owner consent. Sales Manager checks the Listed record before reviewing a visit linked to it. The selected reservation and visit should refer to the same property and the intended opportunity.
Next, rehearse a similar address for a different unit. The property code and links must make the difference visible before the wrong viewing is reviewed. Change the listing’s asking price through the authorized maintenance process and inspect the older visit evidence. The reviewer should still understand the price recorded for that earlier conversation.
Finally, close a sample opportunity as Won through its commercial review path and check the property record separately. The team should know which listing maintenance action is needed instead of assuming that the customer outcome silently rewrote the listing.
What your team sees
- Listed Properties — Property details and recorded owner consent for listings marked Listed.
- Viewing Schedule — Stored property and agent holds that Sales Manager can inspect before the viewing handoff.
Follow the work through
Use property visit review and agree listing-source responsibilities in integrations.
What it keeps track of
Data model- Properties
- Consented property listings available for viewing
- Property visits
- Property viewing records awaiting confirmation
- Viewing reservations
- Atomic agent and property viewing holds
- Opportunities
- Property sales opportunities in the pipeline
Who uses it
Permissions- App Administrator
- Maintains listings.
- Sales Manager
- Inspects property and reservation context.
- Auditor
- Reads authorized listing and viewing evidence.
- Relationship Owner
- Prepares the linked visit through the authorized operating path.
Set up Real Estate CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.