Answer supporter and beneficiary questions on a small team
Charity teams are small and the enquiry volume is not. Both donors and the people you serve need answers, and both usually need them outside office hours.
No credit card. Live in an afternoon.
What a charity actually gets asked
Both columns matter. The right-hand one is what a reader is really checking for, so it is on the page rather than in a footnote.
Answered from your own pages
The reply is the answer, with a link to the page it came from.
- “Can I claim Gift Aid on this?”
- “How do I set up a monthly donation?”
- “Am I eligible for your support?”
- “What does volunteering involve?”
- “Where does my donation actually go?”
Handed to a person
Declined plainly, then routed with the whole conversation attached.
- “I need help today — who can I speak to?”
- “Can you cancel my standing order?”
Each of these arrives with the whole conversation attached, so whoever picks it up starts from what the customer already said rather than from a one-line message.
Two audiences, one very small team
Nonprofits serve supporters and beneficiaries at once, with completely different questions, on a headcount set by what could be justified against programme spend. Enquiry handling is the first thing to be squeezed and the worst thing to get wrong.
- Donation and Gift Aid questions take time from programme work
- Volunteers ask the same eligibility and process questions repeatedly
- People seeking help need answers when the office is closed
- Every hour on admin is an hour not spent on the mission
You have already written most of it
Point the crawler at these four and the assistant has what it needs. There is nothing to re-author, and nothing to keep in sync afterwards.
- 01
Ways to give
One-off, monthly, Gift Aid, payroll giving.
- 02
Who we help
Eligibility and how to access support, in plain language.
- 03
Volunteering
Roles, commitment, how to start.
- 04
Impact and reports
What you publish about where money goes.
Supporters and beneficiaries, both served
Donation methods, tax treatment, where money goes, volunteering requirements, service eligibility, and how to access help. All published, all repeated constantly, all answerable with a citation.
- Donations and tax
- How to give and how tax relief works, quoted from your own material.
- Volunteering
- Requirements, checks, and process, answered before an application starts.
- Access to services
- Eligibility and next steps, available at the hour someone is looking.
- Sensitive cases escalate
- Anything needing a person routes to your team with the conversation.
Careful with vulnerable users
Where an organisation serves people in difficulty, an assistant must be unambiguous about its limits. The refusal behaviour matters more here than anywhere: it should hand over quickly and visibly rather than attempt to handle a situation that needs a trained person.
Multiply a small team
The point is not to replace anyone. It is that a team of three can cover the enquiry volume of a team of eight for the published, repetitive share, and spend the difference on the work only people can do.
Open when the office is not
People seeking help rarely need it during office hours.
Two audiences, one team
Supporters and beneficiaries both get an answer without splitting staff.
Careful by default
It declines rather than improvising, which matters most with vulnerable users.
Admin hours back
Every repetitive answer handled is an hour returned to the work itself.
It is not a crisis service, and it should never look like one
This is the deployment decision that matters. An assistant answering eligibility and process questions is genuinely useful; the same assistant meeting someone in distress is not. It refuses and routes, and the route you configure should be a real one.
- Giving, eligibility and volunteering questions: answered from your pages
- Anyone who needs a person is handed to one, immediately and plainly
- Nothing about an individual's donation or case is visible to it
- Conversations are stored, so a coordinator can review what was said
Put a crisis route in the widget copy and in the handover, not only in the assistant's answers. The refusal is only as good as what sits behind it.
What a charity asks first
Short answers. If yours is not here, the assistant on this page will try it — and tell you honestly if it cannot.
Is this appropriate if we support people in crisis?
Not as a front line for crisis contact. Configure it for published, practical information and make the route to a trained person prominent and immediate. An assistant should never be the thing standing between someone in difficulty and a human.
Can it take donations?
No. It answers questions about giving and points people to your donation flow. It does not process payments.
Can we control what it costs?
Yes, and this matters on a charity budget: a hard daily reply cap and per-visitor rate limits mean the ceiling is set in advance and cannot be exceeded by a traffic spike.
Keep reading
All solutionsFrom the blog
All posts- BuildingClinics: when fluent answers are unacceptableFor clinics and health-adjacent sites, AI support must refuse outside published admin facts. Fluency without grounding is unacceptable.Read
- BuildingAgencies: one bot, many client knowledge basesHow agencies should run AI support across clients: separate knowledge bases, domain locks, and evaluation per property.Read
- BuildingLocal services: hours, areas, and the lies maps createFor local service businesses, ground AI support on your published hours and service areas — not on whatever maps currently invent.Read
Answer honestly. Capture the rest.
Point Matter Chat at your site and see what it can — and can't — answer. It's honest about both.
No credit card. 2 minute setup.
Every answer cites the source it came from. When there isn't one, it says so — and hands the visitor to you.
Installs on the tools you already run.