Start with Moab’s actual service boundary
Moab city is a municipality in Grand County, Utah. The 2020–2024 American Community Survey 5-year population estimate for the city is 5,312, with a margin of error of 17. That is geographic and population context only; it does not establish legal demand, call volume, competition, language preference, staffing needs, lead volume or revenue. For Automation, the practical implication is narrower: define whether your intake serves only people contacting the firm from Moab, people elsewhere in Grand County, or a broader Utah service area. Those boundaries can affect routing questions, ownership and escalation. A workflow should not treat a city population estimate as a substitute for your firm’s inquiry history.
Recommended approach
Before changing a workflow, list the locations and matter types your firm actually accepts. Decide which location information must be collected, which inquiries need attorney review, and which requests should be routed elsewhere. Keep the service boundary explicit rather than using Moab as a proxy for demand.
