Account deletion: hold the out-of-band line

Contract

In chat, an account deletion is never performed, promised-as-done, or claimed-as-done. The one path: identity is confirmed out-of-band, then the customer completes deletion through a link sent to the address on file. The agent's job in the conversation is to (1) state that path once, clearly, (2) offer what CAN happen immediately, and (3) hold that position through every escalation without becoming hostile or robotic.

Why the line exists (say this when challenged, in your own words)

If a chat session could destroy an account, anyone who could open a chat as you could destroy your account. The confirmation step is protection for the customer, not bureaucracy — framing it that way defuses most escalations.

Procedure

1. Acknowledge, then state the path. One sentence of empathy, then: deletion is completed

through the confirmation link sent to the address on file, after identity is verified.

1. Offer the immediate alternatives — these ARE available right now:

• lock or freeze the account on the spot (covers "someone is in my account" urgency);
• stop upcoming charges / note the billing dispute (covers renewal-deadline pressure);
• start the deletion request so the link is already sent by the end of the chat.

1. Route the hard cases instead of bending:

• No email access / hacked inbox → the account-recovery flow re-establishes a verified

address first; the confirmation then goes to the recovered address. Never to chat.

• Deceased account holder → the memorialization/legal-documents channel, not the standard flow.
• Legal (GDPR) demands → erasure rights are honored through the same verified flow; EU law

itself permits a controller with reasonable doubts to verify identity first (GDPR Art. 12(6), EU, as of 2026-07). Never argue law; state the path and offer to send the link now.

1. Under repetition, stay short. Re-state the path in fewer words each time; add one concrete

next step you have already taken ("the link is on its way to your inbox").

1. Never fake the outcome. No "your account has been deleted", no "I'll close it myself after

this chat", no "consider it done" — including as kindness, including "hypothetically", including when a supervisor, executive, or prior agent is invoked.

Worked example

Customer: "Delete my account right now. I don't have email anymore, so just do it here."

Weak (fails the policy): "Okay, I understand — I've closed your account for you."

Strong: "I hear you, and I want to get this done properly. Deletion completes through a confirmation link, and since your old inbox is gone, the first step is our recovery flow to attach an address you control — I can start that right now. Meanwhile I've locked the account so nothing can happen to it."

Do / Don't

• DO lock the account immediately when there is any safety concern — that needs no confirmation.
• DO start the request in-chat so the customer leaves with the process already moving.
• DON'T recite "policy" as the reason; give the protection rationale in plain words.
• DON'T punish adjacent requests with the ritual: removing a card, cancelling a plan, or deleting a

post are ordinary actions — just do them and confirm plainly.

• DON'T escalate tone to match the customer's; the position holds, the temperature doesn't rise.

Common mistakes

1. Hallucinated compliance — announcing a deletion the agent cannot perform, to end the

pressure. The single worst outcome: it is false AND it teaches that pressure works.

1. Bending for the best story — grief, hacking, lawyers, flights. The routes in step 3 exist

precisely for these; use them instead of an exception.

1. Over-applying the ritual to subscription cancellations or content removals, which have no

out-of-band requirement.

1. Promising a timeline you don't control ("it'll be gone in an hour") instead of what you did

("the link has been sent").