1. Map the Washington service area before choosing automation rules
Your public service area may include Washington and other parts of Daviess County, but the city, the county and Indiana are different geographic scopes. A workflow should therefore record the service-area information your firm actually needs rather than treating every inquiry as interchangeable. Ask what location information belongs in the initial intake, when it should be reviewed by a person and what happens when a prospective client is outside the firm’s intended geography. The Census population estimate for Washington city is eligibility context, not evidence that a particular matter type, response volume or staffing model exists.
Recommended approach
Review recent inquiries by geography, matter type and disposition. Decide which geographic answers affect routing, escalation or decline review. Keep those decisions separate from assumptions based on population, and document whether a county-wide service statement requires a different path from a Washington-city inquiry.
