VBS Registration and Reminders: A Church Texting Guide

Vacation Bible School is most churches' single largest annual outreach: a week that can bring more first-time families through the doors than any other point in the year, powered by dozens of volunteers, hundreds of registrations, and a logistics load that would humble a small school district. It is also, operationally, a communication project, and the churches that run VBS smoothly have usually solved one problem the others have not: they stopped depending on email and paper forms, and started texting.

Here is the full VBS texting playbook: registration, volunteers, the week itself, and the follow-up where the real ministry outcome is decided.

Why Texting Fits VBS

The VBS audience is parents of young children, coordinating summer schedules from their phones, often connected to the church loosely or not at all. Registration links sent by text get opened; email announcements to unchurched families largely do not. And VBS communication is inherently time-sensitive, registration deadlines, day-of drop-off logistics, weather calls, which is exactly the terrain where SMS outperforms every other channel.

Two rules frame everything below. First, consent: automated texts require prior express consent under the Telephone Consumer Protection Act (47 U.S.C. 227), so collect phone numbers with clear texting language on every form ("By providing your number you agree to receive VBS updates by text; reply STOP anytime"), honor opt-outs instantly, and identify the church in each message. Second, children's privacy: VBS lists are lists of families with children; keep kids' details out of message bodies, message parents rather than children, and fold your texting into the same safeguarding policies that govern the rest of children's ministry, the framework in our guide to youth group texting policies applies directly.

Phase 1: Registration (6-8 Weeks Out)

The registration campaign is a funnel: announce, invite, remind, close.

The announcement, to the whole congregation list: "[Church]: VBS is June [dates]! Kids age [range] are invited for a week of [theme]. Registration opens Sunday: [link]. Spots go fast."
The community invitation. VBS grows through friends. Give your families a forwardable version: "Know a family who'd love VBS? Forward this: [Church] welcomes all kids [dates], free, register at [link]." A texted invitation from a friend is the most credible outreach a church has.
Deadline reminders, only to families who have not completed registration, segmentation, not blasting: "[Church]: VBS registration closes Friday, and [child's age group] is nearly full. Two minutes finishes it: [link]."
The confirmation, immediately on registering: "[Church]: [Child first name] is registered for VBS! Drop-off details, what to bring, and the week's schedule arrive the week before. Questions? Just reply."

Every message invites a reply, and replies must land somewhere staffed. An AI Powered Helper can answer the recurring ones, ages, times, cost, allergies process, while the children's director handles the rest. A registration question answered at 9 p.m. is a registration completed; one answered Thursday is a family that chose the other church's VBS.

Phase 2: Volunteers (Parallel Track)

VBS runs on volunteers, and volunteer coordination is its own texting program:

Recruiting: "[Church]: VBS needs you! Crew leaders, snacks, check-in, decorations, one hour or all week, there's a spot. Reply SERVE and we'll find your fit."
Scheduling and confirmations: shift assignments by text, with reply-to-confirm, and reminders the night before each serving day.
Training and screening nudges: background check completion and training session reminders, tracked to completion, because safeguarding requirements are non-negotiable and chasing them by announcement never works.
The during-week channel: a volunteers-only thread for daily briefings: "Crew leaders: doors at 8:15, rotation change today, station 3 and 4 swap. Rain plan is ON for rec time."

Phase 3: The Week Itself

Daily parent logistics, brief and predictable:

Night before day one: "[Church]: VBS starts tomorrow! Drop-off 8:45-9:00 at the [entrance], pick up at noon with your family code. Water bottle and closed-toe shoes, please. See you there!"
Daily notes, one per evening at most: what tomorrow brings, theme-day reminders ("crazy hat day!"), pickup changes.
Weather and safety calls: the moments texting exists for. "[Church]: Storms expected at pickup; we'll hold kids inside until a parent arrives at the door. Drive safely, no rush."
Security notes: pickup-code reminders and any check-in changes, with children's names kept out of broadcast messages.

Phase 4: The Follow-Up That Makes It Ministry

The week ends; the outreach outcome is decided in the following ten days, and this is where most churches drop the thread. A follow-up sequence for first-time families:

Day after: "[Church]: Thank you for sharing your kids with us this week, we loved every minute. Photos from the week: [link]."
The bridge invitation, a few days later: "[Church]: The fun doesn't stop at VBS! Kids' Sunday programming happens every week at [time], same joyful crew. We'd love to see [child first name] again this Sunday."
The personal touch for families who engaged deeply: a human text from the children's director, not a broadcast.

Families who respond flow into the church's regular communication rhythms, the welcome arc in our guide to church attendance follow-up texts, and the broader invitation cadence covered in church announcement text templates. Churches evaluating platform options for all of this, VBS plus the year around it, can start with our comparison of free church texting options.

The VBS Communication Calendar at a Glance

