Obstruction · European Union
Customer-support obstruction
The label “Customer-support obstruction” describes this recurring design mechanism: access to support needed to resolve a purchase, account, charge or right is hidden or burdened by unnecessary loops and dead ends. It is a design and research taxonomy, not a standalone legal conclusion. Depending on the complete journey and likely effect, current EU consumer or sector rules may require separate assessment. No published Digital Fairness Act proposal currently creates a pattern-specific prohibition or duty under this label.
- Family
- Obstruction
- Also known as
- Journey stages
Definition
What is this pattern?
Access to support needed to resolve a purchase, account, charge or right is hidden or burdened by unnecessary loops and dead ends. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.
How it works
Access to support needed to resolve a purchase, account, charge or right is hidden or burdened by unnecessary loops and dead ends. Self-service loops or irrelevant prerequisites prevent a user from raising the actual issue and preserving a case through an accessible support route.
Warning signs
- Support is materially needed for a consumer issue connected with supply.
- Available routes are difficult to find, repeatedly loop or lack a viable escalation path.
- The obstruction plausibly delays or prevents remedy.
Potential harms
- A customer may be unable to dispute a charge or preserve evidence of the request.
- Potential customers cannot obtain material support because the form assumes a completed transaction.
Learn by comparison
What does this look like?
These fictional examples make the design mechanism easier to recognise. They do not depict a real company and do not establish that an individual interface is unlawful.
Illustrative example 1 · Billing support
A fictional subscription service routes every “charged after cancellation” message through the same three bot articles and offers no human or written case route.
Potential consumer harm: A customer may be unable to dispute a charge or preserve evidence of the request.
Illustrative example 2 · Pre-sale accessibility query
A fictional retailer’s only contact form requires an order number and rejects enquiries from people seeking accessibility information before purchase.
Potential consumer harm: Potential customers cannot obtain material support because the form assumes a completed transaction.
Support bot loops without escalation
A fictional subscription service routes every “charged after cancellation” message through the same three bot articles and offers no human or written case route.
How can we help?. The bot repeats three articles and closes the conversation after each answer.. Start over. Unconfirmed state: Start over
Billing issue not resolved. A written escalation route preserves the history and creates a case number.. Send to support. Saved state: Send to support. Persisted account state, expanded: The saved state behind “Send to support” remains consistent after refresh and across supported channels.
Why the first version can mislead: The route adds avoidable effort between the user’s stated intention and completion. In this billing support example, the obstacle is: “The bot repeats three articles and closes the conversation after each answer.” Evidence should show whether the alternative remains usable and whether “Send to support” reaches the represented state. A customer may be unable to dispute a charge or preserve evidence of the request.
What a fairer design does: Provide an accessible escalation route, retain the conversation and issue a case reference when self-service cannot resolve the issue.
Show annotated differences (2)
- Unconfirmed state: Start overIn “Support bot loops without escalation”, this element shows how customer-support obstruction can shape the decision.
- Persisted account state, expanded: The saved state behind “Send to support” remains consistent after refresh and across supported channels.In “Support bot loops without escalation”, this element keeps the clearer alternative visible at the same decision point.
Review questions (3)
- How many steps, waits and channel changes separate “Start over” from the completed billing support outcome?
- Test the control across refresh, device and account states; is “Support is materially needed for a consumer issue connected with supply” still observable after persistence is considered?
- Measure the same task through the clearest available route: does the effort difference persist once “Reasonable queue or documented service hours” is accounted for?
Contact form requires irrelevant purchase data
A fictional retailer’s only contact form requires an order number and rejects enquiries from people seeking accessibility information before purchase.
Contact customer care. An order number is mandatory for every topic.. Required order number: Enter required order number. Question: Enter question. Enter order number
Choose an enquiry type. Pre-sale questions can be sent without purchase data.. Email address: Enter email address. Accessibility question: Enter accessibility question. Send accessibility question. Purpose and refusal effect, expanded: The form explains why “Send accessibility question” is requested and what happens if it is not used.
Why the first version can mislead: The route adds avoidable effort between the user’s stated intention and completion. In this pre-sale accessibility query example, the obstacle is: “An order number is mandatory for every topic.” Evidence should show whether the alternative remains usable and whether “Send accessibility question” reaches the represented state. Potential customers cannot obtain material support because the form assumes a completed transaction.
What a fairer design does: Ask only for information relevant to the enquiry and provide routes for pre-sale, account and order support.
Show annotated differences (2)
- Enter order numberIn “Contact form requires irrelevant purchase data”, this element shows how customer-support obstruction can shape the decision.
- Purpose and refusal effect, expanded: The form explains why “Send accessibility question” is requested and what happens if it is not used.In “Contact form requires irrelevant purchase data”, this element keeps the clearer alternative visible at the same decision point.
Review questions (3)
- How many steps, waits and channel changes separate “Enter order number” from the completed pre-sale accessibility query outcome?
- Which fields or permissions are required, what happens on refusal, and does the resulting state support this criterion: “Available routes are difficult to find, repeatedly loop or lack a viable escalation path”?
- Measure the same task through the clearest available route: does the effort difference persist once “self-service that fully resolves the issue” is accounted for?
What is a fairer alternative?
Provide a discoverable support route, preserve context, and offer viable escalation for unresolved material issues.
Legal and information status
Legal position at a glance
Access to support needed to resolve a purchase, account, charge or right is hidden or burdened by unnecessary loops and dead ends. Self-service loops or irrelevant prerequisites prevent a user from raising the actual issue and preserving a case through an accessible support route. Risk increases where the mechanism changes a material consumer choice, hides a consequence or makes a genuine alternative harder to use. The taxonomy label remains a review prompt and does not establish an infringement.
Dark-pattern research taxonomy
Editorial analysis
The cited research sources support identification and comparison of this recurring interface mechanism. They do not determine that a particular interface is unlawful.
UCPD Articles 5 to 9, where applicable
Possible risk indicator
Depending on the trader, audience, overall presentation, material information and likely transactional effect, the facts may require a separate assessment under the applicable UCPD provisions.
Evidence layers and open questions
Applicable law, enforcement records, policy preparation, stakeholder input, editorial analysis and unknown future details remain visibly distinct.
Current lawCurrent law
The UX label “Customer-support obstruction” is not a standalone EU offence. Depending on the trader, audience, complete presentation, omitted information and likely transactional effect, the observed facts may require a separate assessment under the applicable UCPD provisions or another instrument within scope.
Under considerationUnder consideration
The Commission is preparing a Digital Fairness Act initiative, but the call for evidence does not select a final rule for customer-support obstruction or establish that this taxonomy term will appear in a proposal.
Editorial analysisEditorial analysis
The pattern definition, variants and examples on this page use the cited research taxonomy sources to support recognition and comparison. That analytical classification is not a legal conclusion about an individual interface.
UnknownUnknown
No published DFA proposal currently establishes a definition, covered actor, legal threshold, duty, remedy, transition rule or application date for customer-support obstruction. Those details remain unknown pending primary legislative text.
Context matters
Context and boundary cases
- Support is materially needed for a consumer issue connected with supply.
- Available routes are difficult to find, repeatedly loop or lack a viable escalation path.
- The obstruction plausibly delays or prevents remedy.
- Exclude or qualify the label where reasonable queue or documented service hours.
- Exclude or qualify the label where self-service that fully resolves the issue.
- Exclude or qualify the label where support not relevant to the scanned transaction.
When a similar design can serve a legitimate purpose
- A similar design should not be classified this way where reasonable queue or documented service hours.
- A similar design should not be classified this way where self-service that fully resolves the issue.
- A similar design should not be classified this way where support not relevant to the scanned transaction.
Operational review
What teams should review
- Teams
- How many steps, waits and channel changes separate “Start over” from the completed billing support outcome?
- Test the control across refresh, device and account states; is “Support is materially needed for a consumer issue connected with supply” still observable after persistence is considered?
- Measure the same task through the clearest available route: does the effort difference persist once “Reasonable queue or documented service hours” is accounted for?
- How many steps, waits and channel changes separate “Enter order number” from the completed pre-sale accessibility query outcome?
- Which fields or permissions are required, what happens on refusal, and does the resulting state support this criterion: “Available routes are difficult to find, repeatedly loop or lack a viable escalation path”?
- Measure the same task through the clearest available route: does the effort difference persist once “self-service that fully resolves the issue” is accounted for?
- Which complete journey evidence supports or contradicts the customer-support obstruction classification?
Evidence to retain
- Versioned captures of the Account Management and Pricing states before, during and after the relevant decision
- Configuration, content and event records supporting the observed customer-support obstruction mechanism
- Responsive, keyboard and assistive-technology review of every material option and consequence
- Control defaults, validation rules and consent or selection state changes
Legal map and implementation tools
Evidence base
Sources
- An Ontology of Dark Patterns KnowledgeGray et al.; ACM CHI 2024 · Secondary · checked 2026-09-14 · DOI 10.1145/3613904.3642436; arXiv:2309.09640
- Unfair Commercial Practices DirectiveEuropean Parliament and Council of the European Union · Primary · checked 2026-08-09 · Directive 2005/29/EC; CELEX 02005L0029-20220528
- Digital Fairness Act: call for evidence for an impact assessmentEuropean Commission · Primary · checked 2026-08-09 · Initiative 14622; Ares(2025)6275573
- Commission work programme 2026: Europe's Independence MomentEuropean Commission · Primary · checked 2026-09-14 · COM(2025) 870 final; CELEX 52025DC0870; Annex I item 30