Crisphive

Built for pharmacy courier operators

Deterministic scheduling for pharmacy couriers, embedded in the software your drivers already use.

Crisphive sits behind your existing dispatch board, pharmacy system, or AI assistant. When a driver calls in sick at 6:30 or a STAT oncology delivery lands mid-route, it re-cascades cold-chain runs, controlled-substance drops and long-term-care rounds across qualified, nearby drivers in under 3 seconds — without missing a dose window, and without anyone learning a new tool.

Try the sandbox
cascade re-schedule on a call-in
< 3 s
MCP tools for Claude & ChatGPT
43
new screens for dispatchers
0

Every job inside its window

The day Crisphive protects

  • Refrigerated pharmacy courier van backed up to a pharmacy loading door at dawn, insulated totes stacked on a hand truck

    The route

    40–80 drops a day per van across clinics, care homes and patients' doors. One absent driver is a day of missed doses.

  • Validated cold-chain cooler open on a van floor, gel packs and a temperature data logger showing a reading, sealed medication bags inside

    The cold chain

    Insulin, biologics and vaccines carry excursion limits. Every re-route must respect the time out of refrigeration.

  • Handheld signature device and a sealed tamper-evident pharmacy bag on a long-term-care nurses' station counter

    The chain of custody

    Controlled substances need a trained, background-checked driver and a signature. The solver treats that as a hard constraint, not a note.

The problem is statistical, not occasional

Every week, roughly 1 in 30 of your field crew won't show up as scheduled.

Across transportation and material-moving occupations, 3.4% of full-time workers miss part of any given week — and 1.8% of scheduled hours are simply lost. Illness and injury, not vacations, drive most of it.

3.2%
of U.S. full-time workers absent in any given week (2025), up from 3.1% in 2023
BLS, CPS Table 47
4+ days
lost per full-time employee per year — 1.7% of scheduled hours, before vacation and holidays
BLS, CPS Table 47
US$3,600
cost of unscheduled absence per hourly worker per year — about US$36K for a 10-tech crew
Circadian
US$150–300
direct disruption from a single field-tech no-show, before any missed-appointment revenue
U.S. field-ops stat sheet

Weekly absence by field segment

% of full-time workers who worked under 35 h in the reference week for illness, injury or personal reasons · all-worker benchmark 3.2%

  1. Installation, maintenance & repair3.2%
  2. Last-mile delivery & transport3.4%
  3. Facilities / grounds maintenance3.4%
  4. Production / plant3.4%
  5. Skilled trades / construction2.7%
  6. Construction industry overall2.3%

U.S. Bureau of Labor Statistics, Current Population Survey Table 47, 2025 annual averages (11-month average, excluding Oct 2025). Construction reads low partly because unpaid hourly absences go unrecorded.

Planning rule of thumb

1 absent tech per 30, every week

At a 2.7–3.4% weekly absence rate and 1.5–1.9% of hours lost, plan for about one absent technician per 30 in any week and 4–5 lost days per technician per year. The CDC puts absenteeism-linked productivity losses at US$225.8B a year — US$1,685 per employee.

In a pharmacy courier operation each no-show is a manual re-plan: dispatch phones around, cold-chain certs get guessed, a hospice med pass slips, controlled drops pile onto one driver, and the patient finds out last. That's the work Crisphive removes — inside the tools you already run.

Sources: BLS CPS Table 47 (2025 annual averages); CDC Foundation, "Worker Illness and Injury Costs U.S. Employers $225.8 Billion Annually"; Circadian, "Absenteeism: The Bottom-Line Killer"; Integrated Benefits Institute ($530B total illness-related lost productivity).

Three ways in — انسخ رابط هذا القسمتم نسخ الرابط

Pick the surface. The same deterministic solver answers behind all three.

Call the solver from your own backend.

Your dispatch system already owns jobs, techs and contracts. Send Crisphive the delta — "tech 04 is out" or "new urgent stop" — and get back a complete, SLA-valid plan to write wherever you keep schedules. Idempotent, deterministic, versioned.

  • Event in, plan out. One call returns reassignments, new start times and a plain-language reason per move.
  • Webhooks for drift. Traffic, overruns and no-shows trigger re-solves you can accept automatically or review.
  • Nothing to host. Constraints and territories live in your tenant; we never see customer data you don't send.

FitsExisting FSM platformsIn-house dispatch toolsVoice agents (Twilio, Vapi, Retell)

POST /v1/solvedeterministic
POST https://api.crisphive.com/v1/solve
{
  "schedule": "2026-10-06/portland-metro",
  "event": { "type": "tech.unavailable",
             "tech": "T-04", "from": "06:30" },
  "constraints": ["certifications",
                  "sla_windows", "drive_time",
                  "daily_capacity"]
}

