---
title: "Nine of Ten Emails to the Order Desk Are Gloves and Gauze. The Tenth Is a Recall Question."
description: "How medical and dental supply distributors split routine reorders from recall, allocation and license questions in 2026, plus math on 1,900 messages a month."
canonical: https://callsphere.ai/blog/nine-of-ten-emails-to-the-order-desk-are-gloves-and-gauze-the-tenth-is
category: "Healthcare"
tags: ["medical supply distribution", "dental distributors", "order desk automation", "model routing", "prophet 21", "recall management"]
author: "CallSphere Team"
published: 2026-06-03T11:52:28.000Z
updated: 2026-07-25T23:27:30.303Z
---

# Nine of Ten Emails to the Order Desk Are Gloves and Gauze. The Tenth Is a Recall Question.

> How medical and dental supply distributors split routine reorders from recall, allocation and license questions in 2026, plus math on 1,900 messages a month.

Pull one ordinary Tuesday in March and count what actually landed on the order desk. A distributor doing $18 million a year in dental and medical consumables — three inside customer care reps, six territory managers, two equipment service techs — sees something close to this: 94 emails, 31 faxes that land in the shared mailbox as PDFs, about 140 EDI 850 purchase orders that drop straight into Epicor Prophet 21 untouched, and 61 phone calls. Of the 125 emails and faxes a person has to read, roughly 85 are a practice reordering something they have bought eleven times before: nitrile exam gloves in medium, ASTM Level 3 earloop masks, 4x4 12-ply sterile gauze, prophy angles, blue articulating paper, saliva ejectors.

Then there is the tenth one. A pediatric office asking whether their gauze lot falls inside the Class I recall notice that came through Friday. A dental office whose state prescription-device license expired in January, ordering an Rx-only item. A clinic wanting a substitution on an item the manufacturer just put on allocation. Those three eat two hours, and at least one ends up on your desk.

Both kinds cost the same to answer today, because both sit in one queue and both get the same person. That is the thing 2026 actually fixed.

## The queue does not know the difference, so the queue is the problem

Walk behind the order desk at 12:40 and you will see the workaround everyone pretends is fine. The senior customer care rep — nine years in, the one who knows the Fairview account always means the 100-count box, not the 50 — is keying a reorder for two cases of gauze. The recall question sits unopened for forty minutes because she is the only one who can answer it and she is typing item numbers.

The 2024 and 2025 attempts failed for a reason worth naming. Owners were told to put one assistant on the whole mailbox. Pick a cheap one and it was fine on the gauze and dangerous on the recall. Pick the expensive one and it was excellent on the recall while you paid premium rates to read "same as last time, thanks" nineteen hundred times a month. Most distributors tried it, looked at the bill or looked at one bad answer, and turned it off.

**Model routing means the assistant sends easy, repetitive work to a fast cheap engine and escalates only the genuinely difficult requests to an expensive one — and in a supply house, you are the person who defines which is which.** It became standard practice in 2026: Cisco built routing directly into the personal agent it is rolling out to roughly 90,000 employees, precisely to keep cost and capability in balance across a huge volume of ordinary requests.

## What routing looks like when the product is gloves

The routing rule in a supply house is not a technical setting. It is a list, and it reads like something your compliance officer would write, because that is who should write half of it. Routine here has a specific meaning: every line is an item this account has bought before, on an active contract, in stock, not prescription-only, not temperature-controlled, not on the recall board, and inside their credit limit. Miss one of those and it is not routine.

```mermaid
flowchart TD
  A["Email lands in the order desk mailbox"] --> B{"Every line a repeat item on an active contract?"}
  B -->|Yes| C["Fast model drafts the order in Prophet 21"]
  C --> D["Customer care rep glances and releases"]
  B -->|No| E{"Touches a recall, an allocation, or a license?"}
  E -->|Yes| F["Strong model builds a briefing packet"]
  F --> G["Compliance officer or owner decides"]
  E -->|No| H["Strong model drafts, rep answers the customer"]
```

Notice what the strong model does in that bottom branch. It is not placing an order. It reads the recall notice, pulls the affected lot range, checks Prophet 21 for which consignees received that lot, and drafts the notification letter with the business reply form attached. That is a two-hour job for a person, and it is the job you want the expensive engine on.

## Tuesday, 12:40 p.m., with the line drawn

Same lunch hour after the split. Forty-one reorder emails arrive in the practice lunch window — the only stretch of the day the office manager is not chairside. The fast engine reads all forty-one, matches each to the customer's item history and contract price, and writes forty-one draft orders in Prophet 21 in held status. It flags four: a quantity six times the usual, an account $9,400 past due, an item on manufacturer allocation, and a composite shade that does not exist in that manufacturer's line.

Your rep opens the held queue at 1:05. Thirty-seven she releases in eleven minutes total, because she is confirming, not typing. The four flagged ones she works properly — past-due to credit, allocation to the buyer, who decides whether to offer a substitute and at what price. Nobody has been protected from a decision; they have been protected from data entry.

