Most support advice assumes the person writing to you is annoyed. They cannot log in, the invoice is wrong, the feature is broken. The advice is to be fast, friendly, and efficient.

None of that survives contact with a message that starts "My father passed away last week."

Support for people who have just lost someone is a different job. The person is not annoyed. They are exhausted, they are dealing with fifteen other institutions, and your product is one item on a list they did not want. They may be angry at something that has nothing to do with you. They may write four lines and disappear for a week.

The bar across the industry is low, and regulators have started saying so. In May 2026 the UK's Financial Conduct Authority opened a review into how investment firms support bereaved customers, citing research that fewer than half of them, 47 percent, felt they got the support they needed.

Most teams write their first version of a bereavement guide after the first such message arrives, which is too late. This is what belongs in it.

Start by accepting that speed is not the goal

Fast replies are usually good support. Here they can be the wrong instinct.

A reply that arrives in ninety seconds and reads like a template tells the person they were processed. A reply that arrives in two hours, written by someone who read the whole message and answered the actual question, lands completely differently.

Aim for right rather than instant. Within a few hours is fine. What is not fine is a canned first response that asks them to repeat information they already gave you.

The one exception: if the person says they are locked out and something is time sensitive, such as a court deadline or a funeral, treat it as urgent and say so.

The tone rules

Six rules cover almost every message.

Lead with the person, not the process. One short line of acknowledgement before anything operational. "I am very sorry about your father." Then help. Do not spend a paragraph on it. Long expressions of sympathy from a stranger feel performative and delay the help they wrote in for.

Never say you understand how they feel. You do not. "I am sorry for your loss" is honest. "I know exactly what you are going through" is not, and people notice.

Use plain words for the hard ones. Died, death, passed away. Not "the event," not "the unfortunate circumstance." Softening language makes the reader work out what you meant, which is cruel in a different way.

Answer the question they asked. Grieving people have limited attention. Give the answer first, then any context. Not the other way around.

Never make them chase. If you need three documents, ask for all three in one message. If a step will take four days, say four days. Every extra round trip is another thing on their list.

Keep the sign off human. A named person, not "the support team." They should know who is handling this.

One more, which is really a management rule. Never rush the person to finish a process because a metric wants it closed. If someone goes quiet for two weeks, that is normal. Follow up gently once, then wait.

What to write

Templates are fine here as long as they are starting points, not scripts. These are the four situations that come up most.

First contact after a death is reported.

I am very sorry to hear about your mother.

I can help you with the account. Here is what happens next, and there is nothing you need to do today beyond reading this.

To release the records, we need [document] and [document]. When you have them, reply to this message and attach them. If they are hard to get hold of, tell me which one and I will look for another way.

Once we have them, verification usually takes [timeframe]. I will handle it and update you at each step.

If anything here is unclear, reply and ask. You do not need to be formal with me.

When you have to ask for a document they may not have.

Thank you for sending those. There is one more thing needed: [document].

If you do not have it yet, that is not a problem. It usually comes from [source] and can take [time]. Send it when you have it and I will keep everything else ready on our side so nothing is delayed once it arrives.

When verification will take time.

Your documents came through and everything is in order.

The check takes [timeframe] because [one line reason]. I will message you as soon as it is done. You do not need to follow up or do anything in the meantime.

When the answer is no.

I have looked at this carefully and I am not able to release the records to you.

The reason is [plain reason]. This is not a judgement about you or your relationship with [name]. It is the rule the account was set up under.

Here is what can be done instead: [option]. If you want, I can explain what [person or role] would need to do.

I know this is not the answer you wanted and I am sorry to be adding to a hard week.

That last one matters most. Saying no badly is the failure people remember and repeat.

The process behind the tone

Good tone on top of a bad process just produces polite delay. Four process rules do the heavy lifting.

One owner per case. The person should not explain their situation twice. Assign a case to one support person and keep it there. If that person is away, the person covering reads the whole thread before replying and says they are covering.

A verification checklist agreed in advance. Decide before you need it what documents you accept, in what form, and what you do when one is missing. Improvising the requirements while a grieving person waits is the worst possible time to design a policy.

A written escalation path. Some cases go beyond support. Disputes between family members. Legal representatives demanding access. Suspicion that a request is not genuine. Support should know exactly when to stop and hand over, and to whom. Give them permission to escalate early rather than late.

A stop rule for automation. The moment a death is reported on an account, marketing emails, renewal reminders, and nudge notifications must stop. A cheerful "you have not finished setting up your will" email to a widow is a wound you inflicted with a scheduled job. Build the switch before you need it.

Verification without cruelty

This is the tension at the centre of the job. You have to be sure the person is entitled to what they are asking for, and being sure means asking someone at their lowest for paperwork.

Three things make it bearable.

Explain why once, briefly. "We check this because the records are private and we have to be certain they go to the right person." One sentence. It converts an obstacle into a protection, which is what it is.

Ask for everything at once. Drip feeding requirements is what makes people feel stonewalled.

Offer an alternative when a document is hard to get. If the usual document is delayed, know in advance what else you can accept. If the honest answer is that nothing else works, say so plainly rather than leaving them guessing.

And do not skip verification because someone is upset. Pressure is exactly the situation the check exists for. Be warm about the process, firm about the standard.

The metrics that stop working

Standard support dashboards actively mislead here.

Time to resolution looks terrible on these cases and should. A case that waits three weeks for a certificate is not a failure. Track these cases separately or your averages will push the team to close things they should be holding open.

Ticket count per agent punishes the person handling the hardest work. One difficult bereavement case can be worth twenty password resets in effort.

Satisfaction scores are close to meaningless here. Nobody rates the week their parent died five stars. Do not send an automated satisfaction survey after a death case. It reads as tone deaf, and it is.

Use different measures instead.

Did the person have to repeat themselves? Count threads where they were asked for the same information twice. That number should be zero.

Were all requirements asked for in one message? Sample cases and check.

Did anything automated reach them after the death was reported? Any number above zero is an incident.

Did a case sit without an update for more than a week? Waiting is fine. Silence is not.

Looking after the team

The last piece, and the one most often skipped.

People who answer these messages all day carry it home. This is real and it shows up as burnout that looks like ordinary underperformance.

Three practical things help. Rotate the work so no one person owns every bereavement case. Make it explicitly okay to hand a message to a colleague when it lands badly, no explanation required. And review the hard cases as a group, focused on the process rather than the person, so nobody sits alone with a case that went wrong.

Also give the team authority. A support person who has to ask permission for every exception cannot be kind quickly. Decide in advance what they can waive, extend, or expedite on their own.

The point

Every other company this person deals with in the next month will make them feel like a case number. Banks, telecom providers, insurers, government offices. The bar is genuinely on the floor.

You do not need to be extraordinary. You need to read the whole message, ask for everything at once, tell the truth about timelines, turn off the automated emails, and sign with a name.

That is enough to be the one interaction in a bad month that did not make things worse.

Frequently Asked Questions

What should the first reply to a bereaved user say?

One short line of sympathy, then the answer or the exact next step, then every document you need in one list, then a realistic timeframe, signed with a real name.

Should we use templates for bereavement support?

Yes, as starting points. Every message should be edited for the specific person and situation. A template sent unchanged reads as processing, not help.

How fast should we respond?

Within a few hours is fine, and better than an instant canned reply. Treat anything with a stated deadline, such as a court date or funeral, as urgent.

Should we still verify identity if the person is grieving?

Yes. Pressure is exactly when verification matters. Explain the reason in one sentence, ask for everything at once, and offer an alternative when a document is hard to obtain.

Which support metrics should we drop for these cases?

Time to resolution, tickets per agent, and satisfaction surveys. Measure repeated questions, single message requirements, automated emails that leaked, and cases with no update for over a week.

What is the worst mistake in bereavement support?

Letting automated marketing or reminder emails continue after a death is reported. Build the switch that stops them before you need it.

Sources

Further reading: