A patient who finishes a first consultation on your app is at the weakest point of the relationship. The problem that brought them in has been discussed, a prescription or advice has been delivered, and the app has served its purpose. Whether they open it again depends on what happens in the next few days: whether they can find their records, whether anyone follows up, whether they know what to do if the advice does not work.
This article is for product and growth leads at consultation and condition-management apps in India. It looks at the 30 days after the first call and what actually brings patients back, using the operational levers you control: records, follow-up, reminders and doctor continuity. It also explains how to measure retention without confusing marketing nudges with clinical need. Published retention benchmarks for health apps are inconsistent in how they define a "return", so we do not quote them; define the metric for your own product and compare against your own cohorts.
For the acquisition side of the funnel, see telemedicine marketing. For bringing back people who have already left, the healthcare retargeting article covers ad-based approaches. This post stays inside the product and the care journey.
First, decide what "back" means
Retention figures mean little until the event is defined. For a consultation app, there are several candidates:
- Opened the app again
- Viewed their records or prescription
- Completed a prescribed step, such as booking a test
- Sent a message to the doctor
- Booked a second consult
These are not equivalent. Opening the app can be driven by a push notification and says little about value. A second consult is the clearest signal of repeat demand, but for a patient with a one-off problem it may be inappropriate to count the absence of a second consult as failure. A patient who recovered and never returned has had a good outcome.
Separate patients into two groups when you analyse:
- Patients with a clinical reason to return. The doctor advised a review, a follow-up test or a medication check.
- Patients with no clinical reason. The issue was resolved or one-off.
Measure return rate for the first group and engagement for the second. Pushing the second group to book another consult is not retention; it is a nudge that may erode trust. Whether a patient needs a follow-up is a clinical judgement. Your product should capture the doctor's recommendation, not infer one.
Capture the follow-up instruction at the end of the call
The most useful single change is to have the doctor record a structured follow-up recommendation before closing the consult. A short set of fields works:
- Follow-up advised: yes, no, only if symptoms persist
- Suggested timeframe: for example, in one week, in one month
- Tests advised: none, or a list from a defined set
- Warning signs: a brief doctor-approved line on when to seek urgent care
Each field becomes a trigger. If the doctor advised a one-week review, the app can remind the patient on day six. If tests were advised, the app can prompt the patient to book them and later route the result back to the doctor. If no follow-up was advised, the app does not send a manufactured reminder.
This also respects the Telemedicine Practice Guidelines, which place clinical decision-making with the registered practitioner. The guidelines are available from the eSanjeevani site; your clinical lead should confirm how your workflow reflects them.
Make the record easy to find
A large share of the "I don't know what to do next" problem is a records problem. After the call, the patient should be able to find in one place:
- The consultation summary or advice in plain language
- The prescription, in a form they can show a pharmacy
- Test orders and results
- The doctor's name and how to reach the same doctor again
- The follow-up date, if one was advised
Send the summary promptly, and make the destination obvious. If you deliver by message, include a link that opens the right screen rather than the app's home page. Test the path with real users: ask someone unfamiliar with the app to find last week's prescription and time how long it takes.
Records carry privacy obligations. Under India's Digital Personal Data Protection Act, 2023, you need to process health data under a valid notice and consent, and you should plan for access, correction and erasure requests. App stores add their own rules. Apple's App Review Guidelines state in section 5.1.3 that apps may not use or disclose health data gathered in a health context to third parties for advertising or marketing, other than for improving health management. That limits any plan to export consultation data to ad platforms for retargeting. Keep re-engagement inside owned channels.
Timing the first 30 days
A simple structure for the month after the first call, to be tuned to the condition and approved by your clinical team:
| Day | Touchpoint | Purpose | Condition |
|---|---|---|---|
| 0 | Summary and prescription delivered | Confirm what happened | Always |
| 1 to 2 | Check-in message | Ask if the advice was understood and the prescription was filled | Always, short |
| 3 to 5 | Medication or test prompt | Prompt step the doctor advised | Only if advised |
| Doctor-set date | Follow-up reminder | Book a review | Only if advised |
| 14 to 21 | Outcome question | Ask how the patient is doing | Where clinically suitable |
| 28 to 30 | Next-step message | Offer review, or confirm no action needed | By case |
Keep each message useful. A message that says "We miss you" has no clinical content. A message that says "Dr. Sharma advised a review in a week; here are available slots" does. Use plain language and the patient's chosen language where possible.
Channel choice matters. Many Indian patients respond more readily to WhatsApp than to push notifications, and they may have disabled app notifications. If you use WhatsApp, the sender must follow the platform's opt-in and template rules; the WhatsApp healthcare guide explains how clinics set this up, and your consent record should note the channel.




