6 docs tagged with "hear"

Canonical rules for what the ChurchWiseAI chatbot and voice agent must always and never do — derived from battle-tested prompt fragments, the HEAR protocol, and the Safety Covenant

APPROVED — pre-populated from the 2026-06-08 four-agent examination (voice-agent audit, admin/data-model audit, cited best-practice research, QA acceptance audit) and three founder decisions (2026-06-08): (1) spec-then-build phased, (2) refer-first / capture-only-if-already-tried, (3) available on ALL agent tiers (chat + voice), then resolved in the Stage-2 founder interview (2026-06-08 — all open questions closed). Defines the EXPECTED OUTPUT — what a caller / chat visitor, the church benevolence team, and the church admin experience — when a person asks the church for food / money / shelter / rent / utility help (reportedly ~50%+ of church inbound). The model is REFER-FIRST: point callers to vetted local agencies + 211 first; capture for a human benevolence team only when the caller has already tried those; the AI NEVER decides worthiness. CLAUDE.md Rule #17 is SATISFIED — the build is cleared.

Design for deferring empathy-sensitive tool execution so HEAR protocol is structurally enforced in chatbot responses

4-email cold outreach sequence for church prospects in the ChurchWiseAI outreach engine. HEAR protocol, CASL/CAN-SPAM compliant.

Step-by-step verification for the ChurchWiseAI church cold outreach pipeline — from scrape to prospect interaction to booking.

Stage 1 DRAFT — pre-populated from code and production research by an agent. Every touchpoint must be confirmed or corrected by the founder in a Stage-2 interview. No production deployment decisions should rely on this file alone.