Refill Reminder Agent

Refill-due outreach and adherence nudges, drafted from fill dates only — never diagnosis.

Beginner~3 hours to buildEnterprise/API AI pricing + $0–15/mo tooling~3 hours/week saved

Be honest about what your PMS already does: PioneerRx, Liberty, Rx30 and most others send a basic "your refill is ready" or "refill due" text on their own, and if you haven't turned that on, do that first — it's free and takes an afternoon. What those systems do badly is the second and third touch: the warmer, personalised nudge when a due date passes with no fill, the tone shift for someone who's been late two months running, and the point where automated texting should stop and a pharmacist should pick up the phone. That's what this agent does. It works entirely from structural data — an internal Rx or patient ID, fill date, days' supply, and refill-due date — and never references a drug name or condition in outward-facing messages; nudges say "your prescription is overdue," never "your metformin is ready." Controlled substances are excluded from automated outreach entirely: they get an internal pharmacist flag, never a drafted text. Even a minimum-necessary refill list is PHI, so the workflow runs only inside a BAA-covered AI environment, and the pharmacist reviews every batch before anything sends.

What this agent takes off your plate

  • Late-refill patients get a second, gentler adherence nudge instead of silently falling off therapy after the PMS's one generic reminder
  • Controlled substances never appear in automated outreach — they route to an internal pharmacist flag only
  • No drug name or condition appears in outward-facing messages by default — "your prescription" language protects patient privacy even if a text is seen by someone else
  • Pharmacist reviews a short daily batch instead of manually tracking refill dates across hundreds of patients
  • A documented adherence-nudge trend you can review monthly for patients who repeatedly run late

The stack

Claude or ChatGPT (Enterprise plan or API build with a signed BAA)Your pharmacy management system export (PioneerRx, Liberty, Rx30, etc.)Zapier or MakeSMS gateway (Twilio or your PMS's built-in texting)

Real costs & ROI

  • Claude or ChatGPT with a signed BAA (Enterprise plan or API build)Enterprise / API pricing — confirm
    As of writing, neither vendor includes a BAA on Pro/Team/Business seats — a BAA is available on Enterprise plans or via an API-based build. Expect materially higher cost than the consumer tiers and get the BAA in writing before any real data is entered.
  • Zapier or Make (paid tier)$0–10/mo
    a busy pharmacy can exceed the free tier's ~100 tasks/month with daily refill checks; the entry paid tier covers most independents
  • SMS gateway (Twilio or PMS-native texting)$0–5/mo
    many pharmacy management systems already include a basic texting module at no extra cost

The math

Non-adherence from simple forgetting is one of the most fixable causes of a patient falling off therapy. Pull your own number first: run your PMS's overdue-refill report for the last 90 days and count the refillable, non-controlled prescriptions that went unfilled or significantly late. Every one of those is lost dispensing revenue as well as a clinical risk — for a pharmacy averaging 150 refills/week at a modest $8 average dispensing margin, closing even a 10% adherence gap recovers roughly $120/week, or about $500/month — get your actual BAA-covered AI pricing in hand before you compare that against running cost. The time saved matters too: a tech currently spending 20–30 minutes a day manually checking refill-due lists gets that down to a 5-minute daily approval of pre-drafted messages.

Build steps

1

Turn on your PMS's built-in reminder, then define the follow-up rules it doesn't cover

First, check that your PMS's native refill-due text is switched on — PioneerRx, Liberty, Rx30 and most others have one, and it handles the first "your refill is due" touch adequately. Then decide what this agent adds: when the late-refill nudge goes out, how its tone differs, and when automated texting stops and a pharmacist calls. This is useful groundwork even before any automation exists.

Data you need

You don't need patient data for this step — just what your PMS already sends (and when), your general sense of typical days'-supply patterns, and how many refills currently go unfilled per week if you know it.

Prompt
I run an independent pharmacy. My pharmacy management system already sends a basic refill-due text. I want to define timing rules for the follow-ups it doesn't do: late-refill adherence nudges and a stop-and-escalate point. Controlled substances are excluded from all automated outreach.

What my PMS already sends and when: [e.g. "one 'refill ready' text the day the refill is processed"]
My typical days'-supply range for refillable prescriptions: [e.g. mostly 30-day, some 90-day]
My rough sense of how many refills go unfilled or significantly late per week: [NUMBER OR "not sure yet"]

Please define:
1. **A first-nudge timing rule** — how many days past the refill-due date, with no new fill logged, before the first follow-up nudge goes out (so it never duplicates the PMS reminder)
2. **A second-nudge timing rule** — how many more days before a second, gentler nudge
3. **A "stop reminding" rule** — after how many missed nudges does the system stop and instead flag the pharmacist for a phone call, rather than continuing to text indefinitely
4. **A tone difference** between the first nudge (light, helpful) and the second (caring, non-judgmental, no guilt-tripping, offers help if cost or access is the barrier)
5. **A controlled-substance exclusion rule** — any item flagged CII–V in the export is dropped from the outreach list and surfaced to the pharmacist as an internal flag only
6. **A one-page reference table**: days'-supply category, first-nudge timing, second-nudge timing, stop-and-escalate threshold

This becomes the rule set for the drafting prompt next.
2

Confirm your BAA and set up the structural fill-data feed

Confirm your AI tool tier includes a signed Business Associate Agreement, and set up your pharmacy management system export to include only structural fields — never drug name or condition in the feed the AI reads.

Data you need

Contact your AI vendor to confirm and get written confirmation of a BAA on your plan before entering real fill data. Your export should include only: patient initials or internal Rx/patient ID, fill date, days' supply, refill-due date, refill status, and a controlled-substance flag (so those rows can be excluded from outreach). That is a minimum-necessary feed, not a de-identified one — initials, dates, and IDs are still PHI. Loop in your pharmacist-in-charge to review the feed design before go-live.

Agent Pack

Unlock the Pharmacy Agent Pack.

One payment unlocks all 3 blueprints in this pack — build steps, the complete system prompt, guardrails, a test checklist, and the maintenance routine — for $29.

See the whole pack

one-time, unlocks all 3 blueprints in this pack on this browser. Secure checkout via Stripe.