Multi-State DSO Call Routing: Time Zones and Holiday Hours

Multi-state DSO call routing decides which office answers a patient, and when. Get it wrong and a caller in Phoenix hears a closed message at 10 a.m. Or a Chicago patient lands at a Seattle office that has not opened yet. Many of those callers will try the next practice on the list.

If your group already works to reduce missed calls across locations, time zones and holiday hours are the next layer. This guide shows how to set local-time hours, handle daylight saving and split-zone states, build holiday calendars, and test it all before a busy week.

What Is Multi-State DSO Call Routing, and Where Does It Break?

Multi-state DSO call routing is the set of rules that sends each patient call to the right location based on local hours, time zone, and holiday status. It breaks wherever one organization-wide schedule gets applied to offices that share neither a clock nor a calendar.

The problem grows with the footprint. According to ADA Health Policy Institute data reported by Becker's Dental, 16.1% of U.S. dentists were affiliated with a DSO in 2024, up from 7.2% in 2015. You can find the underlying dentist workforce research on the ADA Health Policy Institute site.

Why DSO growth makes routing harder

Growth like that adds states faster than phone rules get rewritten. The same Becker's report puts DSO affiliation at 27% of dentists in both Nevada and Colorado, 25% in Arizona and Georgia, and 23% in Florida. That short list covers Pacific, Mountain, Central, and Eastern time, a state with no daylight saving, and a state split across two zones. Newer dentists are driving the trend too, since ADA News reported that more than 1 in 4 dentists within ten years of graduation were DSO-affiliated in 2024.

Where multi-location routing usually fails

Here is where routing usually fails:

• One hours template is copied to every location, whatever its time zone.
• Holiday closures are entered once for the whole group, not by state or region.
• Overflow rules send calls to a sister office that is already closed.
• Callback promises are made in the caller's time instead of the office's time.
• Nobody tests the schedule after a daylight saving change.

Standardizing patient calls across 50 or more offices fixes scripts and tone. It does not fix the clock. That needs its own rules, and they start with how each location's time is stored.

How Do Time Zones Change Which Location Should Answer?

The dialed office's local time decides whether it is open. Your headquarters clock and the caller's area code are both unreliable inputs, because a 212 cell number can ring from Denver, and a Dallas headquarters runs an hour ahead of an El Paso office.

Why a state is not a time zone

A state is not a time zone. Several states you probably operate in are split, and two skip daylight saving entirely. A group that treats "Texas" as one schedule will misroute calls near El Paso every single day.

A four-step routine for local-time routing

The fix is a short, strict routine:

1. Store a named time zone for each location, such as America/Chicago or America/Phoenix, not a fixed UTC offset.
2. Check open or closed status at the moment of the call, in that location's zone.
3. Ignore caller ID when deciding which clock applies.
4. Give callback promises in the office's time and name the zone, for example "by 9 a.m. Central."

Named zones carry daylight saving rules with them. Fixed offsets do not, which is why they drift twice a year.

How Do Daylight Saving Changes Affect a Multi-State Call Schedule?

Daylight saving shifts most offices by one hour twice a year, but Arizona and Hawaii skip it, so their position relative to other offices changes. A schedule built on fixed offsets will treat a Phoenix office as open or closed an hour off for roughly half the year.

When the next clock changes happen

The next change is close. Clocks fall back on Sunday, November 1, 2026, and spring forward on Sunday, March 14, 2027. Both changes happen at 2 a.m. local time, which means offices in different zones change at different real moments.

Picture a 14-office group spread across four zones. After the fall change, the Phoenix location suddenly lines up with Mountain offices instead of Pacific ones. If its overflow partner is a Los Angeles office, the two now sit an hour apart, after lining up all summer.

A pre-change audit for every office

Run this audit the week before each change:

1. List every location that does not observe daylight saving and note its new offset.
2. Review overflow pairs, because the open-hour overlap between two offices will change.
3. Place scripted test calls at 7:55 a.m. and 5:05 p.m. local time at each office on the first Monday after the change.
4. Confirm that after-hours greetings state the correct reopening time.

Avoid editing schedules on the Sunday of the change. Make updates earlier in the week, when someone is around to catch mistakes.

How Should You Build Holiday Hours for Multi-State DSO Call Routing?

Build holiday hours in layers: group-wide closures first, then state or regional observances, then single-location overrides. The most specific layer wins, so one office can open on a day the group closes without breaking any other schedule.

The three layers of a holiday calendar

Layers also keep upkeep small. When a regional holiday changes, you edit one list instead of fourteen offices.

1. Group-wide: New Year's Day, Memorial Day, Independence Day, Labor Day, Thanksgiving, and Christmas.
2. State or regional: Patriots' Day in Massachusetts and Maine, Texas Independence Day, Pioneer Day in Utah, Mardi Gras in Louisiana, and Kamehameha Day in Hawaii.
3. Location overrides: provider vacations, staff meetings, weather closures, and one-off events.

Why dates matter more than weekdays

Dates matter more than weekdays. Thanksgiving lands on Thursday, November 26 this year, Christmas falls on a Friday, and New Year's Day 2027 also falls on a Friday. Many offices will close for long weekends, so those closed-message days stack up fast. Our framework for weekend and holiday call coverage covers what callers should hear on those days.

