FAQ
Frequently asked questions.
Edi pulls from your unified data warehouse, applies the role-based access controls configured for you, and answers in plain language. For a question about attendance, that's a structured query against your church's data. For a more open-ended question, Edi pulls patterns across multiple systems and synthesizes a response.
Edi grounds every answer in your actual data, not generic AI. When Edi cites a number or describes a trend, it can show you the underlying records. When Edi can't answer something with confidence, it says so rather than guessing.
Edi acts when you ask it to. It can draft a summary, start an initiative, or set up an alert — but always in response to your request, and you see exactly what it created. Edi never sends a message, changes a record, or contacts a member without you deciding to.
Each church's data lives in its own isolated store within a private cloud environment that meets enterprise security and compliance standards. We can share specific provider details and our SOC 2 status under NDA during evaluation.
No. Your church's data is contractually never used to train AI models, build features for other churches, or shared with any third party. This is a non-negotiable foundation, not a configurable setting.
Role-based access controls, configurable per role per church. The same controls apply across every surface — the Console, your AI tools, and push channels. The senior pastor's view, the finance director's view, the campus pastor's view, all enforced by the same access layer.
Typical timeline is 2 to 4 weeks from kickoff to first meaningful insight, depending on how many source systems you connect and how complex your terminology configuration is. Our team handles the integrations and configuration; your team's involvement is limited to credentials, walkthroughs of your operating model, and review of the configured outputs.
Reach out. Our integration roadmap is partner-driven, and we prioritize systems based on what our active churches use. Most major church management and giving platforms are either supported today or actively being added.
No. Edi works through the AI tools your team is already paying for. If your team has Claude Pro, ChatGPT Plus or Team, or a Cursor seat, that's all you need on the AI side. The Ediphai connector itself is included with your Ediphai subscription.
No. The B2B platform stands alone — a church can subscribe purely for the unified data, Edi, and the Console and find it worth the cost. The mobile app is an additive layer that deepens what Edi knows when your members opt in.
No. The raw text stays with the member, always. What flows to the church is the structured signal layer — gifts, growth season, engagement patterns, next-step indicators.
Yes. We're happy to walk through architecture, security, data handling, and integration approach with your CTO, IT director, or technical evaluator. Bring them to the demo or schedule a separate technical session.
Let's talk
Let's talk about your church.
We'll learn about your church, walk through how Ediphai could fit alongside your existing systems, and answer any questions.