A property enquiry can reach the wrong branch through a general website form, an agent's personal contact route or a forwarded portal message. Moving it to the correct owner should preserve its context and avoid duplicate follow-up. The administrative question is which branch and agent owns the listing under the agency's accepted rules, not which person happens to receive the message first.
The proposed workflow below uses explicit identities, ownership rules and a conflict queue. It does not decide commission, contractual rights or entitlement to a lead. Managers and the agency's approved process resolve those matters. AI may organise an ambiguous message into candidate references, but it should not invent ownership from suburb names or persuasive wording.
Keep listing, branch and agent identities distinct
Create accepted identifiers for the property, listing campaign, branch and assigned agent. An address is useful evidence but may not distinguish several units or campaigns. Agent names can change or be shared by different people. Store the stable identifiers alongside human-readable labels so a renamed branch does not break the map.
The ownership record should show its version, effective period, approving person and any permitted coverage arrangement. If two active assignments appear to govern the same listing, that is a conflict to resolve. Do not select the newest spreadsheet row without checking which record is authoritative.
Map external portal references to accepted internal listing IDs. Keep that mapping separate from contact deduplication. Source: HubSpot record deduplication describes record-ID and unique-property matching for relevant operations. It does not establish estate-agency ownership rules. The documentation also notes that companies created through the API are not automatically deduplicated by company domain name, which illustrates why integration behaviour needs verification rather than assumption.
Apply the agency's ownership rule explicitly
A proposed routing rule is to use the accepted listing assignment for property-specific enquiries, and a separately approved area or service rule for general enquiries. The agency must decide the actual policy. A buyer asking about several listings may need several linked tasks with one coordinated contact owner, rather than three agents sending competing replies.
Treat a customer's preference as a separate field. If they ask for a named agent, retain the request and show whether that person matches the listing assignment. Do not hide it, but do not let it silently overwrite branch ownership. A manager can approve a handover or a collaboration under the agency's process.
Coverage rules also need precision. An agent being away may justify a temporary response delegate without transferring permanent ownership. Store the coverage period, permitted actions and responsible person. Routing, communication authority and commercial entitlement are different decisions and should not share one ambiguous assigned field.
Reusable enquiry ownership decision table
Use this proposed table to specify routing. Managers should approve the rule versions and identify the authoritative assignment source.
| Enquiry situation | Required check | Proposed outcome |
|---|---|---|
| One accepted listing ID | Current branch/agent assignment and version | Attach enquiry to that assignment |
| Several listing IDs | Each accepted assignment and contact coordination rule | Linked tasks with one approved communication plan |
| Address or description only | Candidate listing identities and original evidence | Ask for clarification or agent match review |
| General property search | Approved service/area routing rule | Assign under that explicit rule |
| Named-agent request conflicts | Customer request plus current listing assignment | Manager resolves collaboration or handover |
| Two active owners | Assignment sources and effective periods | Hold reassignment and create a conflict task |
| Agent unavailable | Accepted temporary coverage arrangement | Delegate permitted response actions only |
| Repeat event | Stable message/event ID and existing enquiry | Return existing routing outcome; preserve new content separately |
| Assignment changed | Current accepted version and earlier owner | Record a traceable handover before further action |
Each routing record should retain the enquiry ID, original channel, accepted listing match, selected rule version, branch/agent IDs, decision time and unresolved questions. The completion check is that every enquiry has one accountable communication owner or one named conflict owner, without losing the original request or duplicating an external reply.
A handover note should state: “Enquiry [ID] concerns [accepted listing reference]. It was previously handled by [owner ID] under [assignment version]. The approved new owner is [ID], effective [time]. Open actions are [specific items]. The customer has received [message references]. [Manager decision reference] authorises this handover.”
Read the current assignment before writing a task
Source: OpenAI function calling describes application-side execution of requested functions. A lookup can return the accepted assignment and a task-creation tool can enforce the permitted branch scope. The model's request does not prove that the match or ownership is correct. Validate IDs and rule versions in the application before changing records.
If the assignment changes during processing, refresh it before the write and preserve the conflicting snapshots. A task created from an outdated owner map should not send an irreversible message without rechecking the current authority. The organisation's integration design must define how staff screens and other systems participate in that control.
Avoid giving a routing model broad access to every branch's private notes just to decide an owner. Supply the minimum accepted mapping and the relevant enquiry. A wrong match should lead to a visible review request, not a wider search that leaks unrelated customer or staff records.
Walk through correct, conflicted and duplicate routing
Imagine a hypothetical enquiry with portal reference P-66 mapped to listing L-18. The accepted assignment identifies branch B-East and agent A-4. The workflow attaches the enquiry to that listing and prepares a task for A-4. It retains the original message and assignment version so the agent can see why the task arrived.
A second hypothetical enquiry names agent A-9 but points to the same listing. The system records the customer preference and creates a manager task because it conflicts with the accepted assignment. It does not discard the preference or reassign the listing automatically. The manager can authorise a coordinated response and record any handover through the normal process.
Now suppose a portal retries the same notification. The stable event ID links to the existing enquiry and routing result. If the customer later asks about another property, the new content becomes an additional linked request instead of being suppressed as a duplicate. Contact identity and enquiry intent must remain separate.
A genuine agent transfer also needs history. If L-18 changes to another accepted owner while a viewing question is open, the handover includes previous replies, tentative arrangements and unresolved access checks. A new assigned-agent field alone is not a complete handover. The customer should not have to restate the entire request to repair missing internal context.
Let managers resolve conflicts and test actual routing
Source: n8n human review describes pausing selected agent tool actions for approval or denial. That may support manager review before a sensitive reassignment or external reply. It does not decide commission or provide branch ownership policy. The approval should refer to the exact enquiry and proposed change, not a general instruction to resolve all similar cases.
Evaluate routing with labelled examples covering shared addresses, multi-property requests, agent preference, temporary coverage and assignment changes. Track wrong branch matches, duplicate external contact, missing handover context and conflicts resolved without authority. Use actual pilot findings to assess whether the procedure helps; do not infer cleaner routing from an AI capability announcement.
Questions about branch ownership
Can we route enquiries by suburb alone?
Only under an explicitly approved general-enquiry rule. A property-specific enquiry should use the accepted listing assignment where available. Suburb text can be ambiguous and branch territories may overlap. If the listing match is unresolved, collect the reference or ask a manager rather than using geography to make a definitive ownership decision.
Does the first responding agent become the owner?
That is an agency policy question, not a model decision. Preserve who responded and when as communication history. Apply the accepted ownership or handover rule separately, and send disputes to the manager. The workflow should not transform response speed into an unsupported commercial entitlement.
What if a customer requests another branch after contact begins?
Record the preference and prepare a handover request with the open actions and prior messages. A manager or authorised person applies the agency's rule. Do not erase the earlier enquiry or create an unrelated duplicate that leaves both branches pursuing it. Confirm the communication owner after the approved change.
If your business needs help defining this process, explore AI agents for estate agencies, the wider AI automation services, and our custom-agent workflow guide. The agents and automation comparison and custom AI agent glossary explain the terms. To discuss your records and approval rules, get in touch.