The recall email that arrived at 12:07 went the other way the moment it landed, because "recall" plus a lot number in one message is on the escalate list. By 12:20 there is a packet on the compliance officer's screen: the notice, the affected lots, the fourteen accounts that received them, and a draft letter for each. She corrects two things and sends. Last quarter that took until Thursday.

## Who decides where the line sits — and when they revisit it

This is the question owners get wrong. They hand the routing list to whoever set up the software. Do not. It has three authors.

- **Your customer care manager** writes the commercial half: which accounts, item classes and order sizes are safe to draft automatically. She knows the Fairview account means the 100-count box.
- **Your compliance or regulatory person** writes the hard stops and holds veto power. Prescription-only, anything needing a current state license or DEA registration on file, anything with a lot or expiry consequence, anything cold chain, anything under an open recall — those escalate, always, no matter how routine the customer thinks the order is.
- **Your buyer** writes the supply half: any item on allocation or short-dated escalates, because a substitution is a judgment call with a margin consequence.
- **You sign it**, and it gets reviewed every Friday for two months, then monthly. The list will be wrong at first. It gets right by being read.

## The arithmetic on 1,900 messages a month

Illustrative assumptions: 1,900 emails and faxes a month needing a human read; 68% pure repeat reorders; a customer care rep at $34 an hour fully loaded; a repeat reorder taking 3.5 minutes to key today and 45 seconds to review when drafted for you.

| Line | Today | With routing |
| --- | --- | --- |
| Repeat reorders per month | 1,292 | 1,292 |
| Minutes each | 3.5 | 0.75 |
| Hours per month on reorders | 75.4 | 16.2 |
| Labor cost at $34/hr | $2,564 | $551 |
| Running cost, cheap engine on the routine traffic | — | about $40 |
| Running cost, strong engine on the 608 hard messages | — | about $60 |
| **Monthly** | **$2,564** | **$651** |

Roughly $1,900 a month, or about 59 rep-hours back. The honest description of the payoff is not headcount cut — it is headcount avoided in the fourth quarter, when Section 179 buying and the December equipment rush normally force a temp onto the order desk. Prove it by counting one thing for four weeks first: minutes from message received to order confirmed, split between repeat reorders and everything else.

## Where this still needs a human

Do not let anything draft an order against an account whose prescription-device license or DEA registration has lapsed. The temptation is to have the assistant check the license file and proceed. Have it check, then stop, and put it in front of a person. Shipping an Rx-only device to an unlicensed practice is not a customer service problem, it is a state board problem.

Substitutions stay human too: when a manufacturer puts sterile gauze on allocation and your buyer wants to offer an alternate, someone with a title owns that recommendation. And equipment-down calls do not belong in a mailbox at all. When a practice's sterilizer throws an error code at 7:50 a.m. and they cannot run their morning schedule, that goes to a service dispatcher, and the value you provide is a tech in a van, not a well-written email.

The Monday first step is small: export last month's order desk mailbox, sort it into repeat reorders and everything else, and count the two piles. You will have the beginning of your routing list by lunch.

## Frequently asked questions

### How is this different from the order-entry automation my ERP vendor pitched in 2023?

That older approach matched on rigid rules — change the email format, or write "the usual plus a box of the blue ones," and it broke and dumped everything back on a person. The 2026 version reads the message the way your rep does, and it knows when it is out of its depth and hands the message up instead of guessing. The escalation is the feature, not the automation.

### What stops the cheap engine from putting the wrong item number in Prophet 21?

Two things. It drafts only from that customer's own purchase history and active contract lines, so it is choosing among items they have actually bought, not the whole item master. And every draft sits in held status until a rep releases it. Skip the held-status step to save eleven minutes and you have built a worse system.

### Does the routing list change during an allocation?

Yes, and that is the point of the Friday review. When a manufacturer allocation hits an item class, that class moves to escalate the same day and moves back when supply normalizes. Same with any product family under an open recall. Your compliance officer should be able to edit it without asking permission.

### Do I have to tell customers their reorder was drafted this way?

A released order signed off by your rep is your order, and most practices notice nothing but speed. Be plain about anything the assistant answers directly in writing, and give your attorney fifteen minutes on disclosure — several state AI statutes are in effect, including Texas and California rules that started 1 January 2026.

The phone splits exactly the same way. Most inbound calls to a supply house are "where is my order," "send the usual," and "what is my price," and they land in the lunch window when the desk is thinnest. [CallSphere](https://callsphere.ai) builds voice and chat agents that answer those lines around the clock, take the reorder, and pass anything touching a recall, a license, or a down sterilizer straight to the person who should handle it.

---

Source: https://callsphere.ai/blog/nine-of-ten-emails-to-the-order-desk-are-gloves-and-gauze-the-tenth-is