Timing	Audience	Message
8 weeks out	Congregation list	Save the date, registration opens Sunday
6 weeks out	Congregation list	Registration live, plus the forwardable invitation
6 weeks out, parallel	Whole church	Volunteer recruiting, reply to serve
4 weeks out	Incomplete registrations only	Deadline reminder by age group
3 weeks out	Confirmed volunteers	Training and background check completion
1 week out	Registered families	What to bring, drop-off and pickup detail
Night before each day	Registered families	Tomorrow's theme, timing, any change
As needed	Affected list only	Weather and safety decisions
Day after	All families	Thank-you and photo link
Within one week	First-time families	Bridge invitation to weekly programming

Edge Cases Worth Planning For

Waitlists. Age groups fill unevenly. A waitlist handled by text works well, one message on joining, one when a spot opens with a short reply window, and one honest close if it does not. Silence on a waitlist is what generates phone calls.
Allergies and medical needs. Collect them in the registration system, never in a text thread, and never restate them in a message. Staff who need the detail see it in the secure record at check-in.
Pickup authorization. Custody arrangements and authorized pickup lists live in the registration record. Broadcast messages should reference the family code process rather than any individual arrangement.
Teen volunteers. Minors serving as helpers need parental consent for texting, and messages to them should follow the same youth communication policy that governs every other channel. Our guide to consent rules for texting minors covers the framework.
Households that speak another language. A registration link a parent cannot read is a family who does not come. Per-family language delivery matters most for exactly the first-time families VBS exists to reach.
Registered but never arrived. A short, warm message on day one keeps the door open, and often surfaces a transport or schedule problem the church can actually solve.
Siblings across age groups. One message per family, not one per child, with the relevant detail for each group consolidated. Parents with three children should not receive three separate texts a night.
Photo and video consent. Whether images may be used, and where, is a registration question. The thank-you message with a photo link should only reach families whose recorded preference allows it.
Numbers collected for VBS only. A family who consented to VBS updates has not consented to a year of general church announcements. Ask before moving them, and say what they would be signing up for.
Volunteer no-shows on the day. A same-morning gap message to the volunteer list is what a group thread is for, and it works only if the thread was not used for anything trivial all week.

What to Ask Before You Pick the Platform

Can we run separate audiences, families, volunteers, and the general congregation, from one system with separate consent records?
Does registration status flow into segments automatically, so deadline reminders only reach incomplete registrations?
Can we deliver per family in the household's language, on outbound messages and replies?
Do replies land somewhere a team can share, with routing to the children's director for anything sensitive?
How fast can an urgent weather message go out, and is it queued behind routine sends?
How are stop requests honored across every list, including the volunteer thread?
Can we lock message templates so children's names and medical detail cannot be added by accident?
Are staff and volunteer personal numbers kept private?
Can we export contacts, consent, and message history when the week is over?
What is the cost pattern for a seasonal spike, and does the plan assume year-round volume?

Frequently Asked Questions

How early should VBS registration texting start?

Open the campaign six to eight weeks before VBS: announcement, then the forwardable community invitation, then deadline reminders targeted only at incomplete registrations. The confirmation text should fire the moment a family registers, because instant confirmation is what stops the "did it go through?" calls.

Do churches need permission to text VBS families?

Yes. Automated texts require prior express consent under the TCPA, so every registration and interest form should include clear texting-consent language, every message should identify the church, and STOP must work immediately. Numbers collected for VBS should not be repurposed to unrelated campaigns without that consent covering it.

What should never go in a VBS text?

Children's full names, medical or allergy details, and anything that identifies a specific child to a broadcast audience. Message parents, keep kids' specifics in your secure registration system, and handle sensitive follow-ups person to person.

How do churches handle VBS weather cancellations?

By text, immediately, to exactly the affected list: the decision, what happens to drop-off or pickup, and when the next update comes. This single use case, urgent, time-bound, universally needed, is why the VBS list belongs on SMS rather than email.

What follow-up works after VBS ends?

A thank-you with photos the day after, a concrete bridge invitation to weekly children's programming within the week, and a personal, non-broadcast text to families who engaged deeply. The follow-up window is short; ten days later, the moment has cooled.

Can churches text teen volunteers directly?

Only inside your youth policy, and generally with parental consent recorded first. Practical patterns that keep this clean include including a parent on scheduling messages, using a group thread rather than one-to-one adult-to-minor conversations, and running all of it on the church platform so the record exists.

How should a church handle a VBS waitlist by text?

Confirm the waitlist spot immediately so the family stops wondering, then send one message when a place opens with a clear and short reply window, and one honest message if the week fills. Keeping the age group in the segment lets you fill openings in minutes instead of working down a printed list.

VBS Week, Minus the Chaos

FRANSiS runs the whole arc, registration funnels, volunteer coordination, daily logistics, and follow-up, with consent handled properly and an AI Powered Helper answering parent questions at all hours. Contact us to get set up before registration opens.