Seven Signs Support Has Become a Customer Trap

Follow one case from need to evidence of resolution

Choose an authorized case or a non-live scenario and capture the issue, desired outcome, channel, reference, timing, states, owners, handoffs, requested evidence, escalations, and final result. Review the customer's available path, not an internal dashboard alone. A closed label may coexist with an unresolved situation.

Mark each signal observed, not observed, or unresolved. One delay does not prove systemic obstruction. Repeated patterns can justify deeper investigation. Do not create false urgent cases, expose personal data, or call ordinary support when a published emergency route is required.

Evidence: UK Government Digital Service; UK Financial Conduct Authority; U.S. Federal Trade Commission Consumer Advice

Sign 1: the customer cannot enter the support system

The form requires the missing account, the help link loops to the failed page, the only channel is inaccessible, contact details are hidden behind login, or a category list has no route for the actual problem. Demand disappears from metrics because the customer cannot create a case.

Map public, authenticated, accessibility, lost-access, and urgent entry routes. Test with appropriate methods and permission. Provide enough structure for routing without making perfect categorization the customer's responsibility.

Evidence: UK Government Digital Service; UK Financial Conduct Authority

Sign 2: every handoff asks for the story again

The reference does not carry evidence, prior actions, desired outcome, permissions, urgency, or promised updates. The customer reuploads documents or restates sensitive details to each team. Context loss raises effort and can create contradictory instructions.

Inspect the handoff packet and role access. Transfer the minimum relevant case summary, not unlimited personal data. Keep a coordinating owner until another role explicitly accepts responsibility. Correct the system boundary rather than training customers to write longer messages.

Evidence: UK Government Digital Service; GOV.UK Design System

Signs 3 and 4: the channel cannot solve the case and nobody owns the outcome

Sign 3 appears when a bot, email, phone, or form lacks the evidence, dialogue, accessibility, security, or authority the case needs, yet no alternate path exists. Sign 4 appears when several teams respond but each can only refer elsewhere. A queue name is not ownership.

Compare channel capability with issue complexity and consequence. Identify which role can make the required state change and whether the current owner can reach it. Escalate high-impact, security, safety, financial, or deadline-sensitive cases by predefined rules, not by customer persistence.

• Channel cannot receive necessary evidence.
• Automation repeats a script after failure.
• No role has resolution authority.
• Customer must discover organizational boundaries.

Evidence: UK Government Digital Service; UK Financial Conduct Authority

Signs 5 and 6: status says nothing and escalation returns to the same queue

Sign 5 is a status such as “being handled” without owner, next action, review time, or dependency. Sign 6 is escalation that changes priority text but returns to the same workflow, or offers a manager who cannot alter the decision. The customer receives reassurance without additional capability.

Trace states to actual events and record escalation acceptance. Tell the customer what changed, who now acts, and when the next update occurs. If a third party controls timing, say so and explain the available route after the estimate passes.

Evidence: UK Government Digital Service; GOV.UK Design System

Sign 7: closure protects metrics while the requested state remains unchanged

Cases close after one unanswered message, a workaround, a policy quotation, or an internal task even though access, charge, delivery, refund, correction, or explanation remains unresolved. Repeat contacts open new references, fragmenting the evidence. Satisfaction requests may arrive before the customer can verify the result.

Define resolution proof by category and distinguish resolved, pending external action, withdrawn, duplicate, and unable to resolve. Provide a confirmation, remaining limitation, and appeal or alternate route. FTC consumer advice contributes the customer's record-and-escalation perspective without deciding the case.

Evidence: U.S. Federal Trade Commission Consumer Advice; GOV.UK Design System

Repair the earliest trap and route evidence into service change

Build a trace with entry, category, severity, channel, owner, status, handoff, escalation, evidence, resolution event, closure reason, repeat contact, and service cause. Fix the earliest broken stage, then retest dependent paths. Review whether lower ticket volume reflects prevention or inaccessible support.

Recheck by 2027-02-10 and after product, policy, staffing, channel, accessibility, or risk changes. FCA material is a scoped UK financial-services example, while GDS and GOV.UK provide service-design references. Serious consumer, legal, security, or safety matters require qualified routes.

Evidence: UK Government Digital Service; UK Financial Conduct Authority; U.S. Federal Trade Commission Consumer Advice; GOV.UK Design System