Skip to main content

"See How ChurchWiseAI Serves YOUR Tradition"

Concept​

A section on the marketing/demo page with a tradition selector dropdown. When a visitor selects their tradition, they see SPECIFIC examples of how the chatbot behaves for their tradition — what it says, what it NEVER says, and what it knows about their care structures.

The emotional goal: "They built this for ME."

This is the moment a priest/pastor/minister stops comparison shopping and starts trusting. Generic church AI companies show the same demo to everyone. We show each tradition a mirror of their own pastoral world.

Implementation​

UI Component​

  • Dropdown or visual selector with tradition icons/names
  • 3-panel display:
    1. "What your chatbot says" (bridge language example)
    2. "What your chatbot NEVER says" (tradition-specific avoids)
    3. "What your chatbot knows" (tradition-specific intelligence)

Data Source​

Pull directly from tradition_care_context table — the same data that powers the actual product IS the marketing demo. This means the demo is always accurate to what the product actually does.

Examples by Tradition​

Roman Catholic​

Your chatbot says: "Please call the parish right away — we want to make sure Father can come to be with them for Confession, Anointing, and Viaticum. This is what the Church is here for."

Your chatbot NEVER says:

  • "Accept Jesus into your heart" (evangelical framing)
  • "I'll pray for you" (that's Father's role, not the AI's)
  • "Divorced Catholics can't come to church" (false — they ARE welcome)

Your chatbot KNOWS:

  • Confession is a sacrament — only a priest can hear it
  • Anointing of the Sick is for the seriously ill, not just the dying
  • The Eucharist is the Real Presence — never "symbolic"
  • Divorced ≠ excommunicated

Southern Baptist​

Your chatbot says: "Pastor [Name] would love to sit with you through this. Your Deacon Family Minister is also here for you."

Your chatbot NEVER says:

  • "Father" (wrong title — it's "Pastor")
  • Language suggesting illness means lack of faith
  • Liturgical/sacramental language that doesn't fit

Your chatbot KNOWS:

  • Deacon Family Ministry Plan structure
  • Lord's Supper is an ordinance, not a sacrament
  • Eternal security theology shapes salvation conversations

Church of Christ​

Your chatbot says: "Your minister and the elders would love to talk with you about that."

Your chatbot NEVER says:

  • "Pastor" (they use "Minister" or "Preacher")
  • "Your denomination" (they're not a denomination)
  • "Baptism is symbolic" (it's when salvation occurs in this tradition)

Your chatbot KNOWS:

  • Plural eldership — never a single authority
  • Lord's Supper every Sunday without exception
  • A cappella worship is doctrinal, not stylistic
  • Each congregation is fully autonomous

Seventh-Day Adventist​

Your chatbot says: "Your pastor or one of our elders would love to connect with you. Our Health Ministries team walks alongside people through this."

Your chatbot NEVER says:

  • "Your loved one is in heaven now" (SDA believes in soul sleep)
  • "They're watching over you" (contradicts their theology)
  • Anything assuming Sunday worship

Your chatbot KNOWS:

  • Sabbath is Friday sundown to Saturday sundown
  • The health message is theological, not dietary preference
  • No alcohol, no pork — these aren't cultural, they're convictional
  • Ellen White is a revered prophetic voice

Eastern Orthodox​

Your chatbot says: "Please call Father immediately — he will want to come and offer Holy Confession, Holy Communion, and Holy Unction."

Your chatbot NEVER says:

  • "Pastor" (always "Father")
  • "The Bible alone" (Holy Tradition is equally authoritative)
  • "Personal relationship with Jesus" (faith is communal and liturgical)

Your chatbot KNOWS:

  • The 40-day mourning period with Panikhida on days 3, 9, and 40
  • Closed communion — non-Orthodox receive blessed bread (antidoron)
  • The priest's wife (Matushka/Presbytera) is a pastoral figure
  • Orthodox divorce ≠ Catholic annulment

Unitarian Universalist​

Your chatbot says: "I hear that you're going through something hard. Your minister would love to walk alongside you."

Your chatbot NEVER says:

  • "God loves you" (can't assume theism)
  • "They're in heaven now" (no consensus afterlife belief)
  • "I'll pray for you" (prayer isn't universally meaningful here)
  • "Sin" language (many members left traditions that weaponized this)

Your chatbot KNOWS:

  • No creed required — members range from atheist to Christian
  • Full LGBTQ+ affirmation since 1970
  • "Holding in the light" replaces "praying for you"
  • Child dedications, not baptisms

Pentecostal​

Your chatbot says: "I'll make sure our prayer ministry team and Pastor [Name] know about this."

Your chatbot NEVER says:

  • Spiritual warfare language (even though the church uses it)
  • "If you had more faith, you'd be healed" (documented harm)
  • Formal liturgical language

Your chatbot KNOWS:

  • Prayer ministry teams and altar workers are key care structures
  • Holy Spirit language is central but the AI doesn't speak it
  • Anointing with oil (James 5:14) is practiced

Mennonite​

Your chatbot says: "This community takes care of its own. Your pastor and care team would want to know."

Your chatbot NEVER says:

  • "God and country" (pacifism is non-negotiable theology)
  • "Sacrament" (Mennonites say "ordinance")
  • Infant baptism language (believer's baptism only)

Your chatbot KNOWS:

  • Mutual aid is theology, not a program
  • Foot washing is a sacred ordinance in many congregations
  • Military service is theologically complicated in this tradition
  • Community discernment > individual pastoral authority

Why This Works as Marketing​

  1. Emotional recognition — clergy see their own world reflected accurately
  2. Trust signal — "if they got THIS right, they'll get everything right"
  3. Competitive differentiation — no other product can show this
  4. Self-qualifying — the right customers instantly know this is for them
  5. Shareable — a Baptist pastor will share this with other Baptist pastors saying "look, they actually get us"

The Trust Cascade​

Clergy member sees tradition-specific demo → Thinks "they understand my tradition" → Trusts the product more than any generic competitor → Signs up for trial → Sees their chatbot actually behave this way → Tells other clergy in their network → Word of mouth in denominational circles

The Data Source IS the Product​

Critical architecture insight: the demo page pulls from the SAME tradition_care_context table that powers the actual chatbot. This means:

  • The demo is always accurate to what the product does
  • Adding a new tradition automatically updates the demo
  • Marketing and product are the same thing