An agentic platform built around your church, not a model.
1Stayz combines swappable AI models, connectors to the tools churches already use, and a guardrail layer each church controls. Here’s how the parts fit together.
Platform architecture
Connectors
Your system stays the record
Your church tenant
Isolated per church with row-level security
Guardrail layer
Decides what may be said
- Your doctrine and wording
- Topics routed to a pastor
- Crisis routing, always on
- One question, short texts
- Quiet hours, STOP / HELP
- Pastor-approved versions
Fast model
Open-weight, high-speed. Everyday replies in seconds.Swappable by benchmarkReasoning model
Frontier model for theology and escalation judgement.Swappable by benchmarkYour pastor
Alerted in about a minute. 15-minute response goal. Assistant stays paused.Two models, two jobs.
Every message passes through your guardrails first. Then the router picks the right model for the moment: a fast open-weight model for everyday questions, a frontier lab model for the sensitive ones, or a real person.
- “What time is kids’ check-in?”
- “How is your church’s view on baptism different?”
- “Is there parking near the side entrance?”
- “My mom went into the hospital last night.”
- “Can I bring my sister on Sunday?”
Toward a Christian-aligned model, built with churches.
Frontier models learn from the whole internet. We’re building 1Stayz-Base: an open-weight model adapted for church care, grounded in historic Christian theology and refined with consented, de-identified patterns from real church follow-up. Patterns, never people.
Consented conversation
Hi, I’m Sarah. My mom is at St. Luke’s tonight. Could someone pray for us?
Only from churches that opt in
De-identified
Hi, I’m [NAME]. My [FAMILY] is at [HOSPITAL] tonight. Could someone pray for us?
Two passes plus human spot checks
Pattern record
guest shares family illness
→ assistant pauses
→ pastor replies in 6 min
→ guest returns Sunday
Patterns, never transcripts
1Stayz-Base
Released only after every gate passes
Opt-in only
Only churches that consent contribute, and a church can stop contributing at any time going forward.
Patterns, not people
No raw transcripts, names or contact details ever enter training. De-identified records can’t be traced back to a person.
Your doctrine still decides
1Stayz-Base learns how to care well. Your guardrails still decide what your assistant may say about your beliefs.
Gated releases
Training begins only once at least three churches consent, and each release must pass extraction tests and an independent privacy review.
1Stayz-Base is on our roadmap and isn’t part of the pilot. During the pilot, no church data is used to train models.
What makes 1Stayz different.
Your church decides what may be said
Doctrine, approved wording, topics that always go to a pastor, tone and sign-off. Guardrails are versioned and pastor-approved, and crisis routing can’t be turned off.
Works with the tools you already use
Church apps and ChMS (Subsplash first, more coming), connection cards and QR forms, SMS and email. Your system stays the record; 1Stayz runs the follow-up.
One person, one ongoing conversation
Every visit has one thread across SMS and email. The assistant remembers recent turns and what the guest has shared, so no one has to start over.
People for people moments
Escalations reach your team in about a minute with a 15-minute response goal. Staff replies go into the same thread, and the assistant stays quiet until released.
Every church in its own space
Each church’s data, knowledge and guardrails are isolated with row-level security and separate search indexes. No church’s data shapes another church’s conversations.
Baseline and real lift
See first-contact speed, reply rates, escalation response times and returning guests against your own starting point.
The details, for your tech team.
| Area | How 1Stayz handles it |
|---|---|
| First contact | Scheduled from your service times: within 30 minutes after the scheduled end of the service the guest attended, in the guest’s channel. |
| Threading | Canonical model: Person → Relationship → Visit → Thread → Participants. Inbound messages attach by conversation and email headers, never by phone number alone. |
| Agent memory | Live turns for the current visit, a durable store of facts the guest shared, and a short working context, so prompts stay small and focused. |
| Models | Fast open-weight model for everyday conversation and orchestration; frontier reasoning model for theology-sensitive review and escalation judgement. Chosen by benchmark, swappable. |
| Guardrails | Church-configured, versioned and pastor-approved. Changes apply without a redeploy. Crisis routing always on. |
| Messaging rules | Registered two-way SMS, STOP and HELP honored mid-conversation, quiet hours in the guest’s time zone, email-first fallback. |
| Data isolation | Per-church tenancy with row-level security, separate vector namespaces, tenant-keyed caching and ID-only logs. |
| Network insights | 1Stayz sees only consented, de-identified aggregates with small-group suppression. Never individual people. |
| Your data | Your church system stays the record. Export of your church’s copy is part of the agreement. |
Every guest known by name. Every pastor freed for people.
We're welcoming a small group of pilot churches. Pilot churches help shape 1Stayz and get hands-on setup with our team.