01
Step one: define the request and who can make it
Begin with what a person must have ready: prescription details, the pharmacy or prescriber on file, and identity information. State who may request a refill, including caregivers acting with permission, and which medications may need a new prescription instead. In our fictional example, Maria manages her father's blood pressure medication and sees a short checklist: medication name, prescription number if available, and preferred pickup or delivery. Keep sentences short, avoid jargon, and place the action button directly beneath the checklist so the first step feels finite instead of an open-ended form.
02
Step two: show the review and status stages
Next, describe what the pharmacy does after the request arrives: verify the prescription, contact the prescriber if authorization is needed, prepare the medication and notify the patient. Label each stage with the plain wording a patient would use, and say what the patient may be asked to do. In Maria's example, the page shows four stages and explains that a prescriber check can add time, without promising a specific hour. Honest uncertainty builds more trust than a rushed estimate. Include a line explaining that urgent or unusual symptoms should be discussed with a clinician, not handled through a refill form.
03
Step three: close with support, privacy and next refill
Finish by telling people how to reach a pharmacist, what to do if a refill is delayed and how their information is handled. Link to privacy terms in plain language, and explain notification choices such as text or email. In the example, Maria sees a pharmacist contact option, a note about changing delivery details and an optional reminder for the next refill window. End with a short question list she can use if the pharmacy asks for updates. This closing section reduces repeat calls and shows the service remains accountable after the button is pressed.