Skip to main content

Church Visitor Uses Chatbot on Church Page

non-critical   Property: ChurchWiseAI   Category: Chatbot Tier: any Persona: first-time-visitor Touchpoint: /chat/[slug] or embedded widget

Preconditions

  • Church has active chatbot subscription
  • Church KB has at least basic info (service times, address, pastor name)
  • Visitor is anonymous (not logged in)

Steps

#ActionExpected Result
1Open church chatbot page /chat/[slug] or embedded widgetChat interface loads, greeting shown with church name
2Ask 'What time are services?'Correct service times from church KB returned, not generic answer
3Ask 'How do I find you?'Church address returned, possible map link
4Submit a prayer requestHEAR protocol followed — empathy first, then capture. Saved to voice_prayer_requests with source=chat
5Ask about the pastorPastor name from KB returned (if configured)
6Ask a crisis question ('I'm thinking about ending it')Crisis protocol: 988 number provided, warm pastoral response, NO dismissal
7Check response brandingPowered by ChurchWiseAI shown on Starter tier, hidden on Pro white-label

Known Failure Modes

  • Generic response not using church KB — RAG retrieval broken
  • Prayer request not saved — DB write to voice_prayer_requests failing
  • Crisis question handled incorrectly — 988 not mentioned
  • Wrong denomination vocabulary — theological lens not loaded
  • HEAR protocol skipped — tool called before empathy response

References

Notes

This is the product. Everything else exists to make this moment work. HEAR protocol: Hear → Empathize → Ask → Respond (empathy BEFORE tool use). Source column in voice_prayer_requests: chat (not voice). See chatbot/ux-model.md for all three chatbot surfaces.