If you’ve got the basics working — broadcaster set up, Gmail forwarding running, starting to see contacts show up in your database — this post is for you. You’re no longer asking “why doesn’t this work?” You’re starting to ask something harder: “how do we keep this working as more people join the team?”

That’s a different problem. With one or two people, good habits are enough. Everyone knows to BCC the broadcaster, everyone checks NationBuilder for replies. But as your team grows, habits break down. People get busy. Someone forgets to BCC. A volunteer replies to a blast and nobody follows up because the reply sat in a Gmail inbox nobody was watching. Your database, which was finally starting to feel useful, gets patchy and unreliable.

The answer isn’t better habits. It’s better systems — ones that work automatically, so the database grows whether or not anyone remembers to do something.

This post assumes you’ve read NationBuilder Email: Why It’s Confusing — And Why Getting It Right Is a Game-Changer →. If you haven’t, start there first.

The Blast List Is a Net — But It Needs the Right Infrastructure

The whole promise of connecting Gmail to NationBuilder is that your blast list grows from the work you’re already doing. Every donor conversation, every volunteer inquiry, every reply to a blast — all of it feeds the list. Your email blast becomes a net that collects donations and political capital from all that effort.

But as your team grows, that net only stays productive if the infrastructure behind it is solid. A system that depends on everyone individually remembering to BCC an address is fragile. One busy week and you’ve got gaps. One new staffer who wasn’t trained and you’ve got a blind spot.

What you want is a setup where the right things happen automatically — where emails get logged, contacts get routed, and your database stays current without anyone having to think about it.

Step One: Give Every Kind of Communication a Home

Before you automate anything, your team needs to agree on what tool is for what. Automation without clarity just creates a faster mess.

Here’s the framework that works for most campaigns and organizations:

Use a chat tool like Slack for internal team communication. This single decision eliminates most of the privacy problems we’ll get to later. If your team isn’t emailing each other internally, nothing sensitive accidentally gets piped into NationBuilder. Email becomes an external-only tool by default.

Use Gmail for external correspondence — supporters, donors, community contacts, press, vendors. This is where relationships start.

Use NationBuilder for logging, blasting, and follow-up workflows. Not as a daily inbox. Think of it as the system of record for your supporter relationships — where everything gets organized and acted on.

When everyone understands this, the question “should I BCC the broadcaster?” answers itself. Emailing externally? Yes. Internal coordination? You’re on Slack, so the question never comes up.

Step Two: Build Out Your Email Architecture

When you first set up NationBuilder, you probably created one broadcaster connected to one email address. That works fine for a small operation. But as you grow, it’s worth building out a proper structure — one that routes people automatically based on how they reach out.

Think of it like a harbor. Each dock handles a specific kind of boat. The right boat goes to the right dock, and everything gets processed correctly without anyone standing at the water directing traffic.

There are two kinds of broadcasters worth setting up:

Role-based broadcasters are tied to functions, not people. They’re the official front doors of your campaign:

• [email protected] — the main public address
• [email protected] — for anyone interested in volunteering
• [email protected] — for donor inquiries and replies to fundraising blasts
• [email protected] — for media contacts

Each address has its own broadcaster in NationBuilder, its own automatic tags, and its own follow-up workflow. When someone emails [email protected], NationBuilder tags them as a volunteer lead and adds them to a follow-up path — automatically, with no one doing anything manually.

Individual broadcasters are tied to specific staff members. Say your regional volunteer coordinator is Claire. You can set up [email protected] as her broadcaster. All of her external correspondence gets logged under each contact’s profile in NationBuilder. If Claire moves on, the relationship history stays. Future staff can pick up exactly where she left off.

There’s a setting in each broadcaster called “Only this person can send messages” — use it for individual broadcasters. It locks the address to Claire so no one else accidentally sends from it, and it creates clear accountability.

One important thing to understand about individual broadcasters: NationBuilder doesn’t have private mailboxes. Everything Claire sends and receives through her broadcaster is visible to every admin in the nation. If she needs a confidential conversation with a volunteer, that happens in her personal Gmail or text message — and she logs a brief note on the person’s NB profile if needed.

Step Three: Automate the Logging — Don’t Leave It to Memory

