Calling
›
Texting
›
Email
›
Relational organizing
›
Voter Universe
›
Insights
›
Campaign tools
›
Run a labor union membership drive
A step-by-step guide to growing your membership.
Read the guide →
Talk to a 10DLC expert
Get compliant and keep your texts delivering.
Get expert help →
Watch our latest webinar
See how campaigns run smarter with CallHub.
Watch now →
Run unified campaigns for better reach
One campaign. Every channel. Automatic.
See how it works →
Industry
Advocacy
›
Unions
›
Nonprofit
›
Political
›
Partners
Organizations and agencies we work with to help campaigns run smarter.
NationBuilder Democracy Partners PDI
View all →
Pricing

6 Departments, 1 Texting Platform. How We Help a 15,000-Student Private University Unify Advancement Texting

A 120-person advancement office, a giving day undermined by texts that arrived up to 12 hours late, and a shared platform that will let every team reach its own audience on its own schedule.

100,000
Constituents to Reach
students, alumni, parents, donors
6
Departments, One Account
each with its own sub-account
10–15K
Contacts Per Campaign
typical segmented send
~2 wks
To Implement
with a pilot available first
OrganizationSectorCRMProducts Used
Private UniversityHigher Education / AdvancementBlackbaud CRM (on-premises)Broadcast SMS/MMS · P2P Texting · Text-to-Give · Voice Broadcast

About the University

Our partner is a private university with roughly 15,000 enrolled students and a 120-person Office of Advancement. That office speaks to about 100,000 constituents: current students, alumni, parents, donors, and prospects.

Advancement is not one team with one message. Annual and Loyalty Giving, Alumni Relations, Donor Relations, Athletics Fundraising, and Development each run their own programs, for their own audiences, on their own calendars. A typical segmented campaign goes to 10,000 to 15,000 people. When the university’s biggest fundraising moment of the year arrives, every one of those messages has to land on time.

We are working with the advancement office and its 6-person selection committee from evaluation through rollout that’s currently underway. This is their story.

The Problem: Giving-Day Texts That Arrived After Giving Day Ended

A 24-Hour Window, and Texts That Missed It

The university’s annual giving day runs for 24 hours. Text reminders are one of the most effective ways to bring donors back during that window. For consecutive years, those reminders arrived late, some of them up to 12 hours after they were scheduled.

Donors noticed. Some replied that they had wanted to give, but the campaign was already over by the time the text reached them. Staff then had to send a separate giving link, and any gift made through it did not count toward the day’s goal.

What late delivery cost on giving day

  • Time-sensitive reminders landed up to 12 hours after they were scheduled
  • Donors replied that they wanted to give, but the 24-hour window had closed
  • Staff had to send a separate giving link to recover those gifts
  • Gifts made through that link did not count toward the giving-day goal

What the Old Setup Held Them Back From

Late delivery was the most visible problem. But the team had been working around structural limits for years:

  • Unreliable CRM sync. The previous vendor’s integration with Blackbaud CRM did not sync cleanly in both directions, so engagement data did not land where fundraisers needed it.
  • One-way messaging. The interim tool could broadcast but could not hold a conversation. When a donor replied, staff copied the reply out and answered by email.
  • Unrecognizable senders. The interim tool sent from a new number every time, so recipients never learned to recognize the University.
  • A single gatekeeper. 6 departments wanted to text their own audiences, but the setup made all of them depend on 1 owner to send anything.

Why They Chose CallHub

The 6-person selection committee scored vendors against a requirements list built around 3 priorities: messages that land on time, independence for each department, and the ability to actually talk with donors.

RequirementWhy it mattered
Fast, predictable throughputGiving-day messages must land inside a 24-hour window
Separate accounts per departmentAthletics, alumni and donor relations each run their own programs
Department-level opt-outsA donor who opts out of solicitations may still want stewardship event invites
Two-way texting in one placeReply to donors without leaving the platform
Consistent, local sender numbersRecipients recognize the university’s number
Bi-directional CRM syncClicks, replies and opt-outs flow back to Blackbaud
Click-through and conversion reportingThe core success metrics for annual giving under $5,000
FERPA-aware data handling, MFAStudent data and IT security review

How We will Help the Advancement Office Move Faster and Reach Further

1 Account, 6 Departments, No Gatekeeper

We set up the advancement office with 1 central account and a sub-account for each department. Each sub-account will have its own numbers, campaigns, workflows, and opt-out list, so every team can send on its own schedule. The main admin can allocate credits from a shared pool to each department before a campaign runs. Student agents can be shared across sub-accounts but never see billing.

Opt-outs are scoped by department, too. A contact who texts STOP to Athletics Fundraising can still receive Donor Relations event invites. STOP handling and the opt-out notice are built into every script.

