What a location can have of its own
When to use them
Use locations
Separate branches with their own crews, phone numbers, and hours. Franchises under one parent account. Distinct metro service areas.
Don't use locations
Separating service lines you run from one place — use services and tags. Or organizing your own reporting — filters do that already.
Setting one up
1
Create the location
Under Locations, add it with its address, hours, and service area.
2
Assign a phone number
A number local to that area. Local caller ID answers materially better. See Phone numbers.
3
Connect its availability
Point it at the calendar or CRM schedule the branch’s crews actually work from. See Calendars.
4
Override what differs
Hours, service area, and any location-specific facts. Leave everything else shared — duplicating your whole knowledge base per location creates a maintenance problem that grows with every branch.
5
Test from that number
Call the branch’s number and confirm you get the right hours, the right service area, and a booking on the right calendar.
Scoping access
Team members can be scoped so branch staff see their own location’s calls, contacts, and bookings without seeing the whole business. See Team & roles.Locations over the API
Pass thex-location-id header to scope a request to one location:
