Here's the thing nobody tells you until you've lived through one: on Giving Tuesday, you are not the only nonprofit with a 9:00am "The campaign is live! Give now 👉" scheduled. You're one of tens of thousands. And every one of those messages is trying to push through the same carrier networks, at the same minute, over 10DLC numbers that each have a hard ceiling on how fast they can send.
So two things collide. Your own number's throughput cap, the per-second and per-day limits the carriers assign your registered campaign, and the general network congestion of the single busiest texting hour in the nonprofit calendar. Fire everything at 9:00am and you don't get a bang. You get a trickle that's still crawling out at 10:45 while your donate page was designed for a 9:05 spike.
Full disclosure: I work for Ready, an SMS platform. We built throughput visibility and schedule-aware sending partly because we watched nonprofits run into exactly this wall every late November. So I have a horse in this race. The physics, though, are the same on any platform.
Two different ceilings, and they stack
People conflate "throughput" into one number. There are really two limits doing the throttling, and they behave differently.
Messages per second (TPS). Your 10DLC campaign gets a per-second rate assigned per carrier based on your brand's trust score. A standard registered brand often sits somewhere in the low double digits of TPS to T-Mobile. That number decides how fast a blast drains. We walk through the arithmetic in Your 50,000-Contact Blast Takes 4 Hours, the short version is that even a healthy TPS turns a big list into a multi-hour drip.
Daily message cap. Separately, a standard brand registration caps your total daily volume to T-Mobile at 3,000 messages a day unless you've done external vetting. Blow past that and the rest silently queues or gets filtered. We broke that number down here, vetting can lift it past 200,000, which is the difference between "my appeal landed" and "my appeal queued past lunch."
On Giving Tuesday both ceilings matter at once, and the network is congested on top of them. Your well-behaved blast is competing for carrier capacity with everyone else's well-behaved blast.
What the 9am collision actually looks like
Say you've got 24,000 opted-in donors and a standard (unvetted) brand. You schedule one blast for 9:00am sharp.
- Your daily cap to T-Mobile is 3,000. Roughly a third of US mobile numbers are on T-Mobile/Metro, so call it ~8,000 of your list. You can only deliver 3,000 of them that day. The other ~5,000 don't bounce, they just never go.
- The AT&T and Verizon portions drain at your assigned TPS, which during the congested 9am window may back off further.
- Your "instant" send is still working through the queue past 10:30. Your email team sent at 9:00 too, your social posts went at 9:00, and your donate page traffic peaked at 9:10, before most of your texts arrived.
Nothing in that scenario is a bug. It's the system working as designed. The mistake is treating a daily/per-second-limited channel like it's a broadcast email.
Stage the send across the day, don't fire it at the bell
The fix isn't a bigger blast. It's spreading the same volume across the hours you've actually got, so you never ask the carrier for more than it'll give you in one gulp.
A workable Giving Tuesday schedule for a mid-size list:
- 8:00am, warm segment. Your most engaged recent donors, the people most likely to give on the first touch. Smaller batch, early, before congestion peaks.
- 9:30am, main broadcast, batch one. The bulk of your list, split so the T-Mobile portion stays inside your daily budget.
- 12:30pm, midday reminder to non-openers/non-donors. Different copy, lunch-break timing.
- 4:30pm, "we're $X from goal" push. The urgency text, when people are deciding how to end their day.
- 7:30pm, final-hours appeal. The match-deadline close.
That structure does three useful things at once. It keeps each batch under the per-send throughput you can actually move, it spaces your daily-cap consumption instead of spending it all by 9:05, and it hits donors at multiple decision moments instead of one. Just mind your frequency, four or five touches in a day is near the edge of where donors start blocking you, so segment hard and stop texting anyone who's already given.
If you want the full capacity-planning version of this, we wrote a dedicated piece: the throughput plan that keeps your appeal from queuing past midnight.
Quiet hours will clip your late sends if you let them
Here's a trap on the back half of the day. TCPA quiet-hours rules, and Ready's enforcement of them, hold sends outside permitted local hours based on the recipient's area. That's a feature; it keeps you out of trouble. But if you schedule a "final hours" blast for a national list at a time that's already past 9pm on the East Coast, those recipients get held, and now part of your closing appeal doesn't land on Giving Tuesday at all.
Plan the evening batch against the latest time zone you care about, not your own clock. If you're sending nationally, your true "last call" window closes earlier than you think. A send that's held is a send that missed the moment.
Get the daily cap raised before late November
If your list is big enough that 3,000/day to T-Mobile is going to bottleneck you, don't discover that on December 2nd. Brand vetting is a one-time $79 (Standard) or $179 (Enhanced) upgrade that raises your trust score and daily throughput. It's not worth it for small senders, standard 10DLC ($10/mo brand + $20/mo campaign) covers most nonprofits fine, but if you're pushing 20,000+ in a day, it's the clearest spend on the list.
The one thing you can't do is rush it. Vetting and registration take days to approve. File in October, not the week of.
Watch the throughput, don't guess at it
The reason staging fails for most teams is they can't see what's happening. The blast goes out, the dashboard says "sending," and they have no idea whether messages are flowing or piling up in a queue.
Ready surfaces throughput so you can watch a batch actually drain and know whether to release the next one. Combined with schedule-aware, quiet-hours-respecting sends, that's the practical toolkit: see the ceiling, send under it, stage the rest. And because the full platform (inbox, automations, the GHL two-way sync) is included rather than priced per seat, your whole war-room team can watch the same send without per-user fees stacking up.
On cost, so you're not guessing there either: a 160-character appeal (one GSM-7 segment) to 24,000 donors on Standard is 24,000 × ($0.02 + $0.0045) = $588. Add an emoji and you've dropped to a 70-character limit, which splits that one segment into three unicode segments and triples the bill to ~$1,764 for the same send. On your highest-volume day, the emoji isn't free. Run your own numbers here.
The practical takeaway
Giving Tuesday breaks nonprofit SMS not because the message is wrong but because everyone treats a rate-limited channel like a broadcast one. Your 10DLC number has a per-second ceiling and a daily cap, the carrier is congested at 9am, and firing everything at the bell guarantees a stall.
So: vet your brand early if you're high-volume, split the list so each batch stays under what the carrier will move, stage sends across the day's real decision moments, and plan your evening batch against the latest time zone before quiet hours clip it. Then watch the throughput instead of hoping.
If you want to see what your Giving Tuesday send would actually cost and how it'd stage, the pricing and calculator are a reasonable place to start, no pitch, just the math. Get the plan drafted now, while there's still time for registration to clear.