A tenant may know a building nickname or unit number without stating the full property address. The receptionist should clarify enough to identify the correct site before creating consequential maintenance or access actions.
Use approved property aliases and caller-provided information as search inputs. A phone match can locate candidates, but shared numbers, recent moves, and several buildings make it unsafe to choose the first result automatically.
Ask for the detail that separates candidates
If two buildings share a name, ask for locality or street. If a caller gives only “Unit 12,” ask which building. Avoid reading unrelated tenant or occupancy details aloud while narrowing the match.
Record confidence as an operational state: confirmed property, candidate unresolved, or no match. A guessed address should not become a confirmed site merely because it exists in the property database.
Work through a fictional nickname call
A caller reports an issue at “the gardens, flat twelve.” The manager has two developments with Gardens in their names. The agent asks for the street or locality and confirms the full site before attaching the request.
If the caller cannot provide enough detail, the workflow captures the report and approved contact route for staff reconciliation. It does not send a contractor to whichever development was most recently serviced.
| Unclear location case | Required response |
|---|---|
| Building nickname matches one site | Confirm full property context |
| Alias matches several sites | Ask discriminating location detail |
| Unit without building | Clarify building first |
| Caller recently moved | Do not reuse old property silently |
| Still unresolved | Owned reconciliation request |
Preserve the report while location is pending
Unresolved property identity should not erase useful caller information. Capture the issue and timestamp, mark the location question, and route according to the manager's approved fallback. Concerns covered by escalation policy need that route even when routine ticket creation is blocked.
Strict property checks add call time but prevent wrong-site actions. Broad automatic matching is faster while creating more privacy and dispatch risk. Set the boundary based on the consequence of the action, not only recognition confidence.
Test noisy numbers, similar streets, and callers correcting a unit. Review address capture tests for a repeatable scenario structure.
Questions about unclear addresses
Can the caller's number establish the property?
It can provide candidates, but the current service site still needs the approved confirmation process.
Should the agent disclose tenant names to help identify a unit?
Follow the manager's disclosure policy and use caller-provided facts. Do not reveal unrelated occupancy information as a matching shortcut.
What should staff receive?
The caller's supplied location clues, candidate ambiguity, report, approved contact route, timestamp, and owner for resolving the property.