Skip to main content
  • Home
  • >
  • COVID-19 Vaccine Hesitancy Chatbot

COVID-19 Vaccine Hesitancy Chatbot

By Twilio

  • COVID use case
  • Studio
  • SMS
  • Twilio
  • Quick Deploy
  • Social Impact
  • Applications

Interactive chatbots have been studied to have a positive impact on COVID-19 vaccine attitudes and intentions. For organizations working to increase vaccine confidence in populations you serve, this template provides an interactive chatbot platform that can answer individuals' vaccine-related questions.

Individuals ask their questions by sending an SMS to a pre-configured phone number, and are responded to by a FAQ chatbot which is built using trusted data sources for answers. The chatbot is powered by Google Dialogflow ES and Twilio Studio flow connects the chatbot with Twilio’s Programmable SMS channel. The application can be extended to other digital channels such as Voice, Whatsapp or Webchat.

The chatbot template includes 2 pre-built chatbot agents: 

  1. An agent trained the on American Medical Association's COVID-19 vaccine FAQ for US audiences.
  2. An agent trained on the India Ministry of Health and Family Welfare's COVID-19 vaccine FAQ for Indian audiences

1. Configure Google Cloud Platform and Generate JSON Auth Key

Follow this guide for step-by-step instructions on how to do this.

This template uses Google Cloud Platform and Dialogflow to power the conversational chatbot agent that interacts with the user. You will need to setup a Google Cloud project, enable the Dialogflow API, and generate a JSON authentication key from a GCP Service Account for Twilio to use to interact with Dialogflow.

2. Create a Dialogflow Chatbot Agent

Follow this guide for step-by-step instructions on how to do this.

The conversational chatbot is powered by an integration between Twilio and Google Dialogflow, a natural language understanding platform used to design and integrate a conversational user interfaces. You may import the pre-built Dialogflow chatbot agents included in this repository, or configure your own chatbot agent.

3. Confirm completion of prerequisite steps

Before moving onto the Quick Deploy section, please make sure the following is true:

  1. You have an active Google Cloud Project with the Dialogflow API enabled
  2. You have a JSON authentication key associated with a Service Account from your Google Cloud Project, and you have the file handy (you'll need it below)
  3. You have created a Dialogflow agent and configured it either using one of the pre-built agents or have created your own
Launch and test this app in a few minutes with Quick Deploy. No server needed. Quick Deploy will automatically configure and deploy this app using Twilio Functions. Learn more about Twilio Functions
Step 1:Log in to Twilio
Step 2:Set up your application
This application requires a Twilio-supplied phone number to work properly.
Get a Twilio phone number
You will get a US number that is configured for this application. You can change this or port over an existing number later.International number regulations
Step 3:Deploy your application and try it out!
Deploy this application
This will use the details entered above to deploy your application to Twilio Functions. You will be able to view the application in the browser and edit it using the Functions UI. Learn more about Twilio Functions
Deploying applicationThis might take up to a minute
Success! Your application has been deployed.
Oops...something went wrong. Retry
Step 4:View and edit your application
Once deployed, any changes to the fields above will not be applied to your app. To make changes, here are two options
Refresh the page, edit customizations and re-deploy the application
Edit your customizations directly in code
Why use Quick Deploy?
No coding required to launch
Easy to edit and iterate post launch
No server management
Scales automatically
Secure by default

Don't see what you want? Request a code sample Explore Docs

Questions about scaling, pricing, or which products/features to use? Get a consultation

There was an issue loading the page.

Please try again in some time.