Free Charity Program Explainer Bot: Explain, Then Convert

Most charity websites have the same structural problem: the programmes are explained on one page, the donate button is on another, and volunteering is buried three clicks deep. A visitor who arrives curious has to navigate to convert, and most of them do not.

The Charity Program Explainer collapses that into a single conversation. It opens with four doors — learn about our programmes, how to donate, volunteer opportunities, or impact stories — and lets the visitor move between them freely, because every branch loops back to a "would you like to learn about anything else?" question rather than ending. Somebody can read about your food security work, then ask about monthly giving, then check what volunteering involves, all without navigating anywhere.

That looping structure is what makes it a conversion tool rather than an FAQ. The visitor educates themselves in the order that suits them, and the donate and volunteer paths are always one answer away. Eighteen connected nodes, all editable text in the chatbot builder.

1. Welcome. "Welcome to our Charity Program Explainer! I'm here to help you understand our various charitable initiatives and how you can make a difference in our community."

2. The main menu. Four options stored in initial_interest: Our Charity Programs, How to Donate, Volunteer Opportunities, and Impact Stories. This node is the hub, and the flow returns to it repeatedly.

3a. Programmes branch. A second choice node offering Education Support, Healthcare Access, Food Security and Environmental Conservation, stored as program_interest. Each leads to its own explanation message covering what the programme does and what it has achieved — scholarships and mentoring, mobile clinics and essential medications, food banks and community gardens, cleanups and tree planting. The achievement figures in these messages are illustrative placeholders and must be replaced with your organisation's real numbers. All four rejoin the loop.

3b. Donate branch. A choice between a one-time donation, monthly giving, and sponsoring a programme, into donation_type. All three converge on a validated amount question — currency prefixed, between $1 and $1,000,000, stored as donation_amount — then an email capture for the receipt into donor_email, then a redirect node labelled "Proceed to Secure Payment" that sends the donor to a payment page. The redirect returns into the loop, so a donor can carry on exploring.

3c. Volunteer branch. A choice of volunteering type — on-site, remote support, special events, or skills-based — into volunteer_type, then a free-text question capturing specific skills and experience into volunteer_skills, then a select node for availability: weekday mornings, weekday afternoons, weekends, or flexible. That is a complete volunteer enquiry in three questions, and it rejoins the loop.

3d. Impact stories branch. A multi-select letting the visitor pick which stories interest them — student success, community health, food programme impact, environmental achievements — into story_interests, followed by a message introducing the stories. This node ships generic and is the one you most want to rewrite.

4. The loop. "Would you like to learn about anything else?" A yes returns to the four-option menu; a no closes with a thank-you and an invitation to get in touch. Because the loop sits after every branch, a single visitor can donate, register interest in volunteering and read two programme explanations in one session.

Multi-programme charities get the most from it, because the structure is designed around a visitor who does not yet know which part of your work they care about. Single-issue organisations can still use it by replacing the programme branch with sub-initiatives.

Foundations and grantmakers can use it to explain funding areas to applicants and the public. Community organisations and mutual aid groups get a full donate-and-volunteer front door without paying for a platform. Faith organisations and schools running several appeals at once can keep them all navigable in one conversation.

It also works well as a campaign microsite substitute: point an ad at a page with this widget on it and the whole explanation-to-action journey happens inside the chat.

Complementary flows in the same category: the Donation Process Guide handles giving in far more depth, the volunteer chatbot goes deeper on volunteer matching, and the non-profit foundation chatbot covers general enquiry handling. See everything at non-profit and charity templates.

1. Replace every statistic and every programme

The four programme descriptions contain invented achievement figures. They are there to demonstrate the pattern — a programme description that ends with a concrete result reads far better than one that does not — but they are not your numbers. Substitute your real programme names, your real activities and your real, verifiable results. A charity publishing borrowed statistics is a serious credibility problem, and it is trivially avoidable.

2. Point the redirect at your own payment page

The donation redirect ships with a placeholder link. Replace it with your own hosted donation page, a Stripe payment link, or your PayPal donate URL. This redirect pattern is the right one: keep card handling with the processor rather than in the conversation. Conferbot's Stripe integration is the alternative if you want the payment set up inside the flow.

3. Route the volunteer enquiries to a person

