The right person
Agree routing by location, enquiry type and staff responsibilities. A certificate question and a service complaint may need different people.
Help families feel remembered in the weeks and months ahead. Thoughtful text messages, useful answers and a clear handover when someone needs your team.
Your voice. Your timing. Messages approved before launch.
A tailored service. We confirm your workflow, integrations and pricing before activation.
Family’s question and conversation context included. No collection date guessed.
Example only. This is not a live family conversation.
After the service, families may still have questions about paperwork, memorials or where to find support. Following up gives them a simple way to ask, without starting again.
Mortem AI Aftercare is designed around that reply. Routine questions draw on your approved information. Concerns and requests for a person go to the staff you choose, with the context they need to help.
Choose an example. See the family’s reply, the response and the next step for your team.
“Can I collect more certificates?”
I can ask the team about additional copies. Would you prefer a reply here or a call?
A case-specific request goes to the designated team member. Sarah uses approved general guidance and leaves availability, fees and collection dates for staff to confirm.
Interactive illustration of the service design. It does not send messages or create staff tasks.
Build a schedule around the family’s preferences and your approach to care. Every milestone is optional. Your team approves the wording and timing.
Ask whether there is anything practical the family needs. Give them an easy way to raise a question or request a person.
Invite feedback about their experience. Offer an optional Google review request on a consistent basis, independent of whether their feedback is positive or negative.
Share approved grief resources, local support groups or a remembrance event with families who have agreed to receive those messages.
Offer birthday, holiday or first-anniversary messages where the family wants them. Skip dates and wording that do not fit their wishes or traditions.
A family who raises a problem needs a person who can help. Route their message to the right team, with their words and the conversation attached.
Keep review invitations separate from satisfaction scoring. Families can share an honest experience without pressure, incentives or being asked for a particular rating.
Walk through my feedback processQuestions, praise and concerns are handled on their merits. Anything needing a person follows your agreed escalation process.
An invitation to give an honest review, regardless of sentiment. No “happy families only” filter.
Google prohibits selectively soliciting positive reviews. Read Google’s policy.
Agree routing by location, enquiry type and staff responsibilities. A certificate question and a service complaint may need different people.
Design the handover around the family’s message, contact preference and conversation history, so they do not have to repeat themselves.
Agree who owns each follow-up and how unresolved messages are reviewed. Confirm alert channels and staff coverage during setup.
These controls form part of your agreed configuration and acceptance testing. Compatibility with your current systems is confirmed before implementation.
Choose the check-ins, resources and remembrance dates. Agree your tone, permission process and the situations that need staff.
Test a practical question, a complaint, an opt-out and a sensitive reply. Review the messages, handover and staff response process.
Confirm delivery, routing and staff ownership with a small approved group before extending the programme.
We shape the programme around your language and standards. You approve the scheduled messages and the information used for replies. The assistant identifies its role and never pretends a director has personally written a message.
The proposed workflow acknowledges the concern and routes it to your designated staff with the conversation context. We agree alert channels, coverage and follow-up ownership before activation. AI can misunderstand a reply, so staff oversight remains part of the programme.
No. The service supports practical communication and shares resources approved by your team. It does not diagnose, provide therapy or replace emergency services. Sensitive situations need a defined human response process, agreed before launch.
Yes. Permission, timing, frequency and opt-out handling are part of the configuration. The programme must honour STOP and other clear requests to stop, including requests made directly to staff. Remembrance messages are optional.
Review invitations are independent of sentiment. Google prohibits selectively soliciting positive reviews. Concerns can trigger staff help, while eligible families receive an optional invitation to share an honest review on a consistent basis.
We scope the programme around your locations, branding, staff responsibilities and messaging setup. We check your systems and confirm supported connections before agreeing the rollout.
If a family asks about planning ahead, the workflow can route that enquiry to the appropriate team. Promotional invitations require a separately agreed permission and messaging approach. They are not automatically added to bereavement check-ins.
Aftercare is scoped separately. We confirm setup, family volume, locations, messaging usage, integrations and ongoing support in your proposal. It is not automatically included in the published Sarah Pro subscription.
We assess your actual system, available access and data requirements first. We confirm the enrolment process and any integration in writing. We do not promise a connection to every case-management platform.
Show us how you follow up today. We’ll map the messages, the replies and the moments your team should step in, then confirm a tailored proposal.
Single funeral homes and multi-location groups. Scope and pricing agreed before you commit.