Support quality is broader than speed. A quick reply that asks the team to repeat the entire story may be less useful than a clear, traceable response with an appropriate next step. Evaluate the whole path from reporting an issue to confirming that the affected work can continue.
Separate the types of help you need
List routine questions, staff training, configuration changes, migration corrections and service interruptions separately. A vendor may handle these through different channels or include them under different terms. A training appointment is not necessarily the same service as urgent incident handling.
Include connected providers in the map. Payment processing, accounting software, email delivery and website hosting can involve separate organizations. Ask who determines where a problem belongs and who remains responsible for updating your staff while that determination is made.
Older service complaints in public Osiris reviews illustrate why scope matters, but individual accounts do not prove a current industry-wide support failure. The practical lesson is to confirm which services you are buying and how the boundaries work, whichever vendor you select.
Ask for hours and commitments in writing
Identify the time zone, normal staffed hours, holiday coverage and available channels. Ask whether telephone, email and in-product messages have the same coverage. “Contact us anytime” may describe when a message can be submitted rather than when a person will respond.
If the agreement includes response targets, read the definitions. Does a response mean acknowledgment, human assessment or a proposed workaround? Does the commitment apply to all issues or only a defined severity? What information must the customer provide before the clock starts?
Separate first response from resolution. Some problems depend on a third party or require product work, so a universal resolution promise may be unrealistic. What matters is a credible escalation route, regular updates and a clear account of the work your staff can safely continue.
Build a practical severity guide
| Situation | What staff should capture | Question for the vendor |
|---|---|---|
| Whole team cannot sign in | Time, scope and observed message | How is a broad interruption escalated? |
| One document request fails | Case reference and request stage | What supported alternative is available? |
| Payment status is uncertain | Processor reference and observed confirmation | Who verifies before a retry? |
| Report differs from expectations | Definition, period and sample | Is this configuration or a defect? |
| New employee needs help | Task and training already completed | Which training is included? |
These are proposed categories to adapt with the vendor. Do not invent a contractual severity label that the agreement does not recognize. Make the employee's reporting instructions consistent with the provider's actual process.
For an urgent issue, include the affected business task. “Cannot prepare the reviewed packet for an appointment” is more informative than “button broken.” Avoid overstating urgency for ordinary configuration requests, which can make genuine interruptions harder to triage.
Make a support request another employee can continue
Use one business-owned issue record with a vendor reference, current status, next expected update and internal owner. A long private message thread on one employee's phone is difficult to cover. Keep relevant responses in an approved shared location.
A useful report states what the employee attempted, what happened, when it happened, who else is affected and whether the result is repeatable. Include the supported browser or device when relevant. Say whether a transaction may already have been submitted so support does not recommend a duplicate action without checking.
Use approved screenshots or redacted examples. Do not send passwords, full payment-card details or unnecessary family information in an ordinary support message. The FTC's information-security guide provides general guidance on limiting sensitive information and managing access. Agree on the vendor's secure method when case material is genuinely necessary.
Test the process without creating a fake emergency
During evaluation, ask the vendor to walk through a fictional blocked-case scenario. Request a sample issue acknowledgment, escalation explanation and closure record if available. A scheduled process review gives useful evidence without misrepresenting a sales exercise as a live incident.
Ask your own staff to explain how they would report the example. If the covering director cannot find the channel or does not know which reference to supply, the problem may be your internal preparation rather than the vendor's response.
For training, choose a real job and let an employee perform it with the provided materials. Observe whether the instructions answer the likely follow-up questions. A large help library is valuable only if staff can locate the relevant answer and understand when it applies.
A fictional issue that spans two shifts
A morning employee reports that a signing request appears incomplete. The vendor assigns an issue reference and asks for the request identifier. The employee records the reference, the information supplied and the next update time in the shared issue log.
At handoff, the evening employee can see that support is investigating. Before sending another request, the employee checks the existing request and the current guidance. The team avoids treating an uncertain status as proof that nothing was sent.
When the vendor reports a resolution, the business checks the actual task: can the right employee locate the correct packet and continue the case? The issue is closed only after that verification, with any remaining training or configuration work tracked separately.
Cover access, staff changes and administration
Name at least two appropriate business contacts for account administration. Ask how access is recovered if an administrator leaves and what identity checks the vendor requires. A support relationship should not depend on a single personal email address.
Clarify whether support staff can access case information, how permission is granted and how access is recorded. Ask the vendor to explain the actual process rather than accepting a broad security adjective. The answer should match the sensitivity of the information and the business's own access rules.
For new employees, define who requests access, who approves the role and which introductory tasks are required. A software vendor can explain the application, but the funeral home still needs to teach its own authority checks, communication standards and operational procedures.
Track outcomes that help the business
Review a small number of issues periodically. Count repeat problems, time until staff can resume the affected task, unclear handoffs and cases reopened after an apparent fix. Keep training requests distinct from service failures so the review remains fair.
Record your own delays as well. An issue may wait because the team has not supplied the requested example or because only one person can approve a change. The aim is to improve the joint process, not to assign every elapsed hour to the provider.
Do not rank vendors using invented average response times or testimonials from unverified conversations. Ask for contractual terms and relevant references, then assess your firm's documented experience after adoption.
Use the checklist in every demo
FuneralHQ invites buyers to bring a real workflow to a demonstration. Include the support questions alongside documents, payments, online arrangements and cemetery work. The person who will cover a busy evening should participate in that discussion.
Use the blank support-scope worksheet to record channels, hours, responsibilities and escalation. Review it when the provider, package or business contacts change. A clear support plan gives staff a dependable next step when the normal workflow stops.
The FuneralHQ advantage
Run the whole case in one place
Keep intake, arrangements, documents, payments and the books together. Bring one of your cases to a demo and see how your team would work through it.
We will work through a real example with you, from the first details to the finished record.
See it on one of your casesAbout the FuneralHQ Editorial Team
This guide was written by the FuneralHQ Editorial Team, the in-house team behind funeral home software used by independent firms to run cases, documents, payments, and QuickBooks sync in one record. Our editorial standards explain how we review product claims, outside sources, automation, updates, and corrections.