The volunteer branch captures type, skills and availability, then loops — which means a genuinely interested volunteer ends the conversation with nothing having happened. Add an email capture and send the details to your volunteer coordinator through the Gmail integration, log them to Google Sheets or Airtable, or add a live handover for people ready to start. Live chat handover and the unified inbox are included on every plan, including Free.

4. Write the impact stories properly

The story node is a single generic message, and the multi-select above it already tells you which stories a visitor wants. Branch it: one real, specific, named story per interest area. Stories move people in a way that programme descriptions do not, and this is the one node where writing effort converts directly into donations.

5. Send the data where your team works

Donation intent, volunteer profiles and story interests are all worth keeping. Google Sheets works for a small team, HubSpot and Zoho CRM for donor records, Notion or Airtable for campaign tracking, Slack for instant notification of a volunteer enquiry. For a donor database Conferbot does not connect to natively, Zapier reaches 2,000+ apps, or use a webhook to your own endpoint. Webhooks and API access require a paid plan; native app connectors and the widget work on Free.

6. Close the loop honestly

The donate branch collects an email for the receipt but the bot itself sends nothing. Either wire the Gmail node, or rely on your processor's receipt and make sure the wording matches what actually happens.

Suggested amounts with impact framing. Replace the open amount question with preset options labelled by what each buys — "$25 — a month of clean water for one household" — keeping a custom option. This is the single highest-impact change to the donate branch.

Add a "where does my money go" branch. Fifth menu option, one honest message about your cost ratio and how restricted funds work. Transparency questions are the commonest reason a considering donor hesitates, and answering them proactively converts.

Capture a name in the donate branch. The flow asks for an email but not a name, which makes the record harder to use. One node fixes it.

Offer the newsletter to non-converters. The "no, thank you" close is the end of the road for every visitor who did not donate or volunteer. An email capture there turns a bounce into a contact.

Add corporate partnership. Companies looking to sponsor a programme arrive on charity sites regularly and find nothing aimed at them. A branch capturing company name and a contact, routed to a handover, is small effort for a large potential gift.

Localise the programmes. If your work is geographically split, a location question at the top lets you show the programmes running near the visitor, which materially raises relevance.

Let people share. A redirect offering a prewritten share link at the end of the impact stories branch costs nothing and extends your reach through the people already moved by the story.

Channels are not gated by plan in Conferbot, so this flow runs on every surface your supporters use. The website widget is the primary home, and it belongs on more than the homepage — put it on programme pages, your about page and your campaign landing pages, where the visitor is already reading about the work.

Instagram and Messenger matter enormously for charity campaigns, because a moving post can open directly into the explanation-and-donate conversation instead of a link in bio. WhatsApp is the right primary channel for organisations working in regions where it is the default, and it suits supporter groups that already coordinate there. Telegram, Discord, LINE, Microsoft Teams and the mobile SDK are all available on any plan.

Design the donate branch redirect-first and it will behave correctly everywhere, including on messaging channels where asking anyone to enter payment details in-thread would be inappropriate.

The free plan includes 600 conversations a month and one chatbot — enough to run a real campaign and find out whether conversational explanation works for your supporters. Paid plans start at $19/month and add webhooks, API access and removal of Conferbot branding, which most charities want before a public appeal; Pro adds A/B testing for comparing two versions of a programme description. See pricing for the comparison.

Charity communication carries a higher standard than most marketing, and this template will be judged against it.

Every number must be yours and verifiable. The placeholder achievement figures in the programme descriptions are the biggest risk in the file. Replace them with results you can evidence in your annual report, and keep them current — a statistic from four years ago presented as present tense reads as carelessness at best.

Stories need consent. If you replace the generic impact story node with real beneficiary stories, make sure you have permission to tell them, and be careful with identifying detail. The people in your stories are not marketing assets.

Do not imply the chatbot processes the gift. It captures intent and hands over to a processor. Keep the redirect label honest and make sure the donor understands where they are going.

Respond to what you collect. A volunteer who tells you their skills and availability and then hears nothing is a supporter lost. Before launching, decide who reads the volunteer enquiries and how fast they respond, and then build the flow to promise exactly that.

Handled this way, the template does something a static site struggles with in 2026: it lets a curious visitor understand your work in the order they care about, and act the moment they are ready.