HN Debrief

Kinney Drugs pulls back AI phone assistant after hundreds of customer complaints

  • AI
  • Healthcare
  • Customer Support
  • Business
  • Regulation

The article says Kinney Drugs pulled back its AI phone assistant after a flood of complaints, including missed prescription notifications and incorrect information. That hit a nerve because pharmacies are a brutal setting for automation. Callers skew older, drug names are hard to recognize, insurance rules are messy, and many calls happen only because the easy path already failed. In that environment, a system that sounds flexible but cannot reliably resolve exceptions feels worse than an old phone tree. People are not calling to chat. They are calling because something went wrong and they need a human who can fix it.

If you are deploying AI into support, keep it on tightly bounded workflows and make human escalation instant. In regulated or trust-sensitive businesses, a cost-saving bot that blocks edge cases will damage the brand faster than it saves labor.

Discussion mood

Strongly negative. Most comments treat AI phone agents as a cost-cutting barrier to human help, and in pharmacy that feels reckless because mistakes, delays, and dead-end escalation paths can affect medication access and health outcomes.

Key insights

  1. 01

    Cheap models break the business case

    The practical problem is not just "AI" in the abstract. Companies often deploy weak, low-cost models behind a polished voice layer, then discover they are worse than a basic deterministic workflow. Human call-center scripts have been refined into predictable escalation trees over years. Replacing that with a nondeterministic system means more brittle behavior, harder testing, and failure modes that are expensive to catch before customers do.

    When comparing AI support to human labor, compare it to the full existing system, including stable scripts and escalation rules, not to an idealized blank slate. If the model is too cheap to outperform a search box or phone tree on your real traffic, do not ship it as frontline support.

      Attribution:
    • dj_axl #1
    • PhilipRoman #1
    • asdff #1
  2. 02

    Drug names and accents wreck voice accuracy

    Automatic speech recognition is a deeper bottleneck here than a lot of product teams admit. Pharmacy calls are loaded with hard-to-pronounce brand names, inconsistent pronunciation, and regional accents. Even humans already stumble over names like Wegovy, Ixempra, Qvar, and Keflex. That makes a voice-first interface much more fragile than demos suggest, because the input layer is shaky before the language model even starts reasoning.

    If your workflow depends on correctly hearing specialized vocabulary, test the speech layer as aggressively as the model layer. In domains with messy pronunciation, text, keypad, or hybrid flows may be safer than pure voice.

      Attribution:
    • fn-mote #1
    • munk-a #1
    • thunderfork #1
  3. 03

    People call only after automation failed

    By the time many customers pick up the phone, they are already in an exception path that the app, website, or refill IVR could not handle. That means phone support is disproportionately filled with back orders, insurance conflicts, and other edge cases. Adding a conversational layer on top does not remove that complexity. It just exposes more of it to a system that is least suited to deal with it.

    Do not judge phone AI on average requests alone. Measure the distribution of calls that remain after self-service channels siphon off the easy work, because that is the workload your voice agent actually inherits.

      Attribution:
    • AndrewKemendo #1 #2
    • superb_dev #1
  4. 04

    Narrow automation is accepted

    A lot of the pushback disappears when the task is tightly scoped. Several comments were fine with automation for store hours, refill status, stock checks, or appointment prep by SMS. The line gets crossed when the bot is asked to handle refill exceptions, dosage questions, or insurance confusion. That is not hypocrisy. It is a recognition that low-stakes lookup tasks and healthcare judgment calls are different products.

    Scope support automation around tasks customers already treat as lookup or routing problems. Keep anything that looks like advice, exception handling, or policy negotiation behind a human.

      Attribution:
    • coffeefirst #1
    • fn-mote #1
    • SalaevAl #1
  5. 05

    The real failure is blocking escalation

    What enrages people is not occasional error. It is a system that refuses to recognize its limits and stands between the customer and the person empowered to help. Commenters described AI and IVR systems as obstacles that repeat website advice, lack authority to override rules, and turn every unusual situation into a maze. In that framing, the bot is not support. It is a filter designed to shed costly cases.

    Make escalation a first-class product feature with a clear trigger, not a hidden failure state. If the handoff is slow, adversarial, or unavailable, users will treat the entire AI layer as hostile no matter how good it is on easy cases.

      Attribution:
    • dkarl #1
    • cameldrv #1
    • Terr_ #1

Against the grain

  1. 01

    Pharmacies may need automation to survive

    The strongest defense came from a pharmacy AI operator who argued that many retail pharmacies are already running on terrible margins and cannot staff phones well enough to handle demand. In that view, the alternative is not warm human service. It is twenty-minute holds, chronic understaffing, and more closures. If AI can absorb routine transactional calls, even imperfectly, patients may get faster access than they do now.

    In low-margin sectors, judge automation against the actual baseline, which may already be failing customers badly. If you reject AI on principle, you still need a believable operating model for how the service gets staffed and paid for.

      Attribution:
    • jonathan-adly #1 #2 #3
  2. 02

    Older patients can succeed with well-scoped AI

    One builder working on SMS-based medical workflows said elderly patients engaged far better than expected when the system focused on appointment prep and logistics. They reported major reductions in no-shows because the tool handled diffuse real-world issues like anxiety, language barriers, and confusion about where to go. That suggests the problem is not simply that older users or healthcare workflows are incompatible with language models.

    Do not generalize from failed voice bots to every healthcare automation project. Text-based, bounded workflows with clear operational goals can work, especially when they remove friction instead of replacing judgment.

      Attribution:
    • zukzuk #1
  3. 03

    Bad examples may hide useful deployments

    A few comments warned that customer hatred of AI support may be skewed by visibility. People notice the disasters, while the successful interactions vanish into the background. There are reportedly voice agents in production that callers do not even realize are automated. If that is true, the public picture is biased toward the worst implementations because those are the ones that generate outrage and headlines.

    Look for completion rates, transfer rates, and repeat-contact data before drawing broad conclusions from anecdotes alone. The market signal may be less about whether AI can work and more about how often companies ship it before it is ready.

      Attribution:
    • vanuatu #1
    • josefritzishere #1

In plain english

AI
Artificial intelligence, software designed to perform tasks that usually require human judgment or language ability.
IVR
Interactive voice response, an automated phone system that lets callers navigate options by voice or keypad.
SMS
Short Message Service, standard text messaging over mobile phone networks.

Reference links

Pharmacy economics and PBMs

AI support failures and critiques

Call center and customer support context