You automate church visitor follow-up by putting a conversational agent in place of the paper connection card. It asks for a name, a way to reach them, and what brought them, one question at a time, types the answers into a member record, and delivers it to your team before the 48-hour window closes.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
Someone who visited for the first time, or is thinking about it, usually filling out a card during the announcements or reading the website from the parking lot before they walk in.
What it costs today
A stack of connection cards, some illegible, sitting on a desk until the one staff member who handles follow-up gets to them, days after the 48-hour window that decides whether anyone comes back has already closed.
What it has to produce
A typed record: their name, how to reach them, what brought them, and whether they would like a call, a text, or simply to be left to visit again on their own terms.
75%
more likely to return when someone reaches them within 48 hours - most churches reach out days later
EvangelismCoach
| Field | Type | Required | Why it is there |
|---|---|---|---|
| full_name | text | Yes | Who to welcome back, by name |
| phone | phone | Yes | How the connections team calls back |
| whats_bringing_them | text | Yes | The reason they reached out, in their own words |
| request_in_own_words | text | Yes | The prayer or pastoral care request itself, never our summary of it |
| service_type | text | — | Routes a wedding or funeral enquiry to the right pastor |
| is_a_member | boolean | — | Feeds the eligibility question a pastor answers, never a ruling made in chat |
| date_needed | date | — | The date a booking or service needs, checked by a real person |
| areas_of_interest | text | — | Matches a volunteer to a real opening, not a form into the void |
| availability | text | — | When a volunteer or family can actually be reached |
| last_time_here_estimate | text | — | A gentle estimate, never a tracked attendance record |
And what it will not do
Collected data
142 collected18 this week3 need attention
Export CSVMaria Alvarez
Captured 1h ago · Newcomer Connection · joina.chat
Captured data 6 of 8 fields
From the conversation
“I came last Sunday because a friend from work invited me, and I genuinely don’t know what to do next , is there a smaller group or something I could try?”
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 visitor connection",
"record_id": 1234,
"attributes": {
"full_name": "Maria Alvarez",
"phone": "+1 704 555 0132",
"whats_bringing_them": "Visited last Sunday, a friend invited her",
"how_they_heard": "A friend from work",
"interested_in_next_step": "Wants a call, mornings work best"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of record. 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 file.
Quotes are opt-in
The provenance block, the visitor’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 church database.
Free tier, no app to install, and it fires the moment the record is complete.
Straight to the office
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The connections team sees the visitor 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 |
|---|---|---|---|
| 08:14:02 | data.collected | Delivered | 200 OK |
| 08:13:41 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 19:22 | data.updated | Delivered | 200 OK |
| Yesterday 09:03 | 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. Planning Center, Breeze ChMS, Church Community Builder and Realm 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 | Paper connection card | Group text or email chain | Gnosari |
|---|---|---|---|
| After the service | Sits on a desk until Thursday | Whoever saw the text first, maybe | Answered, typed, delivered |
| What you get back | A scribbled name, if legible | Whatever fit in the message | The reason in their own words |
| A prayer request | Passed hand to hand, or lost | Forwarded to the wrong group | Routed to the right person, privately |
| Half-told story | Staff call back to ask | Nobody follows up | It asks the follow-up |
| Gets into your church database | Re-typed by hand | Not at all | Signed webhook, the moment it is complete |
| The pastoral line | Depends who answered | 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 church handles today with a connection card, a clipboard and a Monday morning of data entry: the visitor who wants to be welcomed, the member asking for prayer, the family registering children for an event, the volunteer offering time. It asks one question at a time on your website or through a QR code in the bulletin, then posts a typed record to your church management system.