How does it recognize an at-need situation versus pre-planning?

From language indicating a death has already occurred — it's treated as urgent by default whenever there's any ambiguity, and the response leads with your phone number rather than continuing as a normal conversation. Getting this wrong in the cautious direction costs nothing; getting it wrong the other way is unacceptable.

Does it quote a total price for a specific service?

It states your published General Price List item by item, since itemized pricing is both legally required and the honest way to answer. It doesn't assemble a final custom total — that's confirmed with your staff during arrangements.

Can it discuss grief or offer emotional support?

It acknowledges loss with simple, sincere language, but it isn't a grief counselor and doesn't attempt to be one — its job is getting the family to a real person and real information as fast as possible.

AI customer support for funeral homes

A funeral home's website serves two entirely different visitors: someone pre-planning calmly, and someone who needs help right now. RubyRep's first job is telling those apart — an at-need message gets your direct phone number immediately, not a chat conversation — and the rest of the time it answers pricing and service questions plainly, using the price list the FTC already requires you to publish.

What funeral homes deal with

A family in an urgent, at-need situation shouldn't be stuck typing into a chatbot — they need a phone number instantly.
Pricing questions feel awkward to ask directly, and a site that hides its price list reads as evasive at the worst possible moment.
Pre-planning visitors have genuinely different questions than at-need families, and one generic response serves neither well.

How RubyRep works for funeral homes

An at-need situation is recognized immediately and answered with your direct phone line, front and center — not a chat flow.

Pricing questions answered from your published General Price List, honestly and without requiring an awkward phone call to ask.

Pre-planning questions — package options, payment plans, what to bring — answered patiently and separately from at-need urgency.

The knowledge comes from pages you already publish:

General Price List (GPL), published in full
At-need immediate contact page
Pre-planning and payment plan options
What to bring / arrangement conference guide

Questions your visitors actually ask

“My father just passed, what do we do now?”
“How much does a funeral cost?”
“What's the difference between burial and cremation pricing?”
“Can we pre-plan and pay over time?”
“What do we need to bring to make arrangements?”

RubyRep for funeral homes

How does it recognize an at-need situation versus pre-planning?: From language indicating a death has already occurred — it's treated as urgent by default whenever there's any ambiguity, and the response leads with your phone number rather than continuing as a normal conversation. Getting this wrong in the cautious direction costs nothing; getting it wrong the other way is unacceptable.
Does it quote a total price for a specific service?: It states your published General Price List item by item, since itemized pricing is both legally required and the honest way to answer. It doesn't assemble a final custom total — that's confirmed with your staff during arrangements.
Can it discuss grief or offer emotional support?: It acknowledges loss with simple, sincere language, but it isn't a grief counselor and doesn't attempt to be one — its job is getting the family to a real person and real information as fast as possible.

tool

Website support score

Scores a website on how well it could support customers — and how well an AI representative trained on it would perform. Five dimensions, a total out of 100, and the specific gaps behind the score.

tool

Chatbot ROI calculator

Estimates the support cost an AI chatbot would remove, based on your ticket volume, handling time and loaded hourly cost — plus payback period against a monthly subscription.

use case

After-hours support that doesn't lose the lead

The gap between a question and an answer is where interest dies. Answering after-hours questions immediately — and routing the ones you can't answer to a form or booking link — keeps enquiries warm until someone is back at a desk.

use case

FAQ automation that uses your real pages

A static FAQ page ages badly and never quite matches how people phrase things. Reading your whole site instead means the answer to a question can come from wherever it genuinely lives — a policy page, a product spec, a help article.

term

What is a handoff in customer support?

Every automated support system needs a way out, and the quality of that exit matters as much as the answers. A good handoff carries the transcript, so the customer is not asked to repeat what they already typed — which is the single most common complaint about support automation, and one that is entirely avoidable.

question

My family member just passed away, what do I do now? — what funeral homes need to publish

This is the single highest-stakes moment on a funeral home's site, and the only acceptable response is an immediate phone number, not a conversation. A complete answer for funeral homes contains 4 specific elements, and it belongs on your at-need immediate contact page.

Give your website an AI representative.

It reads your site and starts answering. Around a minute to find out how good yours would be.