The decision to make first
An apartment number, building entrance and street address can be mixed together when a caller describes a difficult-to-find property. Read back the location components separately and mark unconfirmed details; never assume a unit from a previous caller’s conversation.
What the handoff should contain
Use separate fields for street address, building or entrance, unit, callback and the staff-approved access instructions supplied for this request.
Suggested wording to approve
Example wording: “I have the street address. Could you confirm the building entrance and unit separately so the office knows exactly which location this request concerns?”
Test the difficult case
Test two similarly numbered buildings and a caller who corrects the unit after initially giving the wrong one. Keep door codes or sensitive entry instructions out of public examples and ordinary marketing analytics, even if a caller volunteers them.
Worked example
Fictional example: The caller first says Building 4, Unit 12, then corrects the entrance to Building 14. A read-back should expose that correction before the conversation ends. Staff should see the final building and unit as separate fields, with no entry code included in a public-facing recap or demonstration output.
Review it in operation
Review corrected-address requests to confirm the final value is visible and obsolete location details are not presented as current.
Check before you launch
- Read back the location components separately and mark unconfirmed details; never assume a unit from a previous caller’s conversation.
- Use separate fields for street address, building or entrance, unit, callback and the staff-approved access instructions supplied for this request.
- Test two similarly numbered buildings and a caller who corrects the unit after initially giving the wrong one.
- Review corrected-address requests to confirm the final value is visible and obsolete location details are not presented as current.
Missed plumbing call calculator ↗
Try Ava with your business’s public information ↗