Define the purpose of each pharmacy queue
Separate refill follow-up, pharmacy-confirmed ready prescriptions, delivery-status questions and unresolved callbacks. Each queue needs its own approved introduction, permitted tasks and receiving owner. A medication reminder and a request to refill are different events; record them separately. Work from pharmacy-approved existing-patient lists and contact permissions, rather than treating a purchase history as permission for every kind of outreach.
Confirm identity before discussing the record
Use the pharmacy’s approved identity and caregiver-permission checks. Limit voicemail and third-party messages to the approved wording. Ask about the patient’s preferred contact method and callback time, and record restrictions in the designated system. If the person cannot be verified, follow the approved stop or callback process instead of continuing into prescription details.
Record a request without promising a fill
An agent can document that a patient has asked the pharmacy to review a refill. The pharmacy checks whether the prescription is valid, whether refills remain and whether timing, payer and dispensing requirements are met. Avoid describing an administrative request as an approved prescription or a completed refill.
For example, a patient asks for a refill but says they have a question about their dose. Record the request and route the dose question to the pharmacist using the approved escalation process. The agent should not answer the medication question or imply that dispensing has been approved.
Make pharmacy and delivery handoffs visible
Give every unresolved request a receiving team, recorded status and follow-up owner. Only send a ready-for-pickup reminder when the pharmacy has confirmed that status. For mail-order work, use the pharmacy’s approved delivery information and route exceptions to the appropriate team. A request, dispensing event, shipment and confirmed delivery are distinct milestones. The mail-order pharmacy support model should preserve those distinctions.
Use reminders within the approved scope
Agents can provide pharmacy-approved reminders and help patients reach the right person. Questions about missed doses, side effects, interactions, treatment changes or symptoms belong with the pharmacist or designated qualified team. Follow the pharmacy’s escalation instructions. A successful reminder call does not establish that a patient took a medication or demonstrate an adherence improvement.
Report the work that can be verified
Track attempted contacts, verified conversations, patient requests, pharmacist handoffs and pharmacy-confirmed pickup or delivery separately. Report open requests by age and owner so staff can find work awaiting review. GoHealth 360’s pharmacy refill and reminder call support starts at $12 per administrative agent-hour with a five-agent minimum; scope, staffing hours and measures are agreed before launch.
Common questions
Can a call-center agent approve a pharmacy refill?
No. An administrative agent can record the patient’s request. The pharmacy retains prescription validation, clinical review and dispensing decisions.
Do reminder calls prove medication adherence?
No. A completed call documents contact or an approved reminder. Medication adherence claims require appropriate evidence and cannot be inferred from a call disposition.
About this operational guide
Prepared by GoHealth 360. Updated October 27, 2026. This is an administrative workflow framework to adapt to your organization’s approved roles, systems and service requirements.
Editorial standards ↗