Mailchimp
and Volunteer Shift Manager

There's a particular kind of embarrassment that comes from sending a warm "thanks for volunteering with us this year" email to someone who signed up once in March and never showed up. Or worse, to someone who moved away and asked to be removed nine months ago. It's not a catastrophe. It just makes your organization look like it isn't paying attention, which is the opposite of what the email was trying to say.

The root cause is almost always the same. Your volunteer records live in one place and your email list lives in another, and keeping them in step is a manual job that nobody has time to do properly.

What the integration keeps in sync

Volunteer Shift Manager pushes your volunteers into a Mailchimp audience you choose, and updates them every night. For each person it sends their email address and name, then applies tags describing where they stand:

• VSM: New for someone who signed up but hasn't completed a shift yet
• VSM: Active for anyone who completed a shift in the last 180 days
• VSM: Lapsed for anyone whose last completed shift was longer ago than that
• VSM: [program name] for each program they've actually served in

Those tags are the useful part. They let you write a re-engagement campaign that goes only to lapsed volunteers, or a program-specific update that goes only to the people who've worked that program, without maintaining the segments by hand or exporting a CSV every month.

Tags reflect attendance, not intentions

This is worth dwelling on, because it's the design decision that makes the tags trustworthy. Status is calculated from completed shifts, never from signups.

A volunteer who signs up for four shifts and attends none of them is not Active. They're New, because they've never completed anything. That's usually the honest answer, and it's the one you'd want when you're deciding who to thank or who to ask again. If you've been tracking volunteer hours at all, you already know the gap between who signed up and who turned up is wider than anyone likes to admit.

What it deliberately doesn't do

The sync is one-way. Volunteer Shift Manager writes into Mailchimp and reads nothing back. We don't see your campaigns, your open rates, your click data, or your existing contacts, and none of that is copied into your volunteer records. If you want to know how a campaign performed, you look in Mailchimp, same as always.

It also doesn't sync everyone. Three filters apply, and all three are deliberate:

• Volunteers who declined email consent are never sent
• Volunteers who've left your organization are never sent
• Volunteers with no email address on file are skipped

And nothing at all syncs until you pick an audience. Connecting your account doesn't start anything moving. You choose the list first, which means there's no version of this where a sync surprises you.

One more safeguard worth knowing about: when the sync adds someone, it adds them in a way that can never override an existing unsubscribe. If a volunteer opted out in Mailchimp last year, the nightly sync will not quietly opt them back in. That's a genuine risk with this kind of tool and it's one we designed against specifically.

Consent is the part worth thinking about

When you connect Mailchimp, you'll be asked to confirm something that isn't a legal formality. Your volunteers agreed to hear from you about shifts. Adding them to a marketing audience is a broader use of that agreement, and only you know what you actually told them when they signed up.

We can't make that judgement for you, so we don't pretend to. What we can do is make sure anyone who declined email is never sent, and anyone who already opted out stays out. The rest is a question about your own consent language, and it's worth five minutes of thought before you flip the switch. Our guide to handling volunteer data responsibly covers the wider version of this question.

Setting it up

You'll paste your own Mailchimp API key rather than clicking a connect button. You'll find it in Mailchimp under Account & billing, then Extras, then API keys. Copy the whole key including the bit on the end after the dash, which tells us which Mailchimp server your account lives on.

Then pick your audience from the list we fetch, tick the consent acknowledgement, and you're done. The first sync runs that night, or immediately if you press Sync now.

Where this helps most

This integration earns its keep for organizations that already send real email and want it to go to the right people. If you're writing a volunteer newsletter or running a re-engagement campaign, accurate segments are most of what makes the difference between a message that lands and one that gets deleted.

It's less useful if you email your whole list the same thing every time. In that case you could keep exporting a CSV twice a year and be fine. The tags only pay off when you use them to send different people different things, which is also, not coincidentally, what tends to move open rates.

Mailchimp is one of the integrations included in Engage, at $19 a month. Connect it, pick a list, and let your audience keep itself current while you get on with the actual work.