COVID-19 Vaccine Hesitancy Chatbot: answering the questions you answer every day
Look at your inbox for a week and you will find the same handful of questions. Those are the ones worth automating, and only those.
- 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
Inbound messages are matched against intents, answered where the answer is known, and handed to a person the moment they are not.
Visual, editable flows for appointments, screening questionnaires, waitlists and guided conversations. In practice, COVID-19 Vaccine Hesitancy Chatbot is the version of that we deploy when a business needs the result rather than a project. The foundation is maintained by Twilio itself, which is the strongest signal a sample will still work next year. That matters more than it sounds: the failure modes have already been found by someone else, in public.
Why businesses ask for this
Some processes change monthly. Building those in a visual flow means your team can adjust the wording and the branching without a developer in the loop.
The people who get the most out of it: clinics, councils, schools and teams whose scripts change often.
- Front-line staff can change the script themselves
- Multi-step conversations that remember where the customer is
- One flow serving SMS, WhatsApp and voice
How we build it, step by step
The sequence below is the one we follow on every automated conversation build. It is deliberately boring, because the interesting version is the one that breaks in month three.
- Mine the last few hundred real messages for the actual top questions
- Answer only what you can answer correctly every time
- Make the handover to a human obvious and one step
- Review the unanswered queue weekly and grow the coverage
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
Visual flows sprawl if nobody owns them. We version the flow, keep it in source control and give you a staging number to test on.
The technical foundation
Twilio Studio for the flow, Twilio Functions for the logic steps, and a deployment pipeline so changes ship safely.
- 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:
Upstream last updated 2026-06-30.
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 COVID-19 Vaccine Hesitancy Chatbot 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 Studio for the flow, Twilio Functions for the logic steps, and a deployment pipeline so changes ship safely. 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: COVID-19 Vaccine Hesitancy Chatbot. If you want to talk it through against your actual process, a scoping call is 30 minutes and costs nothing.