Hospital consent yield
Apollo Hospitals · Bangalore Cluster · CMO / CFO view
Revenue assumptions
Illustrative · viewer-adjustableGranted-consent counts are read directly from the registry - they are not assumptions. The only estimated input is the monthly revenue each opted-in patient is worth per bucket. Edit the rates below and every number on this page recomputes. That is what makes the headline figure auditable: it is always granted count × a rate you can see.
Defaults shown are placeholder planning figures, not Certinal or Apollo data. Replace with your own ARPU / campaign-margin numbers to model your book.
By marketing bucket
Appointment reminders
marketing_appointment_remindersHealth tips
marketing_health_tipsPartner offers
marketing_third_party_offersLast 30 days · daily consent volume
What this view tells the CMO/CFO
- •Reminders bucket lifts opt-in dramatically when framed as a value exchange (“free SMS reminders”) vs generic “Allow marketing” copy. Test the variant rows below - the lift is real.
- •Each bucket is its own DPDP-clean consent. Patients can grant reminders while denying third-party offers. This is what specificity looks like under DPDP Rule 3 - and it's also what hospital CFOs need to monetize the opted-in subset without violating the un-opted-in subset.
- •Revenue is computed only from granted consents. Withdrawn or denied consents drop out automatically. The granted counts are read from the registry; the only estimate is the per-grant rate, which lives in the editable assumptions panel above - so the headline is always granted count × a rate a regulator could inspect.