A customer account is not a service address. Property managers, landlords, and homeowners with a second home can all request work at a site different from the address most recently used.
Model customer identity, billing details, property, and job location as distinct decisions. The voice workflow should identify the requested site explicitly before it copies equipment history, offers availability, or creates dispatch work.
Ask the caller to supply the property
Start with an open request for the service address. Compare it with authorized candidate properties rather than reading the customer's full property portfolio aloud. Confirm unit, building, and access details when they affect where staff will go.
If the caller describes a nickname such as “the north rental,” ask for a disambiguating address. Keep approved aliases for convenience, but do not let a familiar nickname bypass the location check for a consequential action.
Follow a fictional three-property account
A landlord owns a house on Maple Street, a duplex on River Road, and a small office. They call about no heat in the upstairs River Road unit. The previous service visit was at Maple Street.
The agent should select the River Road property and upstairs unit, then attach the reported issue there. Reusing the last property would also carry the wrong equipment history and might produce the wrong travel assumptions. The billing contact can remain the landlord while site access is coordinated with an approved tenant contact.
| Property scenario | Expected handling |
|---|---|
| Caller gives exact known site | Confirm unit and intended work |
| Nickname matches several sites | Ask for full service address |
| New site under known account | Review property creation policy |
| Two sites need work | Create separate request identities |
| Billing address changes | Do not redirect service automatically |
Keep multi-site requests independently recoverable
One call may legitimately create two requests. Give each its own property, action identifier, status, and follow-up owner. A call-level “completed” flag is too coarse if one site is booked and the other needs dispatcher review.
Separate records increase complexity and may add clarification turns. They also prevent one successful action from concealing a failed action at another location. Staff should be able to see the outcome for each requested site without replaying the whole conversation.
When records conflict, preserve the caller's intended site in a review queue. Avoid creating a duplicate property simply because address formatting differs. Review customer details collection for safe readback and correction patterns.
Questions about multiple properties
Can the last-used property be the default?
It can be a candidate for confirmation, but it should not silently determine the new service location.
Should tenant contact details replace the account owner?
Keep the roles distinct. Follow the business's policy for who receives billing, scheduling messages, and access calls.
What happens when the caller requests two visits?
Clarify each site's work and desired timing, create separate tracked intents, and read back the outcome for each. Do not promise that both succeeded because one remote record was created.