Service-area edge cases and ambiguous addresses

The decision to make first

A town name may cover both served and unserved areas, while a caller may know the landmark better than the postal address. Define the precision needed for the service-area decision and use an office-review state when the available information is insufficient.

What the handoff should contain

Capture the supplied town, ZIP code or street fragment, the ambiguity that remains and a callback number for a human check.

Suggested wording to approve

Example wording: “I cannot confirm coverage from that location detail alone. I can mark it for the office to check before we discuss a visit.”

Test the difficult case

Use a street crossing two service boundaries, a misspelled town and a caller giving a landmark instead of an address. Do not treat an incomplete address as eligible simply because a nearby town appears on the approved service list.

Worked example

Fictional example: A street spans two areas and the caller provides only its name. The assistant should ask for the detail required by the business’s coverage rule or send the address for review. Passing the test means no confirmed coverage answer is produced from the street name alone, even when the caller asks repeatedly.

Review it in operation

Sample office-reviewed area decisions and update the approved location list only after the business confirms the underlying coverage rule.

Check before you launch

• Define the precision needed for the service-area decision and use an office-review state when the available information is insufficient.
• Capture the supplied town, ZIP code or street fragment, the ambiguity that remains and a callback number for a human check.
• Use a street crossing two service boundaries, a misspelled town and a caller giving a landmark instead of an address.
• Sample office-reviewed area decisions and update the approved location list only after the business confirms the underlying coverage rule.

Related guides