A salon owner in Almaty opens her booking service to switch off a 12,000 ₸ monthly subscription. She presses the large "Continue" button and closes the page. A month later, another charge arrives: the button kept her subscription even though she meant to finish cancelling.
Suppose the team investigates this case in the salon booking service. The price comes from that example, and the other numbers are illustrative too. The marketer's job starts with restoring a clear choice and investigating charges. Falling cancellations alongside rising complaints do not belong among retention wins.
Where persuasion becomes deception
A service can explain its benefits, offer a better-fitting plan or present a discount while keeping the choice clear. A dark pattern gets the action the business wants through a hidden condition, an obstacle or a misunderstood button.
The Deceptive Design catalogue describes obstructed cancellation, hidden subscriptions and costs, confusing wording and visually hidden information. A category helps name the problem. Repair requires following the customer's path to where their intention diverges from the operation.
Here the intention is: "Stop future charges and keep using the service until the paid period ends." Before acting, the person should understand the consequences; afterwards, they should see the saved state. Confirmation of irreversible deletion or an access check can protect an account. Their purpose and extent need to fit the task.
The picture has "Continue" on the left and two distinct actions on the right. It contains neither an access date nor the request's outcome; those still need to be added to the working interface.
What the customer is cancelling
Our example's terms allow the next renewal to be switched off while access continues until the paid period ends. The subscription is paid through 30 September. The screen therefore shows the current plan, access period and "Turn off auto-renewal". The other choice, "Keep the subscription", leaves it active.
That is the arrangement in this example. If the product ends access immediately, the copy and action must reflect that condition before confirmation. Do not promise continuing access the billing system cannot support.
The team should distinguish the operations:
| Operation | What to explain before the choice |
|---|---|
| Turn off the next renewal | When charges and access end |
| Pause the subscription | What stops, when it resumes and on which terms |
| Change plan | New price, period and when the change takes effect |
| Delete the account | What happens to data, access and active payments |
Account deletion is not a substitute for payment management. Establish what happens to the subscription in each case for your product, then make the connection clear to the customer.
When cancellation can be confirmed
The button sends a request. "Auto-renewal is off; access continues through 30 September" appears after the system has saved the change. If the request fails, the screen explains the failure and preserves a way to try again.
A broken connection needs separate handling. The request may have succeeded even though the browser received no response. Before retrying or reporting an outcome, the application establishes the actual state. Declaring success from a click is dangerous; sending the customer in circles without checking is unhelpful too.
After signing in again, the salon owner sees the same disabled renewal. A cancellation email supplements that record rather than replacing it. Support must be able to find the requested operation and what the system saved.
Use a test subscription for acceptance. Reproduce normal cancellation, a double click, a lost response and a fresh login. The billing record and the on-screen explanation must agree in every case.
A pause offer can be declined
A salon closing for refurbishment may want a pause. The service explains what happens to billing, the schedule and staff access, when they resume and what it will cost. The customer chooses the pause separately.
If the person already chose cancellation, declining the pause returns them to completing that action. A compulsory manager call or a survey that cannot be skipped can turn feedback collection into an obstacle.
"No, I want to lose customers" judges the person instead of describing the operation. Neutral wording such as "Turn off auto-renewal" explains what happens to the subscription. Ask why they are leaving after the action has been saved, when the answer cannot affect its completion.
Retention through product value leaves customers able to leave. If a hidden cancellation button reduces cancellations while complaints rise, restore the clear path. Removing complaints from the report hides the change's consequences.
Terms are visible at signup too
The salon service has a 14-day free trial, followed by a monthly price of 12,000 ₸. If the team offers automatic renewal, the screen must explain when charges begin, the amount, frequency and how to switch it off before agreement. A button for getting a free resource must not also enrol someone in a paid service.
Show mandatory parts of the price before payment confirmation. An additional paid service remains a separate choice. A default interface language and an unchosen paid package need different assessments: the latter changes the customer's obligations.
A limited offer needs a basis. A course intake deadline or stock availability can be presented as it exists. A timer that restarts on every visit while pretending to be a shared promotion deadline misleads the customer.
Forty unfinished cancellations and 480,000 ₸
The service export shows a hundred salons starting cancellation. Sixty receive confirmation, twenty-five encounter an error, and another fifteen close the page without completing it. The team proposes calling the remaining forty retained.
| Attempt outcome | Salons | What is known |
|---|---|---|
| Auto-renewal switched off | 60 | The requested action was completed |
| Cancellation error | 25 | The action could not be completed |
| Page closed without completion | 15 | Reason and subsequent intention are unknown |
| Total who started | 100 | Everyone stays in the analysis of this path |
If renewal stays active for forty salons, their possible next charges total 40 × 12,000 = 480,000 ₸. Of that, 25 × 12,000 = 300,000 ₸ belongs to the error group and 15 × 12,000 = 180,000 ₸ to the group with an unknown reason for leaving. These are possible charges, not profit or an estimate of value added by the service.
The team first fixes the known error, recovers the state from the log and investigates disputed charges already made. A salon prevented from leaving cannot be counted as wanting to continue using the service. The other fifteen cannot automatically be labelled satisfied either.
Report errors, repeated attempts, support requests and later disputed charges alongside completed cancellations. If the same number of people start cancelling, while errors fall and completed cancellations rise, the fix worked. A fall in cancellations alone is insufficient evidence of benefit.
Test understanding and the system
Ask a colleague uninvolved in development to cancel a test subscription. Afterwards, they explain in their own words whether another charge will occur, how long access lasts and how to inspect the result later. Telling them "this button cancels" would spoil the test.
Compare their explanation with the system record. If they believe they cancelled but renewal remains active, the problem survives. If the record is correct but the screen threatens immediate loss of access contrary to the terms, the copy needs fixing too.
On a phone, the conditions are readable without hidden continuation, actions are reachable, and keyboard users can see focus and complete the action. An error preserves a route to retry. Every signup and cancellation method the team supports goes through this acceptance process.
Fix known deception and technical faults without waiting for proof of lost profit. Comparisons can test clear presentations that carry out the chosen action and disclose the terms.
Exercise: the label changed, the action did not
Your project renames a button "Cancel subscription". After pressing it, eight customers enter a one-month pause, with a 12,000 ₸ charge scheduled for each afterwards. They did not choose a pause. Write acceptance criteria for the repair.
The new label did not repair the path: future renewal remains instead of cancellation. The eight potential charges total 8 × 12,000 = 96,000 ₸, but that does not make the pause the customers' choice. The team must perform the requested cancellation. A pause remains a separate offer with explicit agreement to its resumption terms.
Acceptance ends when the chosen operation, system record and customer-understood confirmation agree. An attractive screen without a changed subscription leaves the original problem in place.
Video: how design shapes choice
Sally Woellner's talk at TEDxSydney. Afterwards, inspect your cancellation path: what the person expects, what the system does and what confirms the result.