# The connection card becomes a typed member record by Sunday.

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.

## The process this page is about

Not "AI for churches". One process, the one that decides whether a first-time visitor becomes a second-time visitor: the follow-up that has to happen before the 48-hour window closes.

- **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.
- **more likely to return when someone reaches them within 48 hours - most churches reach out days later**: 75% (source: EvangelismCoach)

## What it asks, and what it never asks

You name the fields your connection card already has. It does the asking, in whatever order the story comes out, and it keeps asking until the required ones are filled.

| Field | Type | Required | Why |
|---|---|---|---|
| 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 | no | Routes a wedding or funeral enquiry to the right pastor |
| is_a_member | boolean | no | Feeds the eligibility question a pastor answers, never a ruling made in chat |
| date_needed | date | no | The date a booking or service needs, checked by a real person |
| areas_of_interest | text | no | Matches a volunteer to a real opening, not a form into the void |
| availability | text | no | When a volunteer or family can actually be reached |
| last_time_here_estimate | text | no | A gentle estimate, never a tracked attendance record |

### And what it will not do

- It never offers scripture, a devotional thought, or spiritual advice as a response to what someone shares.
- It never counsels, and never assesses anyone’s spiritual, emotional or mental state.
- The moment anything sounds like a crisis, it stops asking questions and says plainly to call 911 or local emergency services right now.
- It never confirms a date is available or quotes a fee for a wedding, a funeral, or a hall booking.
- It never says whether a request will be approved. A pastor decides, and always follows up personally.
- It never invents a field. If they did not say it, the record says "Not captured" instead of a guess.

## Try the run yourself

Six situations a church office actually handles, each running its own agent with its own fields. Pick one and answer it the way a real visitor, volunteer, or family would, out of order and mid-thought, and watch it ask the follow-up instead of accepting the blank.

- [I just visited](https://joina.chat/l/wc-newcomer): Chat widget. The connection card, replaced, right on your site.
- [Something’s wrong today](https://joina.chat/l/wc-prayer): Conversation page. Share what’s going on and watch it stop and say call 911 now.
- [Do you marry non-members](https://joina.chat/l/wc-wedding): Conversation page. Wedding and funeral eligibility, qualified before a pastor calls.
- [We need your hall](https://joina.chat/l/wc-hall): Conversation page. An event already decided, the logistics captured.
- [I’d like to help out](https://joina.chat/l/wc-volunteer): Conversation page. An offer of time, matched to a real opening.
- [It’s been a while](https://joina.chat/l/wc-welcome): Conversation page. No guilt, just help finding the way back in.

## Frequently asked questions

**What does Gnosari do for a church or religious organisation?**

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.

**How do I follow up with visitors who fill in the connection card?**

Create a free Gnosari account and tell it which fields your connection card already has: name, how they heard about you, whether they want a call, the ministries they are curious about, contact. Put the link or QR code on the card, the screen and your website. Gnosari runs the conversation, asks whether a follow-up is welcome and how, and posts the record to Planning Center or Breeze through a webhook, Zapier or Make. The welcome team calls on Tuesday with the card in front of them.

**Will Gnosari give spiritual counsel or answer a doctrinal question?**

No. Gnosari is instructed never to counsel, never to interpret scripture or doctrine, and never to offer an opinion on a personal or spiritual matter. It records the request in the person's own words and passes it to the pastoral team. A prayer request agent works the same way: it collects the request and the level of confidentiality wanted, and never adds a comment of its own. If anything sounds like a crisis, it stops and says plainly to call emergency services or the pastoral line now.

**Can Gnosari register children for an event and collect allergies and consent?**

Yes. A separate Gnosari agent collects each child's name and age, allergies and medical notes in the parent's words, the emergency contact, who is allowed to collect the child and the consent your policy requires, one child at a time so nothing gets merged. It never decides whether a child can attend or whether an allergy is manageable: it flags anything medical for the coordinator. The record reaches the check-in team before the morning starts.

**Does Gnosari work with Planning Center or Breeze?**

Yes, through a webhook. The moment a record is complete, Gnosari posts a signed JSON payload to the address you give it, and Zapier or Make routes it into Planning Center, Breeze or the church management system you already run. There is no Gnosari app to install on either side, and the record is already in your Gnosari inbox before delivery starts, so a down endpoint never loses a visitor or a prayer request.

## Five minutes from now your connection cards could be typing themselves.

Build the agent, put it on your site, and watch the first record arrive. Free to start, no card.

Full page: https://gnosari.com/for/religious