Skip to main content

FuneralWiseAI — Integration Research & Ranked Backlog

Source: voice-agent-engineer subagent research, 2026-04-28. Founder-directed ("send out a research agent to find out what integrations we should have for funeral homes"). Authoritative APIs verified via vendor docs + recent NFDA reports.

Industry context (so the rankings make sense)​

  • ~19,000 funeral homes in the US + ~1,500 in Canada (NFDA represents ~11,000 of them; total industry is bigger). Cremation rate hit 63.4% in 2025 and is heading to 82.3% by 2045 — relevant because cremation arrangements happen more by phone and less in person, which is exactly where a voice agent earns its keep.
  • The funeral-tech stack is fragmented, not consolidated. There is no Planning Center equivalent — the closest analogues are Passare, FrontRunner Professional, Tribute Technology / CRaKN, SRS Computing, Halcyon, and Gather.
  • Passare is the only vendor with a documented public API that funeral-tech partners actually plug into ("30+ integrations, public API"). FrontRunner has API connectors but they're partner-by-partner. CRaKN advertises "15+ integrations" but no public API. Halcyon, SRS, and Mortware are essentially closed black boxes. Gather has explicitly stated "no API." Tribute Technology has a real REST/JSON API for the Tribute Store (obituary publishing) with bearer-token auth.
  • One free, well-documented API matters disproportionately: Express Funeral Funding's "Express API" (insurance assignment funding) — submission, view, edit claims data; no cost to partners; 10–20 hr typical integration.
  • EDRS (death certificates) is mostly portal-only. Pennsylvania is the first and currently only state to expose an API; everyone else is web-form. SSA notification (Form SSA-721) is paper/fax in most states, electronic only where the state EDRS pipes it through.
  • VA National Cemetery scheduling has no API at all — phone-only at 800-535-1117. Worth knowing for the agent's "I want to bury my dad at the national cemetery" use case but not buildable.

Top 5 must-have integrations (Phase 1 — first paying customer)​

1. Cal.com (already built, just configure for funeral home event types) — S​

Use cases unlocked: "Can I come in tomorrow to make arrangements?" / "Book the chapel for Saturday 11am." / "Schedule a pre-need consultation."

Why first: It's already in the codebase (church_voice_agents.cal_event_type_id, cal_api_key). The exact same integration pattern works — just reframe the event types as Arrangement Conference, Chapel Booking, Pre-Need Consultation. Zero new code, only seed data for the funeral vertical and renamed prompt fragments.

Data flow: push event title/decedent name/family contact, pull available slots, confirm booking and stamp appointment_id on a funeral_call_logs row. Same shape as the church side.

2. Passare API (case management — the "ChMS equivalent") — L​

Use cases unlocked: "My mother just passed at hospice" → auto-create a case. "Look up the status of the Smith arrangement" → read case. "Capture caller as next-of-kin contact on the Jones case" → update case.

Why second: Passare is the only major case-management system with a real, documented public API and a partner integration program (FDLIC, Tukios, Bass-Mollett, FuneralOne, Legacy.com all already plug in). It's mid-market, cloud-native, growing — exactly the customer segment our pricing targets ($999 setup + $199/mo). If the voice agent can write a real case row into Passare on the first call, the demo basically sells itself.

Risk: The API is partner-gated — you have to apply to Passare's developer program. Founder action: email partnerships@passare.com to start the conversation; they're known to be friendly to integrators.

Data flow: PUSH new case (decedent name, DOB/DOD, NOK contact, place of death, disposition preference, voice-agent transcript ID); PULL case status / arrangement details by case ID / search by decedent name; WEBHOOK on case status change → notify on-call director via SMS.

3. Tribute Technology / Tribute Store API (obituary + memorial websites) — M​

Use cases unlocked: "Where can I post the obituary?" / "Can you publish the obituary now?" / "Send flowers to the family."

Why third: Tribute Technology powers obituaries on 9,000+ funeral homes (deeper reach than any single back-office system). Their API is REST/JSON with {HostName, Username, Password} → bearer token, supports POST=upsert pattern, base64 photo upload. It's the cleanest API in the space. Voice agent can take a draft obituary over the phone and push it to the family's funeral home website same-day.