Scheduled Broadcasts That Land Inside the Window

Campaigns will be built once, scheduled with time zone and send-hour limits, and run automatically. Registered 10DLC senders typically deliver a few hundred messages per minute, so a list of several thousand clears in about 1 hour. For a 24-hour giving day, that is the difference between a reminder that drives a gift and one that arrives after the window has closed.

2-Way Conversations from Numbers Donors Recognize

Peer-to-peer campaigns will send the first message automatically. Staff or student volunteers will handle replies on desktop or mobile, with saved replies, surveys, a profanity filter, and the option to call a donor who needs help giving. No more copying replies into email.

Teams can rent numbers in the campus area code and keep them all year across campaigns, so donors learn to recognize the University when it texts.

Text-to-Give, Text-to-Join, and Workflows

Donors will be able to text a keyword to a 10-digit number and get a donation form link, without the cost of a short code. Workflows will handle the follow-through automatically: contacts who reply move to a peer-to-peer follow-up, non-responders can move to a voice broadcast, and uninterested contacts go to a suppression list.

Blackbaud CRM Sync: Engagement Data Where Fundraisers Need It

Lists will come in from Blackbaud, and tags, link clicks, survey answers, and opt-outs sync back. Because the University hosts its CRM on-premises, the sync will run through the CallHub API and the University’s existing middleware layer.

Reporting Built Around Annual Giving Metrics

Per-campaign spend, click tracking, delivery rates, response rates, and best send times are all available in one place and exportable as PDF. Click-through and conversion, the core success metrics for annual giving (i.e, donations above $5,000), are tracked from the start.

How Each Department Plans to Use It

Each Advancement team uses a different combination of channels from the same platform.

DepartmentUse casesChannels
Annual GivingGiving-day countdowns, small-dollar appeals, click-but-didn’t-give follow-upsScheduled broadcast MMS, workflows, text-to-give
Athletics FundraisingDonor appeals, ticket and fan engagementBroadcast, text-to-join
Alumni RelationsEvent registration, reminders, post-event follow-up (no solicitation)Broadcast to small segments, peer-to-peer
Donor RelationsStewardship event invites, thank-you messagesPeer-to-peer, broadcast
Student EngagementMessages to the full student body (~15,000)Broadcast
LeadershipRecorded message from the chancellor to a segmentVoice broadcast with uploaded MP3

Built to pass a university IT review

  • Certifications. SOC 2 Type II and ISO 27001, plus a HIPAA attestation and GDPR-aligned controls.
  • Messaging compliance. TCPA-aligned opt-out handling, automatic landline removal, and 10DLC registration support from our compliance team.
  • Data. Hosted on AWS; data moves over HTTPS via CRM integration, API, or CSV. The university decides which fields to import, and no student ID or SSN is required.
  • Access. Individual logins with multi-factor authentication; agent, collaborator, and admin roles limit who sees billing and campaign settings.
  • Rollout. About 2 weeks to implement. Can include a dedicated Customer Success Manager; support runs 20 hours a day, 7 days a week.

The Expected Results

What the Advancement Office Will Be Able To Do Now That Was Not Possible Before

  • Give every department its own voice. 6 teams send on their own schedules, from their own numbers, without waiting on a single owner.
  • Schedule giving-day messages with confidence. Broadcasts built once, scheduled with time zone and send-hour limits, and run automatically.
  • Respect opt-outs by department. A donor who opts out of solicitations can still hear about stewardship events.
  • Answer donors by text. Replies handled inside the platform by staff or student volunteers, not copied out to email.
  • Keep engagement data in Blackbaud. Clicks, replies, survey answers, and opt-outs sync back to the CRM.

The Future: Branded Messaging with RCS

RCS was not on the committee’s original requirements list, but once they saw it, a branded sender became one of the features they cared about most.

RCS (Rich Communication Services) is the successor to SMS. Instead of a bare phone number, messages arrive from a verified sender showing the university’s name and logo. That solves the recognition problem the team had with its interim tool more completely than a consistent phone number can.

The committee was also interested in multiple calls to action in a single message. One RCS message can carry several buttons, so a giving-day text could offer “Give now”, “Match a gift” and “Share with a friend” side by side, and a stewardship message could pair “RSVP” with “Add to calendar”. Each tap is a separate, trackable action.

The university plans to bring RCS into its program alongside SMS and MMS once onboarding is complete.


Nandhaan Verma
Nandhaan Verma
Nandhaan is a marketer with nearly 5 years of experience researching & writing about communication for nonprofits, advocacies, & political campaigns. His insights have empowered multiple organizations to streamline communications & drive change.