You automate nonprofit volunteer sign-up by putting a conversational agent in front of the registration conversation. It asks for their name, availability, and which program pulled them in one question at a time, types the answers into a structured record, and posts that record to your CRM before anyone re-types a Google Form.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
Someone who heard about you from a neighbor, a flyer, or a search result, usually on a phone, usually not during office hours.
What it costs today
A Google Form that dumps into a spreadsheet nobody checks until Monday, or a PDF sign-up sheet that asks the same six questions of a first-timer and someone who has volunteered for years.
What it has to produce
A typed volunteer record: who they are, when they can help, which program fits, and whether they have agreed to a background check.
35%
of volunteer sign-up forms started on a phone actually get finished, the device most people use to start
Feathery
| Field | Type | Required | Why it is there |
|---|---|---|---|
| full_name | text | Yes | Identity on the volunteer record |
email | Yes | How the coordinator follows up | |
| phone | phone | — | A faster way to reach back when timing matters |
| availability | text | Yes | Matches them to a shift that actually exists |
| program_interest | text | Yes | Routes to the right program team |
| prior_experience | text | — | Context for fit, never used to screen someone out |
| background_check_consent | boolean | Yes | Required before any shift with vulnerable neighbors |
| motivation | text | — | What brought them to the door, in their words |
And what it will not do
Collected data
148 collected19 this week5 need attention
Export CSVJordan Alvarez
Captured 1h ago · Volunteer Sign-Up · joina.chat
Captured data 7 of 8 fields
From the conversation
“My neighbor mentioned you need people to help sort donations, not totally sure how the background check part works , but I’d like to help out where I can.”
Every value keeps the sentence it came from, and a value the visitor never said is never stored. A Gnosari cannot quote itself into your data.
From here a record can go straight on to Slack, a sheet, a Zap or your own API. The inbox is where you read them, not where they get stuck.
Signed headers
Body
{
"type": "data.collected",
"event_id": "1b6f9c02-4d1a-4f7e-9b3c-2a5e8d0f1c44",
"created_at": "2026-08-11T09:14:22Z",
"payload_version": "v1",
"data_kind": "New volunteer",
"record_id": 1234,
"attributes": {
"full_name": "Jordan Alvarez",
"email": "jordan.alvarez@example.com",
"phone": "+1 512 555 0172",
"availability": "Every other Saturday morning",
"program_interest": "Food access, sorting donations"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when someone corrects something.
Signed, so you can trust it
Standard Webhooks HMAC-SHA256, with webhook-id, webhook-timestamp and webhook-signature on every request. Verify before it opens a record.
Quotes are opt-in
The provenance block, the person’s verbatim words, is absent unless you turn it on for that destination.
Zapier or Make
Paste a Catch Hook URL into your Gnosari destination, then point the Zap at your CRM.
Free tier, no app to install, and it fires the moment the record is complete.
Straight to the desk
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The coordinator sees the signup before the newsletter does.
Your own endpoint
Give us an https address, verify the signature, open the record yourself.
A few lines of code, and the delivery log tells you when something did not land.
And you can see every attempt
| When | Event | Outcome | Detail |
|---|---|---|---|
| 19:04:22 | data.collected | Delivered | 200 OK |
| 19:04:18 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 09:37 | data.updated | Delivered | 200 OK |
| Yesterday 07:52 | data.collected | Delivered | 200 OK |
Every attempt is kept, newest first, with the reason when there is one. Failures retry on their own, and the signing secret lives in your dashboard so you can rotate it without calling anybody.
These are examples, not a partner list. Salesforce Nonprofit Cloud, Bloomerang, DonorPerfect and Neon CRM are all reachable the same way: through a Zap, or straight to an endpoint you control. If it takes an HTTP request, it takes the record.
A button in the corner that opens into a conversation. Your logo, your colours, sitting on the pages you already have.
No chat window and no widget. Your headline leads, the thread sits under it, and it reads like you asked rather than like software collecting.
Every screen on this page is a published Gnosari, embedded from the app. Type into any of them.
display_mode="bubble" A floating button in the corner. Opens over your page and closes again. The default, and the one nobody has to be taught.
Four corners to choose from
display_mode="sidebar" A fixed panel down one side, always open. For pages where the conversation is the point rather than an aside.
Left or right, any width
display_mode="sidebar-push" The same panel, but your content moves over to make room instead of being covered. Nothing on the page is ever hidden.
Left or right, any width
display_mode="drawer" Slides in over the page when it is called, then slides away. The middle ground between a bubble and a sidebar.
Left or right
01 · A link you send
Put it in an email, a text, a booking confirmation or a signature. Each link carries its own opening line and headline, and counts its own visits, so you can tell which channel actually worked.
02 · A code they scan
Every link comes with a QR. On a table card, a receipt, a delivery note, a door. Someone points a phone at it and the conversation starts, with no app and no typing.
03 · A flyer you hand over
A builder for the printed thing itself. Pick a template, restyle it, edit the words on the page and export a print-ready poster or card with the QR already placed.
Twelve curated looks, each a colour and a background pattern chosen to go together. Pick one and you are done.
22 colour themes and 44 background patterns, each drawn in code at four intensities. That is 3,872 combinations before you touch a single token.
22 colour themes
44 background patterns
Every pattern, four intensities
Exact hex values, fourteen fonts, bubble shape per side, corner radius, density, header and input. Explicit tokens always win over the preset. Two chats can share every line of markup and still wear two different brands: only the tokens differ.
A boutique hotel
A developer tool
fontFamily accepts fourteen faces
Set with one call, or one click in the designer. Changing it later takes the same one call, and every published surface updates at once.
| What changes | Google Form → spreadsheet | Paper or PDF intake | Gnosari |
|---|---|---|---|
| After hours | Sits unread until Monday | Sits in a folder | Answered, typed, delivered |
| What you get back | Whatever fit in the boxes | Whatever they wrote by hand | The story in their own words |
| Half-told story | Nobody follows up | Re-typed into the spreadsheet | It asks the follow-up |
| Getting it into your CRM | Copied by hand, if at all | Re-typed from paper | Signed webhook, the moment it is complete |
| A neighbor asking for help | A form asking for proof | Screened at the door | Never means-tested, ever |
| The care line | Depends who reads the form | Not applicable | Never crossed, and stated at the start |
Everything you need to know about getting started. Can't find the answer you're looking for? Reach out to our team.
Gnosari runs the conversations a nonprofit handles today with sign-up forms and an overflowing inbox: the volunteer who wants to help, the person asking for a service, the donor with a question about their gift, the grantee with a report due. It asks one question at a time on your programme pages or through a link, then posts a typed record to your CRM, so staff spend their time on people instead of data entry.