Half days and partial closures

Do not limit yourself to open and closed flags. Half days need their own setting:

• The day before Thanksgiving, when many offices close at noon.
• Christmas Eve and New Year's Eve, which often end early.
• Lunch closures, which differ by office and are easy to forget.

For wording on closure notices and patient-facing policies, the ADA practice management resources offer a useful starting point.

What Should Happen When One Location Is Closed and Another Is Open?

Overflow should only go to a location that is open right now in its own time zone, and the caller should hear which office is helping. A closed sister office is a dead end, so the routing rule must check its local status before transferring.

Using time zone overlap on purpose

Time zones can work in your favor. An Eastern office that closes at 5 p.m. is still within business hours for a Pacific office, which stays open until 8 p.m. Eastern. In the morning, a Pacific office that opens at 8 a.m. is already at 11 a.m. Eastern, so it can absorb late-morning overflow from Eastern offices.

Plan these pairings on purpose. Our guide to handling dental call overflow explains when peaks happen and what they cost, and the same logic applies across state lines. Keep a second layer ready too, because phone system failover rules decide what happens if a whole location loses its lines.

What the caller should hear

When a different office takes the call, the caller should hear:

• Which office is helping, stated plainly.
• Which office the appointment will be booked into.
• When the home office will follow up, with the time zone named.
• Emergency instructions if symptoms are urgent.

The helping office should book into the caller's home office schedule, not its own. Otherwise a patient in Tampa can end up with a slot in a Phoenix chair.

How Do You Route After-Hours and Emergency Calls Across Time Zones?

Use the same triage rules in every state, then change only the handoff by local time and on-call coverage. Urgent symptoms do not wait for an office to reopen, so the first answer a caller gets must be consistent everywhere you operate.

Why demand peaks outside office hours

Demand outside office hours is real. An analysis of national emergency department survey data from 1997 to 2007 found rates of nontraumatic dental visits were 40%-50% higher during nonworking hours and 20% higher on weekends than the overall average, according to a study indexed in the National Library of Medicine's PubMed Central. Those are emergency room visits, but they show when dental problems tend to surface.

For a group, the challenge is that "after hours" starts at different real moments. When a Pacific office is closing at 5 p.m., it is already 8 p.m. in New York. National oral health context for sizing this demand is available from the NIDCR data and statistics pages.

A shared urgency model with a local-time step

Start from a shared urgency model. Our overview of AI call routing for urgent and routine calls shows how callers get sorted, and the multi-state version adds a local-time step:

1. Identify urgent signs such as facial swelling, uncontrolled bleeding, trauma, or a knocked-out tooth.
2. Look up the on-call dentist for that location or region at the local time of the call.
3. If nobody is on call, give clear emergency instructions, including when to seek hospital care.
4. Log a message for the next open session with the local callback time.

Routine calls can wait for morning. They still need a real reopening time in the caller's local context, not a generic "next business day."

What Compliance Rules Change From State to State?

Call recording consent, AI disclosure, and outbound calling windows can all differ by state, so routing rules need a state flag in addition to a time zone. A group-wide policy often has to follow the strictest state the group operates in.

Recording, disclosure, and calling windows

• Recording consent: some states require every party to agree before a call is recorded. Our state-by-state call recording guide lays out the differences.
• AI disclosure: requirements for telling callers they are speaking with an automated system are evolving. See what applies in our summary of AI disclosure requirements for dental practices.
• Outbound calls and texts: federal telemarketing rules limit calls to 8 a.m. to 9 p.m. in the recipient's local time, and many practices use that window as a conservative default for reminders. Details are in our TCPA compliance guide for dental practices.

Scheduling outbound batches by local time

That last point catches multi-state groups often. A reminder batch scheduled for 8 a.m. at headquarters lands at 5 a.m. for a patient on the Pacific coast. Schedule outbound batches by the patient's local time, not the sender's.

This is general information, not legal advice. Confirm the specifics with your compliance counsel before you finalize policy.

How Do You Test and Monitor Routing Across Multiple States?

Test with scripted calls at each office's open, lunch, close, and holiday boundaries, then review missed and misrouted calls by location every week. Most routing failures show up at the edges of a schedule, not in the middle of the day.

A four-checkpoint test plan

A simple test plan covers four checkpoints per office: five minutes before open, five minutes after open, five minutes before close, and five minutes after close. Add one holiday call and one daylight saving check per quarter. For a 20-office group, that is 80 baseline calls, which a small team can finish in a morning.

Metrics to review weekly

• Missed-call rate by location and hour of day.
• Calls that reached a closed message during open hours, which signals a schedule error.
• Calls transferred to an office that was closed.
• Time from message to callback, measured in the office's local time.

The first two metrics are the fastest signals of a bad schedule. Our breakdown of dental call analytics metrics explains how to read the rest. Front desk teams should keep reviewing a sample of calls too, since they know what patients actually ask about.

Where Should a Multi-State DSO Start?

Start by giving every location its own named time zone and its own holiday layer. Once those two inputs are right, overflow, after-hours, and compliance rules get much easier to reason about.

Pick one multi-state cluster this week and place scripted calls at its open and close times. Fix what breaks, then repeat the process across every region before the November 1 clock change. Strong routing is built one boundary at a time.