Pre-Planning and Requested Aftercare: What to Ask Before Adding CRM Follow-Up
A request for a pre-planning appointment, a request for an aftercare resource and permission to receive promotions are different things. Before buying CRM follow-up for a funeral home, make sure the proposal preserves those differences and gives your staff a clear way to review, pause and take responsibility for communications.
This guide is for funeral-home owners, licensed operators and operations managers comparing communication support. The buying decision is whether the proposed service can help your team honour a person’s request without assuming more authority or permission than you have. A polished message template cannot settle that question on its own.
Start with the purpose of the contact
“Follow-up included” is too broad to be a useful commitment. Ask the supplier to describe the actual business purpose: responding to a planning enquiry, confirming an appointment, supplying a requested resource or sending promotional material. Each purpose can involve different information, approvals and staff responsibilities.
A sensible brief also identifies what the service will leave to your team. Questions about immediate care, funeral arrangements, disputed instructions or the meaning of a contract need the operator’s approved handling. A communication service should not quietly become the decision-maker because it happens to receive the reply.
| Purpose | What the proposal should clarify | What the record does not establish |
|---|---|---|
| Pre-planning enquiry | The information requested, the responsible staff member and the agreed contact preference | A signed arrangement, payment or unlimited promotional permission |
| Appointment communication | Who confirms the appointment and handles a change or cancellation | Authority to discuss every family member’s information |
| Requested aftercare resource | The requested resource, recipient and limits of the service | Consent to an unrelated sales programme |
| Promotional communication | The proposed purpose, applicable permission, approval and withdrawal handling | Permission simply because an address exists in the database |
We assess your existing tools and scope enquiry management, approved communications and staff handover.
Ask the supplier to explain these distinctions with a fictional example before discussing real family records. If all four purposes are presented as one undifferentiated contact list, the proposal needs more work.
Keep planning interest separate from contracts and prepayment
A person may ask about planning without deciding to purchase anything. In Ontario, the Bereavement Authority of Ontario explains that pre-planning can take place without prepayment, while prepayment involves a contract. That distinction matters when you evaluate what the CRM displays and what staff may infer from it. See the BAO’s pre-planning and prepayment guidance.
For the buyer, the requirement is straightforward: staff should be able to tell the difference between an information request, an appointment and an arrangement documented in the operator’s approved records. A convenient label such as “planning complete” needs an agreed meaning. It should never stand in for evidence of a signed contract, funds received or a person’s authority to instruct arrangements.
Ask which system remains authoritative for contracts and financial records, and who verifies a change in status. You may need only clearer communication responsibilities in your current system. A separate CRM is worth considering when there is a defined gap that existing software and staff arrangements cannot reasonably address.
Evaluate permission, preferences and the actual message
For Canadian electronic communications, purpose and content matter. The CRTC’s CASL guidance distinguishes commercial messages and explains applicable consent, identification and unsubscribe requirements, with exceptions depending on the circumstances. A requested reply and a promotional message should not be treated as automatically equivalent. Review the proposed use with the person responsible for your legal obligations. The CRTC’s CASL questions and answers provide the general framework.
Contact preferences answer another question: how does this person want the permitted communication handled? Someone may prefer a telephone conversation, a particular language or contact through an authorised representative. Those preferences do not establish legal authority or create permission for a new purpose. The proposal should explain how staff can see and respect them within the agreed scope.
For a Canadian operator serving more than one province or language community, ask who approves the wording and who can actually respond in the offered language. A translated first message is incomplete support if the next reply reaches staff who cannot continue the conversation. Define the supported languages, review responsibilities and limits before advertising that experience.
The Office of the Privacy Commissioner of Canada stresses that consent and sensitivity depend on context and reasonable expectations; consent does not permit indiscriminate use for unrelated purposes. Apply that principle to the proposed handling of living family members’ information, with advice on the law that applies to your operation. Read the OPC’s meaningful-consent guidance.
Define requested aftercare without turning it into a sales assumption
Aftercare can mean different things in different proposals. One supplier may mean sending an approved resource requested by a family member. Another may mean reminders for staff, a subscription to information or a series of promotional messages. Compare the actual deliverables rather than accepting the label as a complete description.
Ask what the person requested, what the funeral home has agreed to provide and what happens when the reply falls outside that scope. A request for information about local support does not make an agency a grief counsellor. An automated acknowledgement does not mean a member of your team has read a sensitive reply.
Useful communication support gives the operator control over approved resources and escalation. It should allow a staff member to pause a proposed communication when the context has changed or is unclear. Avoid buying a programme whose value depends on interpreting bereavement as a sales signal, repeatedly prompting someone who has asked for space or assuming every family wants the same contact.
You do not need to prescribe a universal contact schedule to assess fit. You need to understand whether the service can respect the purpose, current preference and judgement of the staff member responsible for that relationship.
Name the people responsible for messages and replies
The contract should distinguish content preparation, approval, sending, monitoring and professional response. These may be shared among your staff, an agency and a software vendor. If no one has accepted responsibility for a reply, a feature called “two-way messaging” is an incomplete service commitment.
| Decision | Evidence to request | Reason it matters |
|---|---|---|
| Who approves wording? | A named operator approver and an agreed review process | Prices, service descriptions and sensitive language need accountable review |
| Who watches for replies? | Coverage hours, included channels and responsibility outside that coverage | Sending and monitoring are separate commitments |
| Who handles urgent or professional questions? | The operator’s designated route and the supplier’s handover boundary | An agency support queue is not an on-call funeral service |
| Who can pause or correct a message? | Staff control and the supplier’s support responsibilities | A change in circumstances should not be trapped behind an unclear approval chain |
| Who maintains approved resources? | An owner for content updates and the cost of revisions | An approved resource can become out of date |
If AI-assisted drafting or intake is proposed, ask for its specific role, review requirements and human handover. Do not infer that an AI feature can judge authority, provide funeral advice or decide how a sensitive family situation should be handled. The proposal should make limitations visible to both staff and the people using the service.
Test the proposal against a changed preference
A demonstration is more useful when something changes. Ask the supplier to explain what staff would see if a person withdrew from promotional contact, changed their preferred channel or said that a previous representative should no longer receive updates. Use a fictional record and assess the business outcome, rather than requesting a tour of configuration screens.
Look for a clear answer about who reviews the change, which agreed communications it affects and what remains unresolved across other systems. An imported address or an old note should not silently override a newer instruction. One relative’s request also should not be treated as blanket authority over every other living family member.
Stopping an unwanted communication and deleting a record are different decisions. The applicable retention obligations and permitted uses still need review; a universal “delete everything” promise can be as misleading as a promise to retain everything indefinitely. The OPC’s consent guidance discusses withdrawal and circumstances in which some information may still need to be retained.
Worked example: two requests, two different responsibilities
Illustrative procurement scenario: an Ontario funeral home is considering CRM communication support. One adult asks for a pre-planning appointment. Separately, an adult family member asks for a particular aftercare resource and says they do not want promotional messages. These are fictional requests, not a client case study or measured result.
The owner compares two proposals. The first offers a single automated follow-up package but leaves the purpose of later messages, staff review and reply coverage undefined. The second identifies the appointment request and resource request separately, requires approved wording, records the agreed preferences and names the operator’s contact for sensitive replies.
The second proposal is more assessable because its responsibilities are explicit. That does not make it automatically compliant or the right purchase. The owner still needs to confirm the permitted information, vendor limitations, actual staff capacity and full cost. If the existing funeral-management system already supports those requirements, a smaller improvement there may be enough.
Now change one fact: the resource recipient asks for no further contact. A useful demonstration explains how the agreed communication stops, how staff are informed and which records still require review. It should not turn that request into a new attempt to persuade the person to remain in a programme.
Compare the written scope, including ongoing work
The total commitment may include software subscriptions, message charges, content preparation, language review, staff training and ongoing support. Ask what is included in the quoted work and what creates an additional charge. A low setup price is not enough to compare proposals if one leaves monitoring and content updates entirely to your team.
Before approving, check that the proposal answers these questions:
- Which contact purposes, channels and languages are included?
- What must your operator approve, and how much staff review will that require?
- Who handles replies, exceptions and interruptions, during which agreed hours?
- How will changed preferences and uncertain authority be brought to staff attention?
- Which system holds the authoritative contract and financial information?
- What vendor access, subscription or supported connection does the service depend on?
- What evidence will show that the agreed communication controls work before release?
- What ongoing charges, support limits and exit arrangements are part of the commitment?
Where a supplier cannot answer a material question, leave that part of the purchase unresolved. It is better to agree a smaller, reviewable service than to buy an expansive promise that depends on permissions, staffing or software behaviour nobody has confirmed.
Discuss a bounded communication brief
Canada Create’s Funeral Home CRM service can scope enquiry management, approved communications, staff handoffs and related CRM support around your existing tools. Start with business requirements and fictional or suitably de-identified examples. Do not send family records, identity documents, passwords or sensitive case details through a public enquiry form.
If the gap is the creation of public information pages or approved outreach materials, review the separate funeral home marketing service. The communication brief should make clear which work is being commissioned and which decisions remain with your operator. Written scope, fees and responsibilities come before a commitment.
Frequently asked questions
What is pre-need planning, and how should a funeral home CRM record it?
Pre-need planning means discussing and recording funeral wishes before a death occurs. In a CRM, a pre-planning enquiry should show what the person asked for, the staff member responsible and the agreed contact preference. It should never be shown as a signed arrangement, a payment or permission for unlimited promotional messages.
Does funeral pre-planning in Ontario mean paying in advance?
No. The Bereavement Authority of Ontario explains that pre-planning can take place without prepayment, while prepayment involves a contract. Staff should be able to tell an information request, an appointment and a documented arrangement apart, and a label such as planning complete needs an agreed meaning. Check the BAO's current guidance before setting up those labels.
Why does requested aftercare need careful handling in funeral home follow-up?
Aftercare can mean very different things from one proposal to the next: an approved resource a family member asked for, reminders for staff, or a series of promotional messages. A request for an aftercare resource is not consent to an unrelated sales programme. Define the resource, the recipient and the limits of the service before any message is automated.
Who should approve the messages a funeral pre-planner sends through a CRM?
Name the people who approve wording and handle replies before the workflow goes live. Questions about immediate care, funeral arrangements, disputed instructions or what a contract means need the operator's approved handling, so a communication service should never become the decision-maker just because it receives the reply. For homes serving more than one language community, confirm who can continue the conversation in the language offered.
Can a funeral pre-planning enquiry be added to promotional email follow-up?
Not automatically. Canada's anti-spam law, CASL, sets consent, sender identification and unsubscribe requirements for commercial electronic messages, and the CRTC explains the exceptions. A requested reply and a promotional message are different things, so review the proposed use with the person responsible for your legal obligations.
Does adding CRM follow-up change who is licensed to handle funeral pre-planning?
No. The licensed operator remains responsible for contracts, instructions and required records, and a CRM label cannot stand in for a signed contract, funds received or a person's authority to give instructions. Ask which system stays authoritative for contracts and financial records and who verifies a change in status. Check current licensing rules with your regulator.
Is automated CRM follow-up for funeral pre-planning a good idea?
It can be, when it helps staff honour what a person actually asked for. You may only need clearer communication responsibilities in your current system, and a separate CRM is worth considering when there is a defined gap your existing software and staff cannot reasonably close. Test any proposal against a changed preference, such as someone asking to pause or to be contacted by phone instead.