Data flow: PUSH obituary draft (name, dates, photo b64, service details), PULL obituary list with thumbnail URL + obituary_id. Webhook ideally on family edit/approval (not currently documented — confirm with Tribute).

4. Express Funeral Funding API (insurance assignment) — M​

Use cases unlocked: "I want to use my mom's life insurance to pay for the services." / "Is the assignment funded yet?"

Why fourth: This is the highest-leverage transactional integration in the entire funeral stack. Funeral homes float ~$8K–$15K of receivables per case waiting on insurance — Express Funding turns that into 24–72 hour cash. Every funeral home director cares about this. The API is free, partner-friendly, 10–20 hr to integrate per their own docs. C&J Financial is the larger competitor (since 1996, "largest in North America") but no public API documented — Express's API-first stance is why it ranks higher for us.

Data flow: PUSH claim submission (decedent, policy info, funeral home contract, NOK assignment signature), PULL claim status + funding receipts; WEBHOOK on funding completion → SMS director.

5. QuickBooks Online API (accounting) — M​

Use cases unlocked: "What's the balance on the Smith account?" / "Send the family their invoice." / Auto-post a paid case to the books once funded.

Why fifth: Roughly 80%+ of independent SMB funeral homes (our exact ICP) run QBO. Both Passare and FrontRunner already integrate with it, so the pattern is well-established. OAuth 2.0, mature SDK, abundant documentation, well-known to any agent. Phase 1 scope: read invoice status + push paid markers; defer general-ledger automation to Phase 2.

Data flow: PUSH invoice (case → invoice mapping by reference number), PUSH payment (via Stripe webhook), PULL invoice status; OAuth 2.0 with per-customer auth.

Next 5–7 nice-to-haves (Phase 2)​

#IntegrationWhy valuableComplexityNotes
6ASD Answering Service (FuneralSync 3.0 API)~33% of US funeral homes already use ASD as their after-hours human-answering. Co-existing rather than displacing them shortens sales cycles ("we work with your ASD account"). FuneralSync 3.0 is free, requires ASD-side activation.MStrategic positioning play — we are the day-side AI; ASD is night-side humans.
7FrontRunner Professional connector2,800 funeral homes (US + Canada). API is partner-by-partner, not public; would require BD relationship. Worth opening conversations now even if integration ships later.LDirect competitor for case mgmt — but they may welcome a voice layer they don't build.
8CRaKN integration (Tribute Tech parent)CRaKN was acquired into Tribute Technology, so a Tribute deal could open both. 15+ integrations advertised but no public API surface — partner-gated.LBundle into the Tribute Tech relationship.
9Gather case management (DB sync, no API)Gather has 1,000+ funeral homes and is the modern Passare alternative. Currently API-less, but they recently announced Homesteaders Life integration — they're moving toward partnerships. Keep on radar; offer "we'll integrate the moment you have an API."n/aWatch-list.
10Homesteaders Life preneed lookupLargest preneed insurer; just integrated with Gather. If our agent can verify "yes, your mom has a $12K Homesteaders policy" mid-call, that's gold. Probably routed through Passare or Gather rather than direct.MSecondary integration — comes free with Passare.
11Resend (email) + Telnyx/Twilio (SMS) — already in stackWe already use these for ChurchWiseAI. Just need funeral-themed templates: arrangement confirmation, obituary draft for review, after-care follow-up, VA benefits checklist.SDay-1 in the funeral vertical.
12Stripe pre-paid + at-need payments — already in stackWe already do Stripe. Funeral-specific: pre-need installment plans, deposit-then-balance flow, partial payment receipts.SWire up funeral-specific products in Stripe.

Defer list (Phase 3+ or never)​

