The year-end giving campaign playbook — planning the December surge without burning out your team
Compliant appeal outreach, SMS-first touchpoints, volunteer staffing with one-day onboarding, secure donation processing at volume, and the post-campaign follow-up that turns December givers into January donors.
On this page
December is a contact center event
For most nonprofits and ministries, a large share of the year's giving arrives in the final weeks of December — much of it in the final days. That concentration makes year-end giving an operations problem as much as a fundraising one: call volume spikes, volunteers replace or reinforce staff, donation processing has to hold up under load, and every appeal you send has to stay on the right side of outreach regulations.
The organizations that handle December well don't work harder in December. They decide things in October. This playbook covers what to decide, in roughly the order you'll need to decide it.
Plan the surge backward from December 31
Start with the deadline and work backward:
- Map your appeal calendar against capacity. Every appeal wave generates inbound calls and texts — questions, gifts, address changes. If three appeals land the same week your phone team is half volunteers, that's a planning decision, not a surprise
- Build the campaign workflows early. Scripts, routing rules, and giving flows should be drafted and tested weeks ahead, while there's still time to fix them. A drag-and-drop workflow builder means the campaign lead can make those changes directly, without waiting on IT
- Decide your channels per segment now — which donors get a call, which get SMS-first outreach, which get both — so the consent and contact data is clean before the first wave goes out
Appeal outreach that respects donors and the law
Year-end appeals are outbound campaigns, and outbound campaigns carry compliance obligations. TCPA rules don't pause for the giving season, and a December complaint is an expensive way to learn that.
- TCPA-compliant dialing and consent tracking should be built into the campaign, not bolted on — outreach goes only to donors whose consent status supports it, on the channel it supports
- SMS-first for donors who've opted into text, with voice fallback for those who haven't. A short text with a secure giving link often outperforms a voicemail, and it scales when your phone team can't
- Honor opt-outs immediately and everywhere. A donor who opts out of texts should not get a text from the next appeal wave
- Keep the appeal warm and specific — donors respond to what their gift does, and the workflow can put that language in front of every caller consistently
Compliance and donor care point the same direction here: outreach that respects preferences is also outreach that performs.
Staffing the surge with volunteers
Most mission-driven organizations can't hire for a four-week spike, and shouldn't have to. Volunteers can carry a December phone campaign — if the platform meets them where they are.
- One-day onboarding. A keyboard-first agent desktop that a volunteer learns in a single training session means your Saturday training day produces Monday-ready callers
- Script guardrails. The workflow walks the volunteer through the conversation — the ask, the gift amounts, the objection handling — so they sound confident without improvising commitments or rates
- Shift scheduling and on-call rotations managed in the same system, because a volunteer roster is more fluid than a staff one and December schedules change weekly
- Keep volunteers off sensitive ground: crisis calls and pastoral concerns route to trained staff with the caller's history attached, so a giving-line volunteer is never left holding a conversation they weren't prepared for
The test of your volunteer setup is simple: could a first-time volunteer take a gift correctly, kindly, and compliantly on their first shift? If the workflow is doing its job, yes.
Secure donation processing at volume
December 30 and 31 are not the days to discover that your giving process has a manual step in it.
- DTMF masking and tokenization keep card numbers off volunteer screens and out of call recordings — donors key in their own card data, and the system handles the rest. PCI-DSS compliant capture matters even more when the people taking gifts are volunteers
- Self-service giving paths absorb the peak: SMS giving links and web giving handle the donors who don't need a conversation, so the phone line is reserved for those who do
- Recurring and one-time gifts through the same secure flow — December is the best moment of the year to ask a moved donor to give monthly, and the ask only works if setup happens on the same call
- Integrations with Planning Center, Pushpay, and Kindful mean gifts land in your donor system as they happen, not as a January data-entry project
The follow-up is the campaign
The most common year-end mistake is treating December 31 as the finish line. The donors who gave in December are deciding in January whether your organization actually noticed.
- Thank-you outreach within days, not weeks — run as its own campaign, triggered by the gifts themselves, with volunteers making warm calls from a light script
- Recurring-conversion follow-up for one-time year-end givers, sequenced after the thank-you rather than crammed into it
- Tax receipt and acknowledgment questions routed through a workflow that puts the donor's giving history on screen, so January's inbound calls are quick and accurate
A year-end donor who gets a prompt, personal thank-you and a thoughtful follow-up is the start of next year's campaign. One who gets silence until the next appeal is a statistic.
Report on it while it still matters
Per-campaign reporting on giving outcomes lets you steer in real time and learn afterward:
- During the campaign: watch response by appeal wave and channel, so a underperforming script can be revised mid-campaign instead of autopsied in January
- After the campaign: compare segments, channels, and scripts; record what worked while it's fresh; and hand next year's planning team a baseline instead of anecdotes
The short version
Year-end giving is won in October: build and test your campaign workflows early, run appeals with TCPA-compliant consent tracking and SMS-first outreach, staff the surge with volunteers who onboard in a day and work inside script guardrails, keep card data out of human hands with masked, tokenized giving, and treat the post-campaign thank-you and recurring-conversion follow-up as part of the campaign itself. Then report on all of it per campaign, so next December starts from evidence. The surge is predictable — which means it's plannable.
Back to
Industries
Return to the main industries page to see the full product family.
Related guides
Guide
The TAS migration checklist — moving off a legacy answering service platform without losing a client
Importing client scripts, rebuilding dispatch rules, preserving on-call contact trees, migrating reporting formats, parallel testing high-risk clients, and sequencing go-live so nothing breaks at 2 a.m.
Guide
The subscriber retention playbook — saves, win-backs, and the calls that keep circulation alive
Renewal reminders, price-increase notices, cancellation save offers, payment-failure outreach, and win-back campaigns — plus the two numbers that tell you whether any of it is working.
Guide
Routing a shared agent pool — serving every client without commingling any of them
Per-client skill routing, hard data boundaries between tenants, blending inbound and outbound work, protecting each client's SLA when agents are shared, and what to put in front of each client's stakeholders.