Legal
Refund logic should be tightened alongside payment setup, support scripts, and pharmacy operations before going live.
Consultation fees may become non-refundable once a doctor has materially reviewed the case, subject to the final policy and applicable law.
Operational errors, duplicate payments, or failed service fulfilment should trigger a support-led review.
Medication and delivery refunds depend on prescription status, pharmacy handling, and whether the order has already shipped.
Support should be able to tag and escalate refunds, delays, side effects, cancellations, and privacy requests.
Users should be able to contact support through the published support and grievance channels.
Final launch should define turnaround times, refund windows, and escalation ownership.