Declining or referring inbound calls from outside a defined geographic service area.
Geofenced service radius is the practice of filtering inbound calls by the caller’s service address against a defined service-area polygon, so calls from outside the contractor’s territory are politely declined or referred without consuming dispatch time and money.
The contractor defines a service area — usually a radius around a primary location, a set of zip codes, a list of named cities, or a custom polygon drawn on a map. When a caller provides their address, the address is geocoded and tested against the service-area boundary. Inside the boundary, the call proceeds through normal triage. Outside it, the agent either declines the work politely or refers the caller to a partner contractor in that area.
Out-of-area calls are an unmanaged cost. The contractor pays for minutes of conversation, the agent invests triage time, and at the end the call is declined anyway because the address is two counties away. Multiply that by a dozen calls a month and the leakage adds up. Geofencing turns out-of-area calls into a 45-second polite refusal instead of a five-minute consultation that ends in “sorry, we do not serve that area.”
Night Watch supports zip-code lists, city lists, and polygon-based service areas. The address is geocoded once at the start of the call and tested against the configured area. Out-of-area calls get a polite decline with optional referral language the contractor can configure (“we do not serve that area, but our partners at X cover Y”). The decline is logged in the call memo so the contractor can periodically review whether their service area should be expanded based on demand.