Someone asks about one unit, returns about another development and schedules a viewing before a new advertising-source message arrives. Should CRM create another opportunity, change ownership or retain both interests? These scope decisions determine how the team follows the person, property and visit together.
Start with the journey from inquiry to a recorded viewing outcome and next step. Avoid combining property management, contracts, collections and all sales in one phase without need. The general property and CRM guide distinguishes these scopes; this article specifies the sales-follow-up journey.
Separate people from property interests
A fictional property-marketing company receives inquiries about two residential developments. One person may want two viewings, and an assistant may arrange appointments. A repeated phone number does not make every interest one opportunity or establish that the sender makes purchasing decisions. Define relationships the team needs to preserve.
Specify person, inquiry source, development or unit, interest, responsible agent and appointment fields. Distinguish customer statements from employee confirmation. If an inquiry describes preferences without selecting a unit, filling a required field should not turn it into a definite reservation.
Acceptance cases for the property journey
| Test case | Company-defined decision | Review evidence |
|---|---|---|
| Another source for the same interest. | Retain the new arrival reference without conflicting follow-up. | Both source histories and an identified follow-up owner. |
| Same person, another development. | Separate linked interest according to the business model. | The second viewing does not erase the first. |
| Unavailable agent. | Substitution or review queue under approved coverage. | No appointment silently lacks ownership. |
| Changed or cancelled appointment. | Update tasks and messages according to policy. | No outdated reminder presented as the current appointment. |
| Unavailable unit. | Verify availability source and review alternatives before promising. | Clear distinctions between interest, viewing and confirmed reservation. |
These illustrative decisions need management approval and do not determine commission entitlement. A technical owner change is not a ruling in a commercial dispute. Separate assignment permissions and reasons from contractual policies outside this article.
Connect routing to actual eligibility
HubSpot documentation describes subscription and configuration requirements for eligible owners and cases left unassigned. Microsoft explains rule order, availability and capacity conditions. Neither reference establishes a complete property system or identical functionality in every plan.
Define project coverage, language or follow-up windows where relevant and how those facts remain current. Review existing account ownership instead of replacing it with every message. Read the general routing rules separately before applying them to property and viewing relationships.
A viewing is work with an outcome
Define appointment confirmation, how agents learn about changes and supervisor visibility. Outcomes may include attendance with interest in alternatives, nonattendance requiring review or an unsuitable unit. “Contacted” does not explain these differences, and recording a visit should not automatically establish reservation status.
If availability comes from another system, identify its source, update limits and behavior when unreadable. Do not present an old file as live availability. Preserve links between suggested alternatives and earlier interests so the reason for a customer's change remains understandable.
Reminders follow events and contact policy
Define channels, eligibility, customer preferences and stopping requests according to organizational context and channel requirements. Creating an opportunity is not blanket messaging permission. Test postponement, cancellation and replies before scheduled reminders, distinguishing sent, prevented and internal follow-up actions.
Use synthetic accounts and data with real sending disabled in preview. Demonstrate inquiry, viewing outcome and next action as one connected exercise. Send the table when requesting property CRM implementation with Nextwave, comparing operational evidence without sales-growth promises or automatic resolution of ownership disputes.
Routing sources and example limits
Documentation on HubSpot owner assignment and Microsoft assignment rules was opened on 4 November 2026. The example and table are original, without actual property or customer data or brokerage-contract interpretations. AI assisted preparation, with information and translation review.
