Playbook, healthtech app
The person who wants out did not sign up, and cannot leave
Three different endings arrive under one word. A subscriber wants to stop paying. Somebody funded through work wants out of a service they never chose and cannot cancel, because they are not the customer. And somebody is leaving a job, so access ends whether they want it to or not, taking a record with it.
Why this is not the general answer
The handling pattern for cancellations holds across every trade. What follows is the part that does not.
- The person asking is frequently not the account holder in any commercial sense, because an employer or an insurer holds the arrangement, and the only cancellation available to them is to stop opening the app.
- Ending access to a health service ends access to a record, so a useful answer says what happens to that record and how to take a copy before the last day rather than after it.
- Sponsored access usually ends on a date decided by somebody else, often the day employment ends, which means the notice that matters is the sponsor's rather than any published subscription term.
- Somebody cancelling may have a consultation booked or a repeat arrangement running, and assuming continuity is how a person ends up short, so the answer has to name what stops on the last day.
How it arrives
- how do i stop using this if my company signed us all up
- i am leaving my job what happens to my account
- can i download everything before my access ends
- does cancelling delete my consultation history
- i have an appointment booked and i want to cancel the subscription
- how much notice before my access actually stops
What has to be indexed for this to work
| How each arrangement ends, listed by who pays | Direct subscription, employer funded, insurer funded. Each has a different last day and a different person who decides it, and one paragraph written for subscribers answers only one of the three. |
|---|---|
| What happens to the record after the last day | What is kept, for how long, on what basis, and what becomes unreachable immediately. Health records commonly carry retention duties that outlive a cancellation, so a page promising a clean break will not survive being read carefully. |
| The export route, and how long it takes | How somebody takes a copy of consultations, documents and readings, in what format, and how far ahead of the last day to start. The lead time is the useful half, because a person asking on the final afternoon has already left it late. |
| What stops working on the last day | Booked consultations, repeat arrangements, reminders, device syncing. Written as a list, since the belief that something will carry on for a while is what catches people out. |
The reply
How access ends depends on who is paying for it. A direct subscription is cancelled in the account settings with the notice period on our terms page, and where an employer or an insurer funds it they hold the arrangement and the last day is set by them [1]. Before that day it is worth taking a copy of your consultations and documents, and the export route and how long it takes are on the same page [2]. What is kept afterwards, and for how long, is in the retention section. I cannot cancel anything, see an arrangement or start an export. If you have a consultation booked or medicine due for review, please sort that out with the service or your own doctor before your access stops.
It sorts by payer first, because two of the three people asking cannot cancel at all and every other sentence is wasted on them. The export is raised before the last day rather than after it, which is the only point at which raising it helps. The closing line is not a general disclaimer, it names the two things that lapse and leave somebody stuck.
Where it stops
The trigger. The visitor asks for a subscription to be cancelled, asks when funded access ends, or says they are leaving an employer and want a copy of their record.
I cannot cancel anything, see when an arrangement ends or start an export. Leave your name, an email you will still be able to read after your access stops, and what you need, and it goes to the team.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- Never say access has been cancelled, extended or reinstated, because nothing here changes an arrangement.
- Never state a last day for funded access, since it is set by the organisation paying rather than by anything published here.
- Never promise that a record will be deleted, or that it will be kept, beyond what your retention material states.
- Never tell somebody their care will carry on uninterrupted once access ends.
Questions
- Most of these people cannot cancel. Is the page worth writing?
- That is the reason to write it. Somebody funded through work who is told plainly that their employer holds the arrangement stops hunting for a button that does not exist, and what reaches you afterwards is the message that genuinely needed a person.
- Should the export be mentioned when nobody asked?
- Yes, and early. Nobody thinks about a copy of their record until the access has gone, and by then the answer is worse for everybody. One sentence with the lead time attached is the whole intervention.
- Can it tell somebody what will be removed from their record?
- No. It has no view of any record and cannot look anybody up. It can quote what your retention material says is kept and for how long, which is a statement about the policy rather than about the person.
Keep reading
- Everything for a healthtech appHealth data is a special category and clinical claims carry device rules. What a healthtech assistant answers for patients, and for buyers.
- Handling cancellations in generalCancellation content is hard to find on purpose. What it costs to answer plainly, how notice periods work, and what happens to data on the way out.
- A refund request about care is not a refund requestA dropped call, a consultation cut short, and a refund asked for because the answer was unwelcome. Three requests, and two different routes.
- The card failed, and something behind it has a date on itA declined card on a health service is a continuity problem. The retry dates, what stops working on each of them, and the part that cannot wait.
- The one question where a fluent answer is the wrong oneAn outage with a booked slot behind it. Why the assistant cannot see the service, and the route that must never run through the thing that broke.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.