Canceling a Dead Person's Subscription
Every SaaS company eventually gets this email: 'My husband passed away. How do I cancel his account?' Most companies handle it terribly. Build a bereavement protocol before you need one.
"Hi, my name is Sarah. My husband David passed away two weeks ago. He had a subscription to your product and I need to cancel it. I don't have his password and I can't access his email because it was his work account. Can you help me?"
This email will arrive in your inbox eventually. It might be from a spouse, a parent, a child, or an executor of an estate. The person writing it is grieving. They're dealing with dozens of subscriptions, accounts, and services that the deceased person had. Yours is one of many.
How you handle this interaction will be remembered. The person on the other end is in the most vulnerable state a human can be in. A corporate, by-the-book response will feel cruel, even if it's technically correct.
What Usually Goes Wrong
The standard response to account cancellation requires account verification: email, password, last four digits of payment. The bereaved family member has none of these. The account holder is dead.
Bad response: "For security purposes, we can only process account changes when the account holder contacts us directly. Please log in with the account credentials."
This actually happens. Automated systems, rigid policies, and agents who don't have a bereavement protocol all produce this response. The bereaved person now has to argue with your support team, while grieving, to stop paying for a product their dead family member used.
Some companies require a death certificate. For a $9.99/month subscription. The administrative burden of obtaining and sending a death certificate (which costs $10 to $25 per copy in most states) to cancel a minor subscription is absurdly disproportionate.
Build the Protocol Before You Need It
You need a bereavement protocol documented and accessible to every support agent before the first bereavement email arrives. Building it during the moment is too late.
The protocol should cover:
Verification. Accept reasonable proof: a verbal or written statement from an immediate family member is sufficient for accounts under a certain value (say, under $500 in total charges). For higher-value accounts or accounts with sensitive data, request a death certificate or estate documentation. But for a $10/month subscription, a family member's email should be enough.
Cancellation. Process it immediately upon verification. Don't make them wait 5 to 7 business days. Don't require a phone call. Don't transfer them to a retention specialist (yes, companies have accidentally routed bereavement cancellations to retention teams).
Refunds. Refund the current billing period without being asked. If the person was charged after the date of death, refund all post-death charges proactively. Don't make the family member notice and ask for each one.
Data. Ask whether the family wants the account data (exported) or deleted. Some families want access to documents, photos, or other data stored in the deceased's account. Provide export options. If they want deletion, process it.
Tone. The response should come from a named human, not an automated system. First name, personal sign-off. "I'm very sorry for your loss. I've cancelled David's account and refunded the March charge. If there's anything else I can help with, please reply to me directly. - Alex."
What the Best Companies Do
Apple has a Digital Legacy program. Google has an Inactive Account Manager. Facebook has a Memorialization option. These large companies have formal processes because they deal with bereavement requests at scale.
For smaller companies, you don't need a product feature. You need a documented human process. A runbook entry that agents can follow: step by step, tone guidance included.
The best responses share common traits:
They lead with condolence. Not a corporate condolence ("We are sorry for your loss"). A human one. "I'm so sorry about David."
They take immediate action. "I've cancelled the account and issued a refund. You don't need to do anything else."
They reduce burden. The family member has enough to deal with. Don't create homework for them. Don't ask for documentation unless absolutely necessary. Don't make them fill out a form.
They offer help beyond the minimum. "If you'd like, I can export David's data for you so you have a copy. Just let me know."
The Recurring Charge Problem
SaaS subscriptions charge automatically. A person dies, and the charges continue. The family may not discover the subscription for months, especially if it was billed to a credit card they don't monitor closely.
By the time they contact you, they may have been charged 3 to 6 months after the death. The right response: refund all charges after the date of death, no questions asked. The legal argument (the deceased agreed to the terms) is technically valid and morally indefensible. Nobody wants to be the company that billed a dead person for half a year and refused to refund.
Proactive option: if your payment processor notifies you of a cardholder's death (some banks send this notification), cancel the account proactively. Send a gentle email to any associated contacts: "We were notified that the cardholder for this account is no longer with us. We've paused all billing. If you'd like to manage the account, please reach out."
AI Classification for Bereavement
Supp can be configured to detect bereavement-related messages. Keywords like "passed away," "deceased," "death," "died," "executor," and "estate" in the context of account cancellation trigger a specific routing. These messages go to a senior agent or team lead, never to an auto-responder.
An automated response to a bereavement email is one of the worst things your support system can do. "Thanks for reaching out! We'll get back to you within 24 hours" in response to "my mother died" is tone-deaf to the point of cruelty.
Flag these messages. Route them to humans. Respond within the hour. And have the protocol ready so the human knows exactly how to handle it with grace.
One Last Thing
Add a "Manage account on behalf of someone else" option to your support contact form or help center. A dropdown that includes "I'm writing on behalf of a deceased account holder." This simple UI element tells the bereaved person: you anticipated this situation, you're prepared for it, and they don't have to explain from scratch.
Most people canceling a dead person's subscription expect a fight. They've already fought with the phone company, the insurance company, and the gym. When your company makes it easy and compassionate, they remember. They tell people. And in a world where most companies fail at this, being the one that doesn't is an act of decency that costs you nothing.