One Phone Number, Two Locations: How to Route Calls So Neither Front Desk Ends Up Covering Both

The real problem isn't the number, it's who owns the call

When a second location opens, the phone setup usually gets decided in about ten minutes. Keep the original number, forward it, sort it out later. Then three months in, the front desk at Location A is fielding parking questions for Location B, your Location B coordinator is sitting idle at 10am and slammed at 5pm, and neither team can tell you how many of their own calls they missed.

The fix isn't a better phone system alone. It's deciding, explicitly, who is responsible for answering what — and then making the routing match that decision instead of accidentally reflecting whichever number you printed on your first batch of business cards.

Pick your model before you touch settings

There are really only three workable structures.

Two numbers, two desks. Each location publishes its own number and answers its own calls. Cleanest accountability. Works when both locations have enough front desk hours to cover their own open time. The weakness: patients call the wrong number constantly, and your Google Business Profiles, ads and old cards leak traffic in both directions forever.

One main number, centralized answering. All calls hit one place — a dedicated coordinator, a small central team, or an AI answering layer — and get booked into whichever location's calendar the patient wants. Front desks stop answering the phone during treatment hours and focus on the people in front of them. This is the model most two-location clinics end up wanting, and the one they usually implement badly.

One number, split by rules. Calls route based on something — time of day, caller history, what the caller says they need. Flexible, but every rule you add is a rule someone has to maintain.

The mistake is picking the third option by default because it feels like the least disruptive. Rule-based routing with no owner is how one desk ends up covering both.

Route by intent, not just by geography

If you go with a single number, the routing question is what you sort on. Options, roughly in order of how well they work:

Menu press-one-for-location. Functional, unpopular. Callers who don't know which location they visited last time guess wrong, and now you have transfers. Fine as a fallback, weak as a primary.

Caller ID plus history. If the number has an existing record tied to a location, send it there. This handles returning patients well and does nothing for new leads — who are the calls that actually matter for revenue.

Ask, then route. A person or an AI receptionist asks what the caller needs and which location works for them, then handles it. This is the only approach that treats a new consultation inquiry differently from a rescheduling request, because those two calls should not go to the same place. A reschedule can be resolved by anyone with calendar access. A new-patient inquiry needs someone who can answer pricing-range questions, capture the lead properly and get it booked before the caller moves on to the next clinic.

This is where AI answering earns its place in a two-location setup: it picks up every call at both locations simultaneously, asks which location the caller wants, books directly into that location's calendar, and only escalates the calls that genuinely need a human. Neither front desk becomes the de facto switchboard, because there is no switchboard.

Write the coverage grid down

Most routing failures are coverage failures wearing a disguise. Build a simple grid — hours down the side, locations across the top — and fill in who answers in every cell. Include the cells everyone forgets:

• Lunch coverage at both locations
• The 30 minutes before open and after close, when a lot of booking calls happen
• Days one location is closed and the other is open
• Staff call-outs
• Saturdays, if one location runs them and the other doesn't

If any cell reads "whoever picks up," that's the cell where your resentment is building. Somebody is picking up, and it's the same person every time.

Make sure the booking knows which building

Routing the call is half the job. The other half is the calendar. Shared-resource problems break multi-location clinics fast: a device that lives at one location, a provider who splits days between both, a room that only exists at one site. If whoever answers the phone can book any service into any location, you will get appointments that can't physically happen.

Two requirements. First, each location needs its own calendar with its own availability rules and its own provider assignments. Second, the confirmation the patient receives must state the address. Not the clinic name — the address. Wrong-location arrivals are one of the most expensive no-show categories you have, because the patient showed up, the slot was held, and nobody gets paid.

SmartSyncLink handles this by keeping location-specific availability behind the answering layer, so a call answered for Location B can only be booked into slots Location B can actually deliver, and the confirmation and reminders carry that address through.

Measure per location, or you're guessing

Split your call reporting by location from the start: calls received, calls answered, calls that ended in a booking, and average time to a callback for anything that went to voicemail or a form. If both locations' numbers are pooled into one report, you cannot see that Location B's afternoons are quietly bleeding leads.

One shared inbox for texts, voicemails and web inquiries helps here, as long as each item is tagged with its location and has one owner. Shared without ownership is just a pile.

A realistic rollout

Start with the coverage grid — it takes an afternoon and usually exposes the actual problem. Then decide your model and commit to it for a full quarter. Keep both numbers live and forward the secondary one rather than retiring it; you'll be surprised how long old listings keep sending calls. Split your reporting on day one, review it at the end of the quarter, and adjust routing rules from what you see rather than from what the front desk feels.

The goal isn't a clever phone tree. It's that at the end of a busy Tuesday, neither front desk had to do the other one's job.