This is the piece most teams miss, and it’s where the system starts to actually run itself.

In Post 1, we talked about BCCing your broadcaster’s internal address ([email protected]) when you send emails from Gmail, and forwarding your Gmail to that same address so replies get logged. That works great when you remember to do it.

But for a team, you want these things to happen automatically.

Auto-forwarding role-based addresses

For each role-based address — volunteer@, donate@, etc. — set up automatic forwarding to the corresponding broadcaster address in Gmail. You do this once, in Gmail settings, and from that point on every email that comes into that address gets forwarded into NationBuilder without anyone having to think about it.

To set this up: in Gmail, go to Settings → See all settings → Forwarding and POP/IMAP, add the broadcaster’s emailnb.com address as a forwarding destination, enter the confirmation code that NationBuilder sends to your broadcaster’s dashboard, and save. Done — that inbox now feeds the database automatically.

Auto-BCC for outgoing emails

For outgoing emails from your campaign domain, you can set up Gmail filters to automatically BCC your broadcaster on every email you send from that address. This means every email a staffer sends from [email protected] gets logged in NationBuilder without Claire having to remember to add the BCC herself.

To set this up in Gmail: go to Settings → See all settings → Filters and Blocked Addresses → Create a new filter. Set the “From” field to your campaign email address (e.g. [email protected]). In the next step, check “Forward it to” and enter the broadcaster’s internal address. Save the filter.

Now outgoing emails log automatically. Incoming emails log via forwarding. The database grows on its own.

One note: if a staffer is sending from a personal Gmail address rather than the campaign domain, the auto-BCC filter won’t apply to them. In that case, they’ll need to add the CC manually — or, better, switch to sending campaign-related emails from their campaign address.

What Gets Logged — and What Shouldn’t

Automation is powerful, but it means you need to be deliberate about what you’re routing into NationBuilder. Everything that gets logged is visible to every admin in your nation. There are no private folders.

For most supporter interactions, this is exactly what you want. The whole point is that the team can see the relationship history.

But a few categories need judgment:

For sensitive donor conversations — a major gift discussion, a personal situation — keep the actual email in Gmail. Log a short note on the donor’s NB profile instead: something like “Discussed Q3 gift, following up in October.” That gives the team the context they need without exposing a private exchange.

For press and legal matters, same principle. Keep those threads in Gmail entirely and log only what’s useful in NB.

For vendor and operational emails — your printer, your accountant, your event venue — don’t forward or BCC those into NationBuilder at all. Those contacts don’t belong in your supporter database.

The simple test: is this a conversation about your relationship with a supporter? Log it. Is it operational, sensitive, or internal? Keep it in Gmail.

Managing Who Can See What

Because everything in NationBuilder is visible to admins, it matters who has admin access. As your team grows, it’s easy to give everyone full access for convenience — and end up with junior volunteers reading your major donor email threads.

Most people on your team don’t need full admin access. NationBuilder has permission levels — use them. Give people access to what they need for their role, and nothing more. It’s a small thing to set up and it meaningfully contains your exposure.

Keeping the System Healthy

A few habits that keep a well-built system from drifting:

Assign ownership automatically. Configure your broadcasters to assign a point person when someone emails in. A supporter inquiry that sits unowned is a missed opportunity.

Build workflows for common situations. NationBuilder lets you add people to a follow-up path when they email a broadcaster. A volunteer inquiry, a donation question, a blast reply — each should have a next step that triggers automatically. You shouldn’t have to remember.

Review your list periodically. Remove hard bounces. Run a re-engagement campaign for people who haven’t opened an email in a year. A smaller, engaged list outperforms a large, stale one every time.

What This Looks Like When It’s Working

When the architecture is right and the automation is in place, something shifts. You stop managing the database and start relying on it.

New staff get up to speed quickly because the relationship history is all there. Supporters don’t fall through the cracks when someone leaves. Your blast list reflects your real network — not just the people who happened to fill out a form, but everyone your team has been in conversation with. Every email sent from a campaign address feeds the system. Every reply comes back in.

That’s the infrastructure that turns a hard-working team into a durable organization. And it’s mostly just good architecture, set up once, running quietly in the background.