Each location gets its own phone number, hours, team, and knowledge — all managed from one dashboard with one subscription.
Each location has different hours, staff, and procedures. One-size-fits-all phone systems break.
Managing separate phone systems per location is expensive and fragmented.
Callers at Location A shouldn't get information about Location B.
Every feature below is included on every plan. No add-ons, no feature gates.
Add as many locations as you need. No per-location fees. Each gets its own phone number and configuration.
Each phone number maps to a location. Your agent automatically loads the right hours, team, and knowledge.
Org-wide policies apply everywhere. Location-specific details (address, parking, hours) are scoped per office.
See aggregate metrics or filter by location. One dashboard for your entire operation.
Add locations from your dashboard in minutes. Each gets its own number, hours, team, and knowledge — while sharing your org-wide policies. No per-location fees.
Watchtower scores calls across all locations. Filter by location to see which offices perform best — and which need attention.
Your agent answers in a voice and name you choose, included on every plan. Hear the voices →
Add locations from your dashboard — name, address, phone number
Configure per-location: hours, holidays, team, knowledge overrides
When someone calls Location A's number, your agent uses Location A's context
Org-wide knowledge (cancellation policy, insurance) applies everywhere automatically
Dashboard shows unified or per-location analytics
No. Locations, phone numbers, team members, and knowledge entries are all uncapped on every plan, and billing happens once at the organization level. A five-office practice and a single storefront on the same plan pay the same. Call minutes are the only thing that varies, so adding a location changes your bill only to the extent it brings more calls.
Each phone number belongs to one location, so the number dialed answers the question before anyone speaks. A caller reaching your downtown number gets downtown's hours, team, and knowledge automatically. Your agent also carries the name, address, timezone, and hours of every location, so "what time does the eastside office close" is answered directly, and when a caller needs location-specific help the agent asks which location they mean rather than guessing.
Yes. Hours, holidays, quick facts, FAQs, team members, escalation rules, catalog items, and booking calendars can all be scoped per location. Know how the merge works, because it differs by type: the greeting is genuinely replaced by a location's own setting and each location's own hours are what the agent quotes, while location-specific facts, FAQs, catalog items, and escalation rules are added alongside the organization-wide ones rather than replacing them. Keep org-level entries to what is true everywhere and put the rest on the location, and give each location's entry its own label (Parking, Downtown rather than a second Parking), because fact and policy labels have to be unique across the organization. Timezone is detected from the address, so a three-timezone operation needs no manual setup per site.
Not today, and it is worth knowing before you plan your numbering. A number maps to exactly one location, so you cannot point a single line at a hand-picked group (one number for your three eastern offices, another for the two western). Each office gets its own number, or a single-location organization uses one number for everything. Moving a number to a different location after it is added is also not available in the dashboard yet.
White-glove setup
Custom API integrations, webhooks, CRM sync, escalation design — designed, wired, and tested on live calls. Included with any plan. No setup fees.
Call Allison, describe your business, and she'll build your agent. Or sign up and configure it yourself.