Google Counts Your Forty Locations as One Sender

Google has a simple test for who counts as a bulk sender. Send close to 5,000 messages to personal Gmail accounts in a 24 hour period and you qualify. Every message from the same primary domain counts toward that number, subdomains included.

Now run that through a multi location group. Forty locations, each sending 150 reminders, recall notices, and newsletters a day to Gmail addresses, adds up to 6,000 messages from one domain. No office manager thinks of their location as a bulk sender. Google does. And once a domain qualifies, the status is permanent. It doesn't expire when volume drops.

That's the whole article in one idea. Your locations have separate front desks, separate managers, sometimes separate names. In the inbox, they share one reputation.

The weakest list sets the standard for everyone

Gmail calculates spam rate daily and expects every sender to stay below 0.3%, with 0.1% as the real target. That number belongs to the domain, not to the location that earned it.

So when one location exports a list from its old practice management system and sends a we miss you email to everyone on it, the complaints land on the domain every other location sends from. The location with a clean list and patients who actually asked to hear from it watches its recall notices slide toward spam. Nobody there did anything wrong.

We've argued before that inconsistent communication across locations is a revenue leak and a compliance exposure at the same time. Deliverability is the same problem showing up in a third place. One location's habits become every location's results.

Where groups actually break

In a single practice, a deliverability problem usually traces back to one bad send. In a group it tends to come from structure. Three patterns are worth checking for.

The location with its own tool

A regional manager signs up for a newsletter tool on a company card and starts sending from an address on the group's domain. For bulk senders, Google requires the domain in the From header to align with the SPF or DKIM domain. A tool nobody configured centrally often isn't aligned, so that mail fails authentication under your name.

It's a compliance problem before it's a deliverability one. If that list holds patient data and the tool won't sign a BAA, it doesn't belong in the stack, which is the filter we apply to every tool. Finding it through a deliverability drop is the expensive way to find it.

The location you just bought

Acquisitions bring patient lists with them, along with whatever sending habits the previous owner had. We've written about the communication problem that comes with an acquired location. Fold that list into the group's sending domain on day one and you import the old practice's reputation along with its patients.

Treat an acquired list like any cold patient list. Segment by last visit, start with the warmest slice, and widen only when the numbers hold.

The problem nobody can see

Postmaster Tools, Google's free dashboard, reports spam rate, reputation, and authentication for the domains you verify. Point it only at the primary domain and you get one blended number for forty locations. When it climbs, you know something is wrong but not where.

Once the primary domain is verified, you can add subdomains for their own dashboards. That's the strongest argument for giving each location or brand its own sending subdomain. It won't change how Google counts volume, since everything still rolls up to the primary domain. What it gives you is the ability to see which location is generating the complaints.

Central hygiene, local voice

The right setup depends on what kind of group you are.

If you run one brand with central control, send marketing from a single authenticated subdomain, kept apart from the domain that carries clinical and billing mail. Put the location in the From name and the signature. Patients book with their location, not with the holding company.

If you're an affiliated or roll up group where locations keep their own names, that local identity is worth protecting. A location sending under its own established brand and domain is its own sender, and that's fine. What doesn't work is a patchwork where some locations use their own domain, some use the group's, and one uses a tool nobody approved.

Either way, one rule is worth writing down. No location sends to a list the group hasn't cleaned.

Local teams decide what to say and when to say it. The group owns authentication, list hygiene, unsubscribe handling, and the dashboard. That split keeps what locations are good at, which is knowing their patients, and centralizes what is shared whether anyone planned it or not.

PatientCampaign is built around that split, with every location running its own campaigns under one account and the sending setup handled once for the group instead of forty times. You can apply the same rule with whatever you use today, though. Start by finding out how many tools are sending under your domain right now. If the answer surprises you, that's where the work begins.