Texting Your Volunteers Without a Bulk Text Service

The roster is built. Now comes the part that decides whether it holds: getting every person to actually see their name, and getting an answer back from the ones who cannot make it.

A text is usually seen sooner than an email. So the deacon who builds the roster ends up texting people from his own phone, one at a time, typing the same sentence with a different date. It works, and it takes an evening. It also leaves no record of who was told what, and the answers come back as a scatter of thumbs-up emoji and "I think so" in a pile of different threads.

Why Not Just Use a Bulk Text Service?

Some congregations do. A bulk service is fast, but it brings its own questions. Whose number does the message come from? Who is allowed to be texted at all? What happens to the person who replied STOP last spring? And a message from an unfamiliar number to a widow who serves on the table committee is not the same as a message from a brother she has known for decades.

Many elders prefer the second kind. The message should come from a person in the congregation, on a phone the member recognizes. The problem was never the sending. It was the typing, the tracking, and the follow-up.

A Text You Press Send On

BetterGather's manual text queue is built around that preference. It prepares the messages; a person sends them.

From the schedule board you choose a range of dates, or from a project's People section you choose that project, and BetterGather prepares a message for each person who has been assigned but has not yet answered. You can also prepare the text for one assignment from the board, for example to send it again. Each message names your congregation, the role, the service, the date, and the time with the time zone, and ends with a personal reply link. You then send each one from your own phone, either from a prepared text link or by scanning a QR code on the screen with the phone you want to send it from.

Preparing the queue does not send anything, and BetterGather does not claim it did. Nothing leaves until a person presses send. After you do, you mark that assignment as handed off, and BetterGather records the message and the number it was prepared for. That entry means the text was handed to your phone. It does not mean the person read it.

Who the Queue Leaves Out, and Says So

When you prepare a range of dates or a project, the queue skips three kinds of people and reports how many of each it skipped:

Anyone who has opted out or been marked do-not-contact. If a member has asked not to be texted, the queue respects it every time, without anyone having to remember.

Anyone who has recorded that they are away on that date. This is the same time-off record the roster draft consults, so nobody is texted about a Sunday they already said they would miss.

Anyone with no usable phone number. They are counted rather than silently dropped, so you know to reach them another way.

That last count is worth reading. A roster that quietly skips the three people without numbers is a roster where those three never get told.

The Reply Link

Each text ends with a link to a short page with two buttons: one for yes, I will be there, and one for no, I cannot attend. The member taps one, and the answer is recorded against that assignment.

A few details matter here:

Opening the link does not answer for them. Phones and messaging apps often preview links in advance, and some mail scanners open them too. BetterGather records an answer only when the person presses a button, so a preview cannot accept a duty on someone's behalf.

The link expires. You set how long a reply window stays open for your congregation. A link opened after it closes says so, and you can prepare a single assignment again to renew it.

An answer cannot be flipped by the link. Once someone has said yes or no, the same link will not change it to the opposite. If a brother accepted and then learns he must travel, he tells whoever runs the roster, who changes it on the board. That is deliberate: a duty should not silently change hands because a link was tapped twice.

What Happens When Someone Says No

A decline is recorded at once, and the board shows it. When someone declines through their reply link, BetterGather then looks for a replacement and invites that person itself: by email, or by a text from BetterGather's own number when email is turned off or no address is on file. That invitation does not go through your phone. If you turn both the email and text channels off in your scheduling settings, the replacement is still placed on the roster but nobody tells them, so text them yourself from the board. A decline you record yourself, on the board or a project page, does not look for a replacement. To choose the replacement it considers the people who fit the role and are not marked away, skips anyone who has told you they are not available for that kind of duty, and does not pick someone who is already at their limit of duties for that day or already fills that role at that service.

Be aware of what it does not weigh. When it chooses a replacement it looks at fit for the role, and seniority if your settings use it, not how much the person has served lately, so look at a suggested replacement before you assume the load is fair. And if the commitment has been archived, the decline is recorded and nobody is invited in its place.

What It Will Not Do

The queue will not send for you. It exists so that a person sends. Publishing the roster, or sending a project's notifications, is the other way to invite people: BetterGather sends the invitations itself, by email or by text from its own number, through the channels turned on in your scheduling settings, and the replacement invitation above goes out the same way. If you want nobody to touch a phone, that is the path to use. It has its own rules, and it is not what this article describes.

It will not tell you a text was read. You will know it was handed off and whether the person answered. The unanswered ones are the list to work through by phone.

It will not settle your obligations about messaging members. Rules about consent and texting vary, and a congregation that texts its members should ask its own counsel what applies.

Where to Start

Pick one upcoming month. Make sure each person on the roster has a current phone number and that anyone who has asked not to be texted is marked that way. Prepare the queue, read the counts of who was skipped, and send the texts yourself in one sitting. Then check the board for who has answered, and call the rest.

The point is not to remove the personal touch. It is to keep the touch and lose the retyping, so the one who builds the roster spends the evening with the people who have not answered, rather than the ones who already have.