200 OK  · solved_in: 2.41s · sla_breaches: 0
{ "moves": [
  { "job": "ACME-7781", "to": "T-07",
    "start": "11:30", "shift_min": 240,
    "why": "nearest certified tech
            with window slack" },
  … 3 more ] }

Pharmacy delivery, modelled properly — انسخ رابط هذا القسمتم نسخ الرابط

Every service type carries its own credential, duration and window. The solver knows the difference.

  • Sealed red STAT delivery bag on the passenger seat of a courier car, hospital pharmacy entrance blurred through the windshield

    STAT / same-day clinical

    Oncology, post-discharge and hospice meds. Highest priority, injected into live routes.

    Credential
    Clinical delivery trained
    Duration
    Direct run
    Window
    ≤ 2 h
  • Validated shipping cooler being loaded into a van with a digital temperature logger clipped to the lid, frost on the gel packs

    Cold-chain (2–8 °C)

    Insulin, biologics, vaccines. Excursion clock starts at pickup and bounds every move.

    Credential
    Cold-chain certified
    Duration
    Timed leg
    Window
    Excursion limit
  • Signature capture handheld on a care-home reception desk beside a locked medication tote with a numbered seal

    Controlled substances

    Schedule II–V. Chain-of-custody, signature, two-step verification on handoff.

    Credential
    CS-authorized driver
    Duration
    10–15 min stop
    Window
    Signature required
  • Stacked blue pharmacy totes on a cart in a long-term-care facility corridor, handrails and room doors receding behind

    Long-term-care rounds

    Bulk tote deliveries to facilities on a fixed daily cycle. Dense, predictable, the backbone of the route.

    Credential
    Facility badge
    Duration
    20–40 min
    Window
    Med-pass cut-off
  • White pharmacy bag with a stapled receipt on a residential front-door mat, doorbell and porch railing in soft focus

    Home patient delivery

    Residential drops with ID check and optional counselling callback. Flexible by hours, so the solver uses them as slack.

    Credential
    HIPAA trained
    Duration
    5–10 min
    Window
    ± 3 h
  • Sealed red sharps container and a returns bin being loaded into the back of a courier van

    Returns & sharps pickup

    Reverse logistics and compliance pickups bundled onto existing legs when capacity allows.

    Credential
    Hazmat awareness
    Duration
    10 min
    Window
    Weekly

What happens in those 3 seconds — انسخ رابط هذا القسمتم نسخ الرابط

Deterministic means the same inputs always give the same plan — auditable, explainable, no surprises at 6:30 AM.

  1. 010.0 s

    Event arrives

    A call-in, an overrun, a STAT oncology run — from your app, a webhook, a voice agent, or a sentence typed to Claude.

  2. 020.1 s

    Constraints load

    Certifications, SLA contract windows, live drive-time matrix, remaining daily capacity and territory rules for the affected day.

  3. 03< 3 s

    Deterministic cascade

    The engine re-sequences the whole connected day, not just the broken slot, and returns one reproducible plan with a reason per move — zero SLA breaches or it says so.

  4. 04you decide

    Preview, approve, write back

    Humans see every move before it lands. On approve, your system of record is updated and technicians and customers are notified.

Hard constraints the solver carries

  • Driver qualification cold-chain, controlled-substance, HIPAA
  • Dose windows med-pass cut-offs, STAT ≤ 2 h
  • Excursion limits time out of 2–8 °C
  • Capacity totes, cooler volume, hours
  • Chain of custody signature and ID rules
Drivers40
Drops per driver per day14
Average delivery feeUS$60
Jobs recovered same-day with cascade rescheduling85%

Your assumption, not a benchmark — depends on cert coverage and territory density.

Techs out in a typical week
1.3
3.2% weekly absence rate
Tech-days lost per year
172
4.3 days per tech, illness & personal only
Jobs on absent routes / yr
2,408
14 jobs × lost tech-days
Unscheduled-absence cost / yr
US$144K
Circadian: about US$3,600 per hourly worker per year

Revenue kept on the calendar per year

US$123K

2,408 jobs a year sit on an absent tech's route. At 85% same-day recovery, Crisphive re-sequences 2,047 of them onto certified colleagues instead of a callback queue — plus 129 dispatcher hours not spent phoning around.

Illustrative. Lost tech-days and weekly rates are U.S. benchmarks from the sources above; dispatcher time assumes 45 min of manual re-planning per absent tech-day; recovery rate and ticket size are your inputs. Excludes overtime, backfill and SLA penalties.

Shipping it — انسخ رابط هذا القسمتم نسخ الرابط

Runs in shadow mode next to your current planner until you trust it.

Crisphive reads your jobs, techs, certifications and SLA contracts through the connector you choose, proposes plans beside the ones your team makes by hand, and only writes back once you flip it live. Your system of record stays the system of record.

  1. 1

    Connect days

    Point a connector at your jobs, techs, certs and contracts. Read-only.

  2. 2

    Shadow mode weeks

    Crisphive proposes a plan for every real disruption beside the one your dispatchers make by hand. Compare SLA breaches, drive time and wrench time.

  3. 3

    Go live your call

    Flip write scope on for the surfaces you chose — API, embedded components, MCP, or all three.

More embedded use cases

The same solver, your vertical's constraints