IntegrationWhy defer
State EDRS (death certificate filing)Only Pennsylvania has an API. The other 49 states are web-form portals. Voice agent should answer questions about how to file ("Your funeral director files this within X days") and route to a human, not attempt to file. Re-evaluate when 5+ states ship APIs.
VA National Cemetery schedulingPhone-only (800-535-1117). No portal. Voice agent should collect info and dial-out; no API to build against.
SSA Form SSA-721Submission is faxed/mailed in most states; electronic only where EDRS hands off. Defer with EDRS.
Salesforce / HubSpot / PipedriveSMB funeral homes don't run CRMs; the case-management system is the CRM. Build only if a chain customer (SCI, Service Corp) asks.
Casket suppliers (Batesville, Matthews)EDI not REST. Procurement is multi-day, not voice-realtime.
Florists (FTD, Teleflora)The funeral home website handles this via Tribute Tech / FuneralOne already. Don't reinvent.
Aldor Solutions / preneed funding adminBack-office finance; no caller-facing use case.
Echovita / Legacy.com obit publishing directLegacy.com is downstream of Tribute Tech for most funeral homes; covered by #3. Echovita is controversial (obit-piracy lawsuits) — actively avoid.
Halcyon / SRS Computing / MortwareNo public APIs. Older, on-premise installs. Customer base skews to firms that won't buy us anyway.

Competitive context: ASD Answering Service​

ASD is the dominant incumbent in funeral-home telephony — ~33% of US funeral homes use them, family-owned since 1972, market leader. They're a human answering service trained specifically for funeral calls (decades of institutional knowledge on grief). Any funeral-home sales conversation will inevitably hit "we already use ASD" — so we need a clear answer.

ASD pricing (from public sources, 2026)​

Cost comparison vs FuneralWiseAI ($999 setup + $199/mo)​

ASD (avg use)FuneralWiseAI
Setup$0$999
Monthly~$165 (range $150–$300)$199
Year 1 total$1,980$3,387
Year 2+ ongoing$1,980/yr$2,388/yr
Per-call cap$0.75–$1.50/call or $1.39/minflat — no cap
Multi-channelvoice onlyvoice + chatbot
Setup timeminutesdays
Integration potentiallow (message relay only)high (Passare, Tribute, QBO, Express, Cal.com)

ASD wins on pure cost for low-volume independents. FuneralWiseAI wins as call volume rises and as the integration moat compounds (writing cases into Passare, drafting obituaries via Tribute, pulling Express insurance funding mid-call) — none of which ASD can do.

Where FuneralWiseAI can supplant ASD​

Strong supplant case:

  • High-volume homes (500+ calls/month) where ASD's per-minute charges cross our flat $199. ROI calculator on the website should show "If you're paying ASD $300+/mo, switch and save while gaining 24/7 instant pickup + integrations."
  • Homes wanting 24/7 instant pickup with zero hold queue or busy signal.
  • Homes wanting voice + chatbot in one product (ASD has no chatbot).
  • Homes already considering AI for cash flow (Express Funeral Funding integration coming) — that's a director-grade pitch ASD can't match.

Weak supplant case:

  • Low-volume rural homes (under 100 calls/month) paying ASD $150/mo flat — pure cost-comparison favors ASD year 1.
  • Homes that prize human-only empathy over efficiency.

Strategic positioning options​

  1. (a) Lower-tier "Basic" offering — $99–$149/mo with reduced features (no integrations, single language) to undercut ASD on price. Risk: brand dilution + cannibalization of the full tier. Not recommended.
  2. (b) Volume-priced premium (status quo) — Stay at $199/mo flat, target homes paying ASD $300+. ROI calculator + cost-cross slider on funeralwiseai.com/pricing. Recommended.
  3. (c) Hybrid co-existence — Position as ASD's daytime AI complement, not replacement. "We handle 80% of operational calls during business hours so ASD focuses on after-hours calls when human empathy matters most." Easier sales motion; eventually converts as usage data shows the AI handling night calls fine too. Recommended in parallel with (b).
  4. (d) Replacement-grade — frame setup fee as the moat — $999 setup is the per-customer Passare/Tribute/voice-clone provisioning cost. Ongoing fee is in the same range as ASD's average. Competitive year-2+, premium year-1. Already our pricing.

Recommended combination: (b) + (c). The 50-year-old trust brand is hard to fight head-on for the price-sensitive segment, but ASD has zero integration story. Funeral homes that want to automate cases (not just answer calls) are inherent FuneralWiseAI buyers regardless of price.

