Launching an SMS program
Texting is the fastest way to reach a list and the fastest way to burn it. This is how to stand a program up so the first send is one you trust and the hundredth is still welcome.
Decide what the program is for
Before any of the mechanics, answer one question: what should a recipient do because of this message? Programs drift into "keeping people updated", which is another way of saying nobody decided. Pick one of:
- Recruit – get a reply that turns into a shift or an RSVP.
- Persuade – open a conversation and record where the person actually stands.
- Mobilise – a specific action on a specific day.
The answer changes the copy, the send window, and how many organisers you need on replies.
Get the sending set-up right first
Choose the from-number deliberately. Replies land back on the number you send from, so the number is part of your routing plan, not an afterthought. One number per program is usually right; one number for the whole organisation stops being workable the moment two programs run at once.
Understand your opt-out obligations before the first send, not after the first complaint. Uprise runs an automated opt-out compliance check as part of the send and keeps a ledger so anyone who opts out is excluded from every future send across the account. That is the floor, not the whole job – see Compliance and opt-outs.
Write it like a person
A text that opens "Hi FIRSTNAME" is worse than no text. Use personalisation tags so the message assembles per recipient, then read it the way a recipient will:
- Use the live preview. Watch the message build as you type, on both channels, so you catch a tag that didn't fill before ten thousand people do.
- Send yourself a proof. A real message to a real phone. Line breaks and truncation look different on a screen than in a compose box.
- Read it out loud. If you would not say it to someone at a bus stop, rewrite it.
Keep the first message short enough to be read in one glance and end it with something a person can answer. A question gets replies; an announcement gets opt-outs.
Size the first send to your reply capacity
This is the mistake almost everyone makes once. A big send produces a lot of inbound, fast, and the replies are where the value is. If you have three organisers free for two hours, do not send to ten thousand people.
Work backwards. Estimate a reply rate, divide by how many conversations an organiser can hold at once, and send the number you can actually answer. Then send again tomorrow.
Run the replies as a team
Put every inbound into the shared inbox rather than a dozen personal phones. The queue is claimable, so two organisers never answer the same person, and releasing a conversation hands it back cleanly when someone needs to escalate or hand over.
Set the room up before the send, not during it:
- Agree who claims what.
- Agree what gets escalated and to whom.
- Turn audible alerts on so nobody is staring at a silent screen.
- Agree the three or four replies you will send most often, and wire them as canned replies.
After the first send
Look at four numbers: delivery, reply rate, opt-out rate, and what proportion of replies produced the thing you wanted. An opt-out rate that jumps is the list telling you the message was wrong for it – change the message, not the volume.
Then keep the cadence honest. A program people expect is a program they tolerate; a program that surprises them every time is one they leave.