Playbook, healthtech app
It is a support question until somebody describes how they feel
Two things break here and neither is exotic. The app will not start on a handset that updated overnight, or a connected device has stopped pairing and the readings have stopped arriving with it. Both are answerable from documents. What makes this different from any other support page is the sentence that arrives halfway down, where somebody explains why the missing readings worry them.
Why this is not the general answer
The handling pattern for technical troubleshooting holds across every trade. What follows is the part that does not.
- A device that has stopped sending is not only a hardware problem, because the days it did not record are days missing from a record somebody may be shown later.
- Pairing failures sit across two things the service does not control, the handset and the device, so honest material names the versions that were tested rather than promising it will work.
- The moment a message contains a symptom it stops being a support question, whatever it started as, which means the reply changes destination rather than answering the technical half and carrying on.
- Asking for more detail is normally free, but every extra question here risks collecting health information through a public chat box, so the list of what to gather is written narrowly and stuck to.
How it arrives
- the app shuts itself down the moment i open it
- my device stopped syncing three days ago
- how do i pair it again after changing phones
- the readings are missing for the weekend
- does the app work on an older phone
- it says i am offline but everything else works
What has to be indexed for this to work
| The supported handset and operating system list, with versions | What has been tested and what is no longer covered. On a product people keep on an old phone for years, a vague statement produces a fault report nobody can act on. |
|---|---|
| The pairing guide, written for a replacement handset | The steps to connect a device to a phone that is not the one it was set up on. Handsets are replaced far more often than these devices are, and most guides quietly assume the original. |
| What a gap in the data means for the record | Whether missing days can be filled in, what happens to them if not, and who should be told. Somebody who has spotted a gap is asking whether it matters, and that deserves a written answer rather than an improvised one. |
| What the team needs in order to look at a fault | The handset, the operating system version, the app version and the time it started. Keep the list this short deliberately, because anything longer starts collecting information about somebody's health. |
The reply
If the app will not open, the supported handsets and versions are listed on our help page, and it is worth checking whether a recent update moved yours off that list [1]. If a device has stopped sending, the pairing guide covers reconnecting after a phone has been replaced, which is the usual cause [2]. Whether missing days can be recovered is answered on the same page. I cannot see your account, your device or your data. Leave your name, an email, your handset and the app version and the team can start. If any part of this is about how you are feeling rather than about the app, please contact your own doctor, or the urgent route on this site, instead.
It separates the two faults immediately, because the fixes have nothing in common and a general answer serves neither. The gap in the data is treated as a real question rather than a side effect, since that is what the person is actually worried about. The final sentence is the whole reason this page is worded differently from any other troubleshooting page.
Where it stops
The trigger. The fault survives the published steps, several days of data are missing, or the message describes a symptom, a reading that is worrying the person, or anything else about their health.
This needs somebody who can look properly, which I cannot do. Leave your name, an email, your handset and the app version and it goes to the team. If your message is about a symptom, or about a reading that is worrying you, please contact your own doctor now, or the emergency services if it is urgent, rather than waiting on a technical reply.
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 interpret a reading, a trend or a missing period of data, whatever the person says about it.
- Never call something a known fault unless your own published list says so.
- Never say a handset, an operating system version or a device is supported when it is not on the tested list.
- Never ask a person for symptoms, conditions or medicines in order to troubleshoot a device.
Questions
- How should it handle a message that is half technical and half clinical?
- It should answer neither half in place. Point at the technical material, say plainly that the rest belongs with a clinician, and route it. Answering the app question and ignoring the other sentence is the failure that matters here.
- Can it say whether somebody's missing days can be recovered?
- It can quote what your material says happens. It cannot look at anybody's data, so it must not say whether a particular gap will be filled, and the difference between those two sentences is worth being careful about.
- Why keep the detail list so short?
- Because every extra question on a health product is a chance to collect something you did not want sitting in a chat log. Handset, version and time are enough to open an investigation, and nothing else is needed before a person is involved.
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 technical troubleshooting in generalThe dominant failure is an answer taken from the wrong release. A refusal beats a confident step list for software nobody is running.
- Most of what blocks a new account has nothing to do with the appEligibility by country and by age, the access code from a sponsor, and the questions asked at sign up. What a first afternoon really runs into.
- The message that has to leave this channel immediatelyTwo routes, one about the software and one about the clinician, with different reviewers and different clocks. How to sort them in one reply.
- The app is awake at three in the morning and nobody else isConsultation hours, a clinician rota across time zones, and a user who has travelled. What an overnight message needs in its first line.
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.