Obstruction · Australia
Customer-support obstruction
Customer-support obstruction is a working label for this design mechanism: Access to support needed to resolve a purchase, account, charge or right is hidden or burdened by unnecessary loops and dead ends. This is editorial implementation guidance for Australian journeys, not a finding of unlawfulness. From 1 July 2027, a similar interface is relevant to ACL section 28B only if the complete consumer-connection, manipulation or unreasonable-distortion and actual-or-likely-detriment test is met. Current ACL rules require a separate assessment.
- 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. This is a design and research taxonomy for learning and evidence review, not a statutory offence label or an automatic finding that an interface is unlawful.
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 · 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.
Potential consumer harm: A customer may be unable to dispute a charge or preserve evidence of the request.
Illustrative example 2 · 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.
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 (4)
- The bot repeats three articles and closes the conversation after each answer.Why this state matters: 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.
- Unconfirmed state: Start overReview prompt: How many steps, waits and channel changes separate “Start over” from the completed billing support outcome?
- A written escalation route preserves the history and creates a case number.Fairer design: Provide an accessible escalation route, retain the conversation and issue a case reference when self-service cannot resolve the issue.
- Persisted account state, expanded: The saved state behind “Send to support” remains consistent after refresh and across supported channels.Review prompt: 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?
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 (4)
- An order number is mandatory for every topic.Why this state matters: 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.
- Enter order numberReview prompt: How many steps, waits and channel changes separate “Enter order number” from the completed pre-sale accessibility query outcome?
- Pre-sale questions can be sent without purchase data.Fairer design: Ask only for information relevant to the enquiry and provide routes for pre-sale, account and order support.
- Purpose and refusal effect, expanded: The form explains why “Send accessibility question” is requested and what happens if it is not used.Review prompt: 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”?
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
How Australian law may apply
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. These harms describe a review risk, not an automatic legal conclusion. Australian section 28B commences on 1 July 2027 and requires its complete, context-specific test. Existing ACL provisions remain a separate current-law assessment.
ACL section 28B, inserted by the 2026 Act
Possible risk indicator
In account management and pricing journeys, the customer-support obstruction mechanism may warrant review where it manipulates a consumer or unreasonably distorts the decision environment and causes, or is likely to cause, detriment. The obstruction label and an interface similarity do not establish a contravention; the complete section 28B test, scope, facts and evidence must be applied from 1 July 2027.
Dark-pattern research taxonomy
Editorial analysis
The cited research sources support this working pattern within the obstruction family. It is editorial implementation guidance, not an Australian statutory category, regulator finding or legal safe harbour.
Evidence layers and open questions
Applicable law, enforcement records, policy preparation, stakeholder input, editorial analysis and unknown future details remain visibly distinct.
Final Act mappingEditorial implementation guidance
This editorial practice label is not itself an express statutory prohibition. Apply the complete provision and its scope to the facts.
Possible general-test applicationCommences 1 July 2027
ACL section 28B, inserted by the 2026 Act: In account management and pricing journeys, the customer-support obstruction mechanism may warrant review where it manipulates a consumer or unreasonably distorts the decision environment and causes, or is likely to cause, detriment. The obstruction label and an interface similarity do not establish a contravention; the complete section 28B test, scope, facts and evidence must be applied from 1 July 2027.
Existing ACLCurrent enforcement
Existing ACL provisions continue to apply on their own elements before and after commencement. The 2027 provisions must not be applied early.
Verified enforcement contextCurrent enforcement
No named pattern-specific enforcement example is asserted on this page. Existing ACL analysis remains fact-specific and separate from the 2027 provisions.
RegulationsRegulation pending
Later regulations may affect specified exclusions, matters or exceptions. That uncertainty does not postpone a core enacted rule unless the provision itself depends on prescription.
Regulator implementation materialGuidance pending
Government funding and parliamentary material anticipate regulator education and guidance. No dedicated final ACCC implementation guide is treated here as published.
Journey and evidence recommendationsEditorial implementation guidance
Provide a discoverable support route, preserve context, and offer viable escalation for unresolved material issues. This is editorial portal guidance, not a statutory duty, regulator safe harbour or compliance certificate.
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.
- Boundary to test: Reasonable queue or documented service hours
- Boundary to test: self-service that fully resolves the issue
- Boundary to test: support not relevant to the scanned transaction
When a similar design can serve a legitimate purpose
- Reasonable queue or documented service hours
- self-service that fully resolves the issue
- 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?
Evidence to retain
- Annotated account management and pricing screenshots at each responsive breakpoint
- The complete state sequence before, during and after the consumer decision
- Design-system component, content, default and configuration records for the reviewed release
- Operational records substantiating price, availability, timing and eligibility claims
- Usability, accessibility, reversal, complaint and support evidence relevant to consumer impact
- A dated product and legal review record identifying evidence, uncertainties and release decisions
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
- Competition and Consumer Amendment (Unfair Trading Practices) Act 2026Federal Register of Legislation · Primary · checked 2026-09-14 · C2026A00064
- Competition and Consumer Act 2010, including Schedule 2: Australian Consumer LawFederal Register of Legislation · Primary · checked 2026-09-14 · C2004A00109
- Unfair trading tricks and traps to be bannedTreasury Ministers · Primary · checked 2026-09-14
- Inquiry into the Competition and Consumer Amendment (Unfair Trading Practices) Bill 2026Senate Economics Legislation Committee · Primary · checked 2026-08-09