THE TEST
AI agents are increasingly presented as systems that will do things for us online, not merely answer questions.
So I gave the idea a deliberately boring test: find the official route for cancelling five common subscription services used by UK customers—Netflix, Spotify, HelloFresh, PureGym and Strava.
I did not sign in, access an account or cancel anything. I assessed only the official public instructions available on 14 August 2026.
The webpage was rarely the hard part. The hidden decision tree was.
PILOT RESULTS
Clear routes. Complicated context.
Official page found
Every service published a cancellation route that could be read before signing in.
Digital path
Every ordinary case included a route that could be completed online.
Context branches
Billing provider, purchase channel, plan type or account role changed the required action.
Timing rules
A deadline could affect the next charge, renewal or delivery.
THE FIVE STOPS
What the official routes said
Step counts describe the ordinary public route. They are not a usability ranking and do not include authenticated account screens.
Netflix
The ordinary route is short, but payment-partner billing can replace it and pausing is presented as an alternative.
Read the official instructionsSpotify
Plan managers, plan members, partner billing and multiple-account cases can require different actions.
Read the official instructionsHelloFresh
The digital route is explicit, but changes must be made by 11:59 PM five days before the next delivery.
Read the official instructionsPureGym
Monthly, fixed-term, corporate and day-pass memberships differ. Monthly cancellation must precede payment by four working days.
Read the official instructionsStrava
The cancellation channel must match the purchase channel, while renewal requires at least 24 hours’ notice.
Read the official instructionsWHAT THE TEST EXPOSED
Agent experience is a business-rules problem.
The encouraging result was that all five services published understandable instructions and a digital route for the ordinary case. The difficult part appeared immediately afterwards.
“Cancel my subscription” may require a system to establish who charged the customer, which account owns the plan, which contract applies, whether a deadline has passed and what consequence the user has actually authorised.
- Publish the branches. A short help page is not enough if the real route changes according to account state.
- Make consequences explicit. Agents need to know whether an action affects the next charge, delivery or access date.
- Separate guidance from permission. Finding a route is not authority to perform an account-changing action.
- Design safe exceptions. Partner billing, ownership ambiguity and missed deadlines need recoverable routes.
Agent experience is therefore not simply whether AI can read your website. It is whether your rules, states and exceptions are explicit enough for a system to act safely.
METHOD AND LIMITS
A small directional pilot
Five services are not a representative ranking of the subscription economy. The test records what could be independently verified from official public pages on one date. No authenticated journey or completed cancellation was observed.
THE USEFUL QUESTION
Could an agent explain why the route changes?
Making a page crawlable is the beginning. Making the decision tree explicit—and the action permissioned—is what turns information into safe task completion.