Connect Volunteers through SMS: reaching everyone at once without breaking the rules
Sending one message to many people is easy. Doing it with real consent, clean delivery and replies that land somewhere useful is the actual job.
- 19:41Message in, after hours: “do you do emergency callouts?”
- 19:41Matched against the questions you actually get asked.
- 19:41Answered instantly, in your wording, with the callout fee.
- 19:43Follow-up is outside what it is allowed to answer.
- 19:43Escalated to a human with the whole thread attached.
What it actually does
A list is maintained with real consent, a message is sent to many at once, and replies come back to one place instead of a hundred.
WhatsApp business messaging, group conversations, chatbots and session handling on the channel your customers already use. In practice, Connect Volunteers through SMS is the version of that we deploy when a business needs the result rather than a project. The foundation is contributed by a developer in the community, which usually means it solves a real problem someone actually had. That matters more than it sounds: the failure modes have already been found by someone else, in public.
Why businesses ask for this
For customers who live in WhatsApp, an SMS is an interruption and a phone call is worse. Meeting them on the channel they chose lifts response rates without extra effort from your team.
The people who get the most out of it: businesses with international, hospitality or community-based customers.
- Conversations that keep their history instead of restarting each time
- Common questions answered instantly, the rest handed to a human
- One business identity across chat, SMS and voice
How we build it, step by step
The sequence below is the one we follow on every broadcast and subscriptions build. It is deliberately boring, because the interesting version is the one that breaks in month three.
- Build the consent record first, with timestamp and source
- Honour STOP, START and HELP automatically and immediately
- Throttle sending so you do not trip carrier filtering
- Report on delivery, not just on send
What we change before it goes live
A reference implementation is a starting line, not a product. Every one we deploy gets the same treatment:
- Your numbers, your sender identity and your wording, so nothing reads as generic
- Secrets moved out of the code and into managed configuration
- Retries, rate limits and idempotency, so a hiccup never sends twice
- Structured logging and alerting, so a failure is noticed by us and not by a customer
- Consent, opt-out and record-keeping built in rather than bolted on
- Source control, a staging environment and a rollback that takes a minute
Compliance and risk
WhatsApp enforces a 24-hour customer service window and pre-approved templates outside it. We handle template submission and design the flow so you rarely need one.
The technical foundation
Twilio's WhatsApp Business API access, a conversation state store, and template management we maintain for you.
- javascript — Node.js, which is where most of this ecosystem lives and where we default unless you have a reason otherwise.
The open-source starting point sits here, and it stays public whether you work with us or not:
What it costs
Three ways to buy this, and the honest recommendation is usually the middle one:
- Starter build, from $2,500 — we build it, hand it over and warrant it for 30 days. Suits a business with someone technical in-house.
- Managed, from $390/mo — we build it and then own it: monitoring, changes, compliance upkeep and a monthly report. Suits everyone else.
- Platform, from $2,400/mo — when this is one of several systems and you want them designed as one layer instead of five.
Platform usage is billed at cost on top and itemised on the invoice. There is no margin on it and no minimum spend.
Common questions
How long does Connect Volunteers through SMS take to build?
For a standard configuration, about a week from kick-off to a staging number you can test on, then a few days of live monitoring before we call it done. Anything involving a port of an existing phone number adds one to two weeks of carrier time that nobody controls.
What does it cost to run each month?
Two lines: our managed plan from from $390/mo, and platform usage billed at cost. Usage for this kind of system usually lands between $30 and $300 a month depending on volume. You see both itemised, and the platform account stays in your name.
Do we own it, or are we locked in?
You own it. The account, the numbers, the phone history and the source code are yours, and the foundation is open source. If you take it in-house, we hand over the repository and the runbook and that is the end of the conversation.
What if it breaks at 6pm on a Friday?
It is monitored. Failures raise an alert, the system degrades to something safe rather than silent, and hello@betr.agency is the inbox that answers. That is what the managed plan buys.
Can it work with the systems we already use?
Usually yes. Twilio's WhatsApp Business API access, a conversation state store, and template management we maintain for you. Where a system has no API, we look at whether an export, a shared inbox or a scheduled sync gets you 90 percent of the value for 10 percent of the cost.
Where to next
The product page for this build lists the specification, the timeline and what is included: Connect Volunteers through SMS. If you want to talk it through against your actual process, a scoping call is 30 minutes and costs nothing.