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.
- Property Listing Portal
- Features
- Accounts
Accounts
Seller and counterparty identities linked to listing engagements.
OverviewAccount Cards×
Property Listing Portal · Accounts
New
Account Cards
Accounts
| Name | Code | Contact name | Address | Eligibility note | Organization | |
|---|---|---|---|---|---|---|
| Account 819 | CDE-136 | Contact 949 | U-20 | EN-835 | ORG-3776 | |
| Account 956 | CDE-448 | Contact 164 | Z-12 | EN-796 | ORG-4066 | |
| Account 722 | CDE-750 | Contact 547 | Z-7 | EN-345 | ORG-5827 | |
| Account 835 | CDE-580 | Contact 879 | B-11 | EN-996 | ORG-1447 | |
| Account 932 | CDE-464 | Contact 578 | U-15 | EN-347 | ORG-3162 |
6 of 6 records
Account 819Accounts · ACC-38166
CodeCDE-136
Contact nameContact 949
AddressU-20
Eligibility noteEN-835
OrganizationORG-3776
What you can do
Know which party belongs to each engagement
Accounts hold the clients, sellers and counterparties associated with listing opportunities. Each account has a name, code, contact name, address, active flag and eligibility note. Its organization link keeps the relationship in the correct brokerage scope. An opportunity points to its counterparty account, making the seller or other party visible while the Relationship Owner works the engagement.
The App Administrator maintains account information and organization membership. The Relationship Owner uses the account record when preparing opportunities and contacting the party. A clear account code helps a team distinguish similar names; the eligibility note carries the operational context a reviewer needs when a listing or outcome is submitted. The account remains a shared reference rather than a fresh copy of contact details on each listing.
How the work is organized
- Identity and scope. The account code and organization link identify the party in the brokerage’s records.
- Contact context. The contact name and address support the owner’s daily relationship work.
- Eligibility note. The note lets the team record why this party may be used in the engagement.
What to agree during setup
Agree who may create an account, how duplicate names are checked, and what the account code means. Decide how the active flag is maintained and who can change an eligibility note after an opportunity is already in review. Give staff a consistent practice for contact names and addresses. If separate brokerage organizations share a seller, decide which organization owns each account record and how staff recognize the right one.
Prepare examples of an active seller, an inactive historical account and two parties with similar names. The App Administrator and Relationship Owner should confirm which account each opportunity references. During implementation, compare imported account codes with existing records before linking opportunities, since the relationship is more useful when staff can trust it.
Check the handoff on an actual case
A Relationship Owner receives an instruction from a seller whose name resembles another account in the same organization. The owner searches Account Cards using the code and contact name, checks the address and asks the App Administrator to update the eligibility note if needed. The opportunity is linked to the correct counterparty. Later, the Sales Manager reviewing a listing can follow the parent opportunity back to that account and compare the seller identity with the authorization file. If the wrong account was linked, the team corrects the opportunity before submitting a listing revision. The original listing decision is not used to bless a different seller.
What your team sees
- Account Cards — Active parties with contact details and eligibility context.
- Opportunities Overview — The current engagements that refer to those accounts.
Follow the work through
Opportunity qualification uses the account at intake. Listing review and publication brings its authorization into the decision. Explore references.
What it keeps track of
Data model- Accounts
- Clients, sellers and counterparties associated with listing opportunities.
- Organizations
- Brokerage organizations that own listings and relationship records.
- Opportunities
- Listing engagements worked by relationship owners from new through won or lost.
- Record attachments
- Owner authorization and supporting evidence files linked to an opportunity.
Who uses it
Permissions- App Administrator
- , Relationship Owner, Sales Manager.
- The administrator maintains the account; the owner links it to an engagement; the manager checks the party during review.
Set up Property Listing Portal your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.