Skip to main content

Knowledge > Products > FuneralWiseAI

FuneralWiseAI Overview

What It Is

FuneralWiseAI is an AI phone answering service for funeral homes. When a grieving family calls a funeral home — day or night — the AI answers, takes information with warmth and discretion, and forwards the call to a funeral director only when it matters. It is the first commercial vertical built on the WiseAI platform outside of churches, and the proof point for the WiseAI Agency multi-vertical thesis.

The pitch: "Never miss a call from a grieving family — even at 2am."

Status

FieldValue
Domainfuneralwiseai.com (hostname rewrites to /funeralwiseai/* in churchwiseai-web)
Codebasechurchwiseai-web/ (shared, not a fork — routes under src/app/funeralwiseai/)
StatusLive marketing + demo; paid customers TBD (launch vertical)
Voice agentShared LiveKit deployment (cwa-voice project) with funeral-home-specific prompts and tools under voice-agent-livekit/verticals/
Deploy branchmain → Vercel (same as churchwiseai.com)

Positioning

Tone: Warm, professional, reverent — never religious. Funeral homes serve families across every faith tradition and none; the brand voice is pastoral in care but denominationally neutral.

Palette: Slate + bone + copper (distinct from ChurchWiseAI's navy/gold).

Value proposition trio (from page.tsx):

  1. Always answers. 24/7, on the existing number, no hold music, no voicemail. Forwards to the director only when it matters.
  2. Trained for your funeral home. Not a generic script — trained on services, prices, chapel names, staff, and local details during a live onboarding interview.
  3. Built by a pastor. Founder John Moelker has 15 years of pastoral care plus CPE and Stephen Leader training. FuneralWiseAI is pastoral care training expressed as software.

Pricing

ComponentAmountNotes
Setup fee$999 one-timeCovers onboarding interview, agent training, integration, test-call review. Non-refundable after go-live.
Subscription$199 / monthUnlimited calls, 24/7 answering. Cancel anytime.
Guarantee30-day satisfactionIf cancelled within 30 days of go-live, first month refunded. Setup fee is not refunded (work already delivered).

Canonical source: knowledge/data/pricing.yaml (verticals section). Live page: funeralwiseai.com/pricing.

Unit economics reference: Average funeral arrangement generates $8,000–$15,000 in revenue. One missed call easily justifies a full year of FuneralWiseAI. This is the headline ROI argument on the homepage.

Pages (site map)

RoutePurpose
/funeralwiseaiHome — hero, value-prop trio, 4-step how-it-works, pricing callout, founder story, CTA
/funeralwiseai/how-it-worksHEAR protocol applied to funeral homes, call flow, integration, privacy
/funeralwiseai/pricing$999 + $199/mo detail, FAQ, 30-day guarantee
/funeralwiseai/aboutFounder pastoral story, HEAR protocol origin, CPE / Stephen Leader credentials
/funeralwiseai/bookDemo request form (POSTs to /api/contact with source=funeralwiseai)

All routes are middleware-rewritten from funeralwiseai.com/* so the site appears as its own domain.

The HEAR Protocol Applied

The same H.E.A.R.™ pastoral framework (Hear, Empathize, Address, Refer) that underpins ChurchWiseAI's voice agent is the spine of FuneralWiseAI — rewritten for a funeral-home context:

  • Hear — let the caller say what happened before asking questions. No interrupting. No rushed menus.
  • Empathize — acknowledge loss with brief, dignified language. Never "sorry for your loss" as a scripted phrase; always context-appropriate.
  • Address — answer the operational questions the family needs answered tonight (can we come in tomorrow? what do we need to bring? does the funeral home take our insurance? is there a chapel?).
  • Refer — when the conversation exceeds what the AI should handle (arrangement details, billing edge cases, clergy requests), warm-hand off to a director.

This is the vertical's competitive moat: every other funeral-AI product is a generic answering service. FuneralWiseAI is designed by someone who has sat with grieving families for 15 years.

Technical Architecture

FuneralWiseAI shares the entire ChurchWiseAI stack:

  • Frontend: Next.js 16 routes under src/app/funeralwiseai/ in churchwiseai-web. No separate codebase.
  • Brand scoping: layout.tsx sets data-brand="funeralwiseai" so CSS variables swap the palette. Shared Footer, MissionFooter, Nav components conditionally style by brand.
  • Voice agent: Shared LiveKit deployment (cwa-voice-9x077mph). Per-vertical prompts live in voice-agent-livekit/verticals/ — the same agent routes to different system prompts based on the phone number or dispatch metadata.
  • Database: Shared Supabase. Funeral homes provision into dedicated funeral_homes + premium_funeral_homes tables per the multi-vertical tenant architecture decided on 2026-04-21. Shared-core tables (voice agent config, call logs, subscriptions state, tool invocations) are renamed tenant_* with a vertical column to disambiguate rows across verticals. See knowledge/decisions/2026-04-21-multi-vertical-tenant-architecture.md and knowledge/architecture/multi-vertical-schema.md.
  • Stripe: Separate product/price IDs from church tiers. Setup fee = one-time invoice + subscription starts after setup.
  • Deployment: Same Vercel project (churchwiseai). Hostname rewrite in middleware.ts maps funeralwiseai.com/*/funeralwiseai/*.

Strategic Role

Per narrative/strategy.md, the vertical expansion priority list is:

  1. Funeral Homes (live) — closest emotional + after-hours parallel to church care
  2. Auto Repair (planned — ShopWiseAI)
  3. Veterinary (planned — VetWiseAI)
  4. Small Law Firms (planned — LegalWiseAI)

FuneralWiseAI is the proof point: if the WiseAI engine can successfully serve a non-church vertical with the same platform, same voice agent, same database, and same pastoral-care framework, then WiseAI Agency's multi-vertical thesis is validated. If it struggles, we re-tighten focus on churches before expanding further.