Decide what happens when location context is unclear
A Smart Business Router campaign needs a useful destination even when a visitor does not share location access or sits outside the areas you planned. Define that fallback before the campaign goes live. The fallback should help the visitor choose a location or reach the team without pretending the system knows more than it does.
Choose a page that can serve every visitor
A location directory, service area page, or contact page can work when it is current and easy to scan on a phone. Show recognizable city or branch names and the next action for each one. Avoid sending uncertain visits to a page that assumes one specific branch, offer, or phone number.
Write the fallback into the routing brief
Record the intended destination for missing location access, an unrecognized area, and a temporary branch outage. Include the person who owns each page and the process for changing it. This turns the fallback into a maintained part of the campaign instead of an emergency redirect no one remembers.
Test the uncertain cases on purpose
Open the campaign with location access unavailable and try it from outside the usual service area when practical. Confirm that the visitor can still understand the available choices and complete an action. Test the final form, call link, or directions link rather than stopping at the first page.
Keep the message consistent with the printed promise
If the sign promises help finding a nearby location, the fallback should support that task. If the campaign offers a local quote, make it clear when availability must be confirmed. Review the fallback whenever a branch, service area, or campaign promise changes so the safest path remains accurate.
