Onboarding process for volunteers
Built on a no-code platform: Manychat, SendPulse, or similar
Small & Medium Businesses
Information Architecture
Information Architecture
Information Architecture
Information Architecture
Information Architecture
Information Architecture
Information Architecture
Information Architecture
☎️ Your time:
✨ My time:
🫰Price:
2–4 weeks
~4–6 hours
9–13 hours
€270+
"Every new volunteer asks the same questions. And every time, someone from the team has to stop and answer them."
Client's qoute
Problem
A new volunteer arrives with the desire to help, but doesn't always understand where to start, what's expected. This uncertainty doesn't look like a crisis. It shows up quietly: the person gradually loses interest, or simply stops responding.
In many nonprofits, onboarding is informal: a new person gets a quick walkthrough. But knowing how to do the work is not the same as knowing how to explain it.
The coordinator carries everything. Usually there's one person who knows how it all works and through whom every newcomer passes. This works as long as that person is around. But if they go on leave, get sick, or burn out — the knowledge that was never written down leaves with them.
Every new person means starting over. The same explanations, the same links, the same questions. When two or three new volunteers arrive per month, the coordinator starts spending as much time on introductions as on the actual work.
My Role
I'll help turn the knowledge scattered in heads and chats into a clear path for a new volunteer: from day one to the point where they can work independently.
If you already have onboarding materials:
I'll review: what's current, what's outdated, what's missing
I'll help with restructuring content for the bot
Then — building the bot:
Designing the scenario: a step-by-step path through the first days
Linking all materials: where documents live, what's for what, contacts, instructions
FAQ section — so that routine questions stop pulling the coordinator and team away from work
Testing with a real newcomer and adjusting based on feedback
A handbook for your team: how to update the bot when things change
Your Part
Participation in the kickoff meeting: goals, who joins the organization, how onboarding works now
Share existing materials: documents, instructions, links, contacts — everything you have, in any format
Access to people involved in onboarding or hold knowledge needed for the bot
Willingness to rethink the current process: some things may be done out of habit and no longer needed
Participation in testing: checking the bot with a real newcomer
Subscription to the no-code platform (if needed)
The hardest part is gathering what's currently scattered. Instructions buried in chats, rules in the coordinator's head, links lost in messages. You don't need to prepare everything perfectly, just share what you have, and I'll help organize it.
Result
A new volunteer goes through their first days with a clear guide and can find the information they need on their own, even months later.
You get:
A bot in your chosen messenger with a step-by-step scenario for newcomers
A structured knowledge base: documents, instructions, contacts — linked to stages
An FAQ section that takes routine questions off the coordinator and the team
A handbook: how to update the bot when things change
Full access handover: the bot, the platform, all settings — everything stays with you
The coordinator is no longer the only person holding all the knowledge — the information lives in a system, not in one person's head.
Follow-up session two weeks after launch — to discuss how the first real onboarding through the bot went and what needs adjusting.
I'd also suggest thinking about:
Meeting the team in person.
The bot will handle the routine — "where's the document," "who do I message," "what comes first." But a new volunteer still needs to feel the atmosphere and meet people. It's worth planning at least one live meeting or call in the first days.
Keeping materials up to date.
The bot works with what's been put into it. If instructions become outdated over time, the bot will deliver outdated instructions. I'll show you how to update it, and it's straightforward — but it's worth deciding early who on the team will be responsible for that.
Mentorship
The bot helps with information, but it doesn't replace a person who can answer unexpected questions or offer support. If you don't yet have a mentorship practice for newcomers, this is a good reason to think about one. We can discuss it separately.
Frequently asked questions:
Do you also write the texts?
You know the content — I'll help with structure, format, and presentation. If you need help with the writing itself, we can discuss it as an additional task.
Can we add video to the bot?
Yes, the bot can send videos, images, and infographics. If you already have materials like these, we'll build them into the scenario. If they need to be created, we can discuss that as an additional task.
Who maintains the bot after launch?
I'll hand over a guide and answer your questions. After that, the bot is yours. If you need ongoing support — content updates, new scenarios, technical maintenance — we can arrange that separately.
What if we don't have any materials?
That's fine. We'll start with conversations with your team and together extract what currently lives in people's heads. It may take a bit more time, but it's not an obstacle.
You might also find useful:
All-in-one Database in Google Sheets
Collecting data manually from scattered folders and formats often leads to outdated results and repetitive tasks, making it difficult to reach timely decisions based on the most current information.
Learn more
Onboarding process for volunteers
Built on a no-code platform: Manychat, SendPulse, or similar
Learn more
Donation page
Integration with donation service depending on your geography, currency, and organisation type.
Learn more
