The Location You Just Bought Came With a Patient Communication Problem

Sixty nine percent of DSOs expect their private equity sponsors to push for more acquisitions in 2026, according to TUSK Practice Sales' Q2 2026 Dental Market Report, and 78% expect a recapitalization within the next twelve to thirty six months. That's a lot of locations about to change ownership, and every one of them is about to inherit a problem nobody put on the closing checklist.

The location didn't come with your group's patient communication standard. It came with whatever the previous owner happened to be doing, which might be a front desk texting from a personal phone, a dormant Mailchimp account, or nothing at all beyond a paper recall log.

Integration has a sequence, and patient communication isn't in it

The technical side of healthcare M&A integration already has a well understood order of operations: validate the business associate agreements, reconcile EHR systems that often speak incompatible data standards, align cloud governance, and phase the cutover carefully enough that patient care doesn't take the hit. That's the right sequence for clinical and billing systems, and none of it mentions the patient's inbox.

Patient communication usually isn't hostile to that plan. It's just missing from it, which means it gets handled whenever someone remembers, or it doesn't get handled at all until a patient complaint or a missed recall makes it visible.

The gap is invisible for exactly as long as it's expensive

A new location's inconsistent communication setup doesn't cause a problem on day one. It causes one on day ninety, when the group's marketing team finally builds a reactivation campaign off the combined patient list and discovers the acquired location's contacts were never captured with real consent, or were sitting in a personal Gmail account that nobody thought to ask about during diligence.

By then the fix costs more than it would have on day one, because now there's a decision about whether the group can even legally message those patients yet, on top of the technical work of migrating them anywhere.

Same problem, whichever side of it you look at

An inconsistent setup at one location is a revenue leak, since the patients there aren't getting the same recall and reactivation treatment the rest of the group runs. It's also a compliance exposure, since nobody has verified what that location's tool can legally hold or who actually consented to what. Those aren't two separate risks that happen to show up together. It's the same gap looked at from two directions, and treating it as a marketing nice to have instead of an integration requirement is how it stays unowned for months.

This is different from the standardization problem an already established multi location group deals with. Standardizing communication across locations that have been part of the group for years is a change management project. Bringing a newly acquired location's patient communication up to standard is closer to the PMS and EHR integration work that already happens on a defined timeline, and it deserves the same treatment: something that gets checked and fixed before the location goes live under the group's brand, not sometime after.

What actually belongs on the acquisition checklist

Three questions cover most of it. What is this location currently using to communicate with patients, and does it hold PHI under a BAA. What consent, if any, was captured for the contacts on that list. And how quickly can that location be moved onto the group's standard platform rather than running its old tool in parallel for months.

None of that is complicated. It's just easy to skip when the acquisition team is focused on the EHR migration and the org chart, and patient communication doesn't have a natural owner in that conversation yet. Groups that let locations keep real autonomy still need one non-negotiable, which is that every location's patient communication runs through a platform that can actually hold their data. For a roll up adding locations every quarter, that's not a project. It's a step in the process, the same as everything else on the closing checklist.