Playbook, healthtech app
The reset email arrives and the sign in still fails
Almost every message here is really about the step after the password. A health account usually carries a second factor, often a recovery code issued once at sign up, and often a handset the app has learned to trust, so somebody who resets the password on a laptop still cannot get into the phone with the readings on it.
Why this is not the general answer
The handling pattern for password resets holds across every trade. What follows is the part that does not.
- The password is rarely the broken thing. It is the second step, the recovery code nobody kept, or a handset that has been replaced, and a reply made of reset instructions leaves all three untouched.
- Opening the app with a fingerprint or a face hides the password for months, so the first time anybody needs it is on a new phone, which is also the moment the second step stayed behind on the old one.
- Households share tablets, and a health app left signed in as one person on a shared device is a disclosure waiting to happen, so the sign out route belongs inside the reset answer rather than in a note nobody opens.
- Nobody at your end can read a password and nobody can read a recovery code either, and saying that plainly matters more here than elsewhere, because the belief that support can look it up is what keeps somebody waiting instead of acting.
How it arrives
- i reset my password and it still wants a code
- i have lost the recovery code you gave me when i signed up
- my new phone will not accept the sign in
- the app opens with my face but now it wants a password
- how do i sign out of the app on my old tablet
- can someone read my password back to me
What has to be indexed for this to work
| The sign in guide, written as steps in order | What happens after the password: the second factor, the code, the trusted handset. Somebody stuck is stuck at one of those, and a guide describing only the first step cannot help them work out which. |
|---|---|
| What the recovery code is, and the route back when it is gone | When it was issued, what it is for, and what somebody does having lost it. This is the document most often missing and the one the hardest version of this question needs. |
| Moving the app to a new handset | What has to be set up again, what carries over, and what to do when the old phone is not available. Handsets are replaced constantly and most instructions assume the old one is still in the person's hand. |
| Signing out everywhere, written for a shared device | The route to end other sessions, aimed at a household tablet rather than at a stolen laptop. A health app left signed in is read by whoever picks the device up next. |
The reply
If the reset worked and it still will not let you in, the step you are stuck on is probably the one after the password, and the sign in guide sets those out in order [1]. A new handset is a common cause, because the second step was set up on the old one, and there is a separate route for that [2]. Nobody here can read a password or a recovery code back to you, and I cannot send anything, reset anything or see whether an account exists. Leave your name, an email you can read and what the screen says, and the team will pick it up. If you are waiting on this and something about your health has changed, please contact your own doctor rather than the app.
It names the second step first, because the reset instructions have already been tried by the time anybody types. The new phone case is volunteered since it explains most of what gets reported as a broken reset. Saying outright that nobody can read a code back removes the belief that keeps somebody waiting for a reply instead of following the route.
Where it stops
The trigger. The visitor has already completed a reset and still cannot sign in, has lost the recovery code, or is asking about a handset they no longer have.
I cannot send a link, reissue a code or see anything about an account. Leave your name, an email you can receive mail at and what the screen shows when you try, and it goes to the team as it is.
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 ask for a password, a recovery code, a one time code or a date of birth in the chat, and never accept one when it is offered.
- Never say a reset message has been sent, delivered or received, since nothing here triggers or observes one.
- Never confirm that an account exists for an address, because on a health product the existence of the account is itself information about a person.
- Never suggest using a household member's sign in to reach something quickly, since that is somebody else's record.
Questions
- Why is the recovery code the part that hurts?
- Because it is issued once, at the least memorable moment there is, and it is needed at the most stressful one. If you have a route for somebody who has lost it, publish that route. If you do not have one, say so and name what happens instead.
- Can it check whether the reset email was delivered?
- No. It has no view of mail, of accounts or of sign in attempts. It can explain the order of the steps and what invalidates a code, which is what most of these messages actually need, and hand the rest over.
- Should the shared device advice really sit in this answer?
- Yes. The person asking is often on a tablet several people use, and a health app left signed in on it is a larger problem than the one they wrote in about. One sentence with the route attached is enough.
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 password resets in generalAn assistant cannot reset anything. It can walk somebody through your real flow and name the step that usually breaks.
- The plan price is not the price of being seenConsultation allowances, the plan that has none, and the medicine priced somewhere else. Publishing a health price so nobody is surprised twice.
- The person seen and the person billed are often not the sameThe receipt someone claims back on, the invoice that goes to an employer, and why neither of them should state a clinical reason.
- The person who wants out did not sign up, and cannot leaveFunded access ends without the user deciding, and the record stays behind. Notice, the last day, and the copy taken before it rather than after.
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.