23 docs tagged with "acceptance"

Layer 3 acceptance spec defining what every plan × role combination sees in the admin dashboard at /admin/[token]. Supersedes per-tier admin-dashboard sections for all plans.

APPROVED — Stage 1 agent research, pre-populated from the AI Front Desk Provisioning handoff (2026-05-21), the eight locked Phase-0 founder decisions, the AI Front Desk and Local Authority offer pages, the voice-agent code (resolve_route, the funeral/vet vertical pattern, moderation.py), the chatbot stream route, and the confirmed `local_business_*` production schema, then resolved in the founder Stage-2 interview (2026-05-21). Defines the EXPECTED OUTPUT — what a caller, a website visitor, and the business owner experience — for the per-business AI voice agent and website chatbot that the AI Front Desk + Local Authority packages promise. The voice agent is the church-built, multi-tenant, LIFE-SAFETY-tier LiveKit agent (one deployed agent serves church / funeral / vet / local-business). All 16 decisions (8 Phase-0 architecture/scope + 8 Stage-2 resolutions) are folded in; CLAUDE.md Rule #17 is satisfied — the customer-facing build is cleared.

What a customer experiences when they cancel their subscription — in-dashboard flow, emails, service during remaining period, post-service state, reactivation

What a ChurchWiseAI Pro Website customer sees at every touchpoint — distinct from the legacy PewSearch path

What the founder sees in the Outreach Engine dashboard about how a cold-outreach prospect engaged with their demo — viewed, chatted, clicked a conversion CTA — so follow-up targets the demos that actually landed.

What customers see and can do at every state of the per-church email-domain-verification flow in the admin Settings tab. Shipped 2026-05-12 (FA-107 v2).

Layer 3 of the knowledge system — per-tier specs defining exactly what a customer sees at every touchpoint

What customers see and can do when composing or replying to an Inbox item via email, SMS, or internal note. Shipped 2026-05-11/12.

What an IllustrateTheWord Premium customer sees at every touchpoint — discovery through working product

What customers see at every touchpoint of self-serve add/remove/resume product flows, with industry-standard UX rationale

What a Pro Website customer sees and does when adding a small number of separate pages (About, Ministries, Sermons, Contact, etc.) to their one-page site — the page model, the public render, the editor, and the draft/publish flow.

What a PewSearch Premium Page customer sees at every touchpoint — discovery through working product

What a PewSearch Pro Website customer sees at every touchpoint — discovery through working product

What a Pro Website customer sees and does when connecting their Planning Center / Church Center calendar to their site so the Events section auto-syncs. v1 = iCal feed.

What a Pro Chat or Suite Chat customer sees at every touchpoint — discovery through working product. Combined spec; differences called out inline.

What a Pro Both (Voice + Chat bundle) customer sees at every touchpoint — discovery through working product

What a SermonWise Pro customer sees at every touchpoint — discovery through working product

What a Starter Both (Voice + Chat bundle) customer sees at every touchpoint — discovery through working product

What a Starter Chat customer sees at every touchpoint — discovery through working product

What a Starter Voice customer sees at every touchpoint — discovery through working product

What a Suite Both (Voice + Chat bundle) customer sees at every touchpoint — the top-tier plan

What a customer sees when their chat plan trial expires without payment — dashboard state, emails, re-subscribe flow

Expected outputs across every touchpoint for VetWiseAI tenants — Discovery, Pre-Purchase, Email, Dashboard, Voice Agent, Public-Facing, Ongoing, and Lifecycle. Two tiers (Starter/Pro). Sales-led product with self-serve checkout as secondary path.