1. Start with Garrett’s actual service boundary
Garrett city is recorded in DeKalb County, Indiana. A firm may serve Garrett alone, Garrett and other parts of DeKalb County, or a wider Indiana territory. Those are different operating scopes. Automation should therefore be evaluated against the locations and matter types your firm actually accepts, rather than against the city’s population as a proxy for demand. Bosseo’s public Automation page describes workflows for capturing contact details, case type, source and intake answers, then routing the inquiry into connected systems. That makes the first review a boundary question: which inquiries belong in the same workflow, and which require a different owner or response path?
Recommended approach
Write down the geographic areas your firm serves, the matters it accepts and any exclusions. Then review whether an inquiry from Garrett should follow the same path as an inquiry from elsewhere in DeKalb County or Indiana. Keep those decisions explicit; do not infer staffing, language or case demand from the population estimate.