Why we still rank ASD's FuneralSync 3.0 API at #6 (nice-to-have)​

Even when the strategy is "supplant ASD eventually," the FuneralSync 3.0 API matters during the transition: a hybrid customer using both products needs the AI to push capture data into ASD's case logs so the human director sees a unified record. Co-existence is the easier sale; replacement is the bigger check. Both motions benefit from the integration.

Per-integration data-flow sketch (top 5)​

Voice agent ──► Cal.com           PUSH: event_type, time, attendee
                                   PULL: free/busy slots
                                   STATE: appointment_id on call_log

Voice agent ──► Passare            PUSH: new case (decedent, NOK, place, disposition)
                                   PULL: case lookup by name/case#, status
                                   WEBHOOK: case status change → SMS director

Voice agent ──► Tribute Store      PUSH: obit draft (name, dates, photo b64, services)
                                   PULL: obit list by funeral home
                                   STATE: obituary_id on case row

Voice agent ──► Express Funding    PUSH: claim (policy, decedent, contract, NOK)
                                   PULL: claim status, funding receipts
                                   WEBHOOK: funded → SMS director "Smith case funded $14,250"

Voice agent ──► QuickBooks Online  PUSH: invoice, payment
                                   PULL: invoice status by ref#
                                   AUTH:  OAuth 2.0, per-funeral-home consent

Open questions (need a real funeral director interview)​

  1. Which case-management system do they use today? Passare-first only works if our ICP runs Passare. We need to know the actual mix among small independents (~5–15 calls/week), which is our cold-email target. Hypothesis: Passare for under-50, FrontRunner for the website-led, SRS/Halcyon for older firms.
  2. What % of incoming calls become a case vs. just an info call? Drives whether case-creation needs to be inline-during-call or batched.
  3. Who actually approves an obituary going live? Family or director? Determines whether the agent should auto-publish or queue-for-approval.
  4. Do they want the agent transferring to a backup human (ASD) or capturing voicemail when stumped? Determines escalation tree — analogue to PASTORAL_ROLES gate in the church product.
  5. Pre-need vs at-need split. Pre-need is a sales conversation (slow, structured); at-need is crisis (fast, empathetic). Different prompts, different tool sets — likely two distinct agents like our Coordinator vs Care.
  6. Insurance assignment volume per home. If a home only does 2 assignments/month, Express integration is nice-to-have. If 20+, it's day-1.
  7. Does the director want the daily morning brief? ChurchWiseAI's pattern of "here's what happened overnight" maps perfectly — but funeral home overnight calls are ~80% removals. Different artifact.

Five-item ranked dev backlog​

#BuildEstimated effortUnlocks
1Funeral-themed Cal.com event types + voice prompts (Arrangement Conference, Chapel Booking, Pre-Need Consultation)1–2 days (S)First paying customer can take real bookings on day one. Zero new code, just seed data + prompt fragments.
2Passare partner API onboarding + case-create + case-lookup tools2–3 weeks (L). Includes BD relationship, sandbox access, two voice tools (create_passare_case, lookup_passare_case), webhook receiverTurns FuneralWiseAI from "answers calls" into "writes cases" — the core moat.
3Tribute Store API: obituary draft + push1 week (M). Bearer auth, two tools (draft_obituary, publish_obituary)"Caller dictates obit, family approves, agent publishes" — strong demo moment, broad reach (9K homes).
4Express Funeral Funding API: claim submission + status1 week (M). Free API, 10–20hr per their guideCash-flow superpower for the funeral home — director's #1 pain point.
5QuickBooks Online OAuth + invoice push/pull1–2 weeks (M). Per-customer OAuth, Supabase token storage same pattern as Cal.comEvery SMB funeral home runs QBO; closes the loop from call → case → invoice → payment.

Recommended sequencing for Phase 2 (after the unified architecture refactor): ship #1 day-one as part of the funeral vertical seed, open BD conversation with Passare immediately (#2 has the longest BD lead time), build #3 in parallel (cleanest API of the bunch and gives a demo moment), then #4 and #5 once a real customer has signed.

Sources​