Skip to main content

ChurchWiseAI — Chat assistant feature page

Decision (John, 2026-10-06): build a feature page for the chat assistant that sells the Website ($29/mo) and Complete ($99/mo) plans. Context: the 2026-10-06 search audit found product-intent queries such as "church chatbot", "ai chat for churches" and "chatbot for church website" had no landing page since /chatbot began 308-redirecting to /pricing on 2026-09-24 (chat is no longer a standalone SKU, see cwa-three-plan-pricing.md). The redirect was correct for the old product page; the new page is a feature page, not a SKU page.

Route and redirects​

  • New page: /chat in the (cwa) segment of churchwiseai-web. Indexable, in the churchwiseai.com sitemap, in llms.txt.
  • /chatbot and /ai-chatbot 308 to /chat (replace the current /chatbot → /pricing redirect in next.config.ts; keep the explanatory comment and update it to this spec).
  • Header "Products" navigation gains "Chat assistant" pointing at /chat; the Phone page and the Pro Website page each link to /chat where they mention chat.

What the page says (truth bar: every claim verifiable in product_knowledge or the chatbot code)​

  1. Hero. H1: "A chat assistant for your church website". Sub: it answers visitors 24/7 in your church's own voice, takes prayer requests and callback requests, captures visitors who want to be contacted, and hands anything pastoral to a real person. Two buttons: "Start free trial" (to /pricing) and "See it live" (to /demo). Pricing line: "Included in Website ($29/mo) and Complete ($99/mo). 14-day free trial. No setup fee." Same numerals in USD and CAD, no currency toggle, never the retired converted prices.
  2. What it does (six cards, each a real capability): answers questions from the church's own pages and uploaded documents; service times, directions and events; prayer requests routed to the prayer team; "have someone call me" callback requests; visitor contact capture (name, email, phone) for follow-up; knows when to stop and hand off to a human (the AI Bridge Principle, quoted from architecture/ai-bridge-principle.md).
  3. What it will not do. It is not a counsellor or pastor: in a crisis it gives the church's crisis contacts and 988 and connects the person to a human. State this plainly; it is a selling point.
  4. Set up in an afternoon. Three steps: pick a plan, paste one line on your site (or it is already on your Pro Website), teach it from your pages and documents in the dashboard (FAQ management, document upload, training simulator, Planning Center integration are Pro-level features all three plans include per the pricing spec).
  5. Which plan. A two-column comparison: Website = Pro Website with the chat assistant built in; Complete = that plus the AI phone line. One line noting Phone ($79) also includes the same chat widget for a church keeping its existing site, so the page never hides a plan. Buttons go to /pricing.
  6. FAQ (6 to 8 items, FAQPage JSON-LD built from the same data): does it work on Wix/Squarespace/WordPress (yes, one script tag); what languages; what happens to prayer requests (dashboard + email, role-gated); who sees transcripts (admin and office admin only); can we change its tone; does it replace a person (no, bridge); how is it trained; what does it cost (the two plans).
  7. Schema: Service (name "ChurchWiseAI Chat Assistant", provider Organization ChurchWiseAI, offers the two plan prices as Offer in USD) + FAQPage + BreadcrumbList, emitted with the existing cwa JSON-LD helpers.
  8. Copy rules: no invented numbers (no "X churches", no "99% accuracy"); no "Delivered/Opened"-style theatre; founder voice; one named testimonial only if it already exists in product_knowledge or on /, otherwise none.

Acceptance checks (on https://churchwiseai.com, real host)​

  1. /chat returns 200 with the H1 above; /chatbot and /ai-chatbot 308 to /chat (curl -I with a browser User-Agent; churchwiseai.com returns 403 to bare curl).
  2. The page states exactly $29 and $99 (and $79 once in the plan note) and no other price; no currency toggle; both trial buttons land on /pricing.
  3. JSON-LD on the page parses and contains Service, FAQPage (Question count = visible FAQ count) and BreadcrumbList.
  4. Sitemap lists /chat; llms.txt mentions it; header nav shows "Chat assistant" on phone and desktop widths.
  5. Lighthouse mobile performance ≥ 70 and accessibility ≥ 95 (the home page is at 46 performance today; the new page must not inherit that: no autoplay video, images sized).
  6. product_knowledge has a row answering "do you have a chatbot / chat assistant page" that points at /chat; validate_product_knowledge() shows no CRITICAL/WARNING after the insert.
  7. Playwright click-through on the deployed URL: load /chat, click "Start free trial", assert /pricing; click "See it live", assert /demo.

Out of scope​

Changing plan prices or entitlements; a standalone chat SKU; any change to /api/chatbot/*; the voice page.