One console for pharmacy customer care: about three minutes saved per contact in the pilot

• Pain
  Prescription-status questions required a separate technician conversation
• Sequence
  Console first for prescription status, deep-linked from the legacy tool
• Pilot
  10 to 40 to 100 representatives to general availability
• Capabilities
  Duplicate search, orders, medications, packets, chat, replacements
• Routing
  Clinical-ticket context routes the contact to the appropriate team

Product workflow, shown through the decisions and handoffs.

Sequence a platform migration around the worst customer moment, not the cleanest architecture diagram. Parity is a threshold you earn, and continuity of care is the constraint you never trade.

My reflection

State reporting automation

I also launched the customer-care console and personally led duplicate-account search, embedded chat, packet workflows and clinical-ticket routing.

Customer-care contacts often arrive with relevant history that the representative must reconstruct before helping. I envisioned assistance that brought useful context into view sooner and worked with customer-experience and contact-center partners to bring it into the product. Source-linked context mattered: a representative needed to inspect the basis for a suggestion, not take polished text on faith.

Around that core, I worked on self-service assistance, representative support and conversation review. Retrieval from approved knowledge can help with routine questions; suggested answers must remain distinguishable from actions; a human needs sufficient context when a conversation exceeds the assistant’s scope. Product evaluation included quality, latency, cost and correction effort. Clinical authority remained with qualified people.

Other work involved assistance with billing exceptions and prescription data entry. I separated proposing a correction from confirming its effect, and paired automation with quality evaluation and operator feedback. A higher automation rate without its error rate would have been an incomplete product claim.

A later account describes a voice handoff failure, transfer monitoring and a callback fallback. The operating lesson is to verify the handoff outcome, rather than rely only on component health.

Tools and methods: customer-care workflow design, product requirements, launch readiness and operator feedback. 11 Automation with visible boundaries

I launched the customer-care console and personally led duplicate-account search, embedded chat, packet workflows and clinical-ticket routing, alongside the requirements, design and launch coordination.

At Amazon Pharmacy, generalists handled about 83% of contacts with the legacy care tool, the contact-center platform and a chat channel to technicians. To answer why a prescription was in follow-up, a generalist messaged a technician while the customer waited three to four minutes on hold. Pharmacists and technicians juggled many separate tools. The console’s goal was to handle a much larger share of clinical contacts.

The decision

I prioritized a narrower prescription-status workflow first, opened from the existing care tool, before expanding the console. Launch sequencing protected continuity of care.

What shipped after the pilot

Capability	What it addressed	Effect
Duplicate account search with match confidence	13% of monthly contacts involved duplicate or partial profiles	The duplicate-search account reports less technician chat and about 2 minutes saved per affected contact; the affected contacts are a subset of overall volume.
Orders view and cancellation	Capabilities the legacy tool never had	Net-new for care
Medications entity	23% of contact volume	Full prescription-level detail in one view
Packet schedules, recovery and modifications	Packet contacts ran 18% longer for lack of visibility	First time care could act for packet customers since the acquisition
Chat in the console	30% of contacts had no console access	The chat-integration account reports about 60 seconds saved per affected chat contact
Clinical-ticket routing	Generalist-to-specialist transfers	The routing account reports about 1,000 avoided transfers per month and 21 minutes saved per affected contact

Results

The prescription-status pilot account reports about three minutes saved per affected contact across more than 6,000 monthly contacts. The roadmap called for making the console primary and retiring the legacy tool; that plan is separate from the pilot result.