Crisphive

Built for pest control operators

Deterministic scheduling for pest control, embedded in the software your techs already use.

Crisphive sits behind your existing pest-control dispatch board, CRM, or AI assistant. When a tech calls in sick at 6:30 or a termite emergency lands mid-route, it re-cascades quarterly stops, food-safety audits and heat treatments across licensed, nearby techs in under 3 seconds — without breaking a contract 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

  • Pest-control service van with its side door open, sprayer tank and chemical cases inside, parked in a customer's driveway

    The route

    10–14 stops a day per van: quarterly residential, commercial contracts, callbacks. One absent driver strands all of them.

  • Flashlight beam on a bait station behind a commercial kitchen line, tablet with a service log resting on the stainless counter

    The contract window

    Food-safety and audit accounts have hard service windows written into the contract. Miss one and the fine is yours.

  • Gloved hands injecting termiticide into a drilled foundation slab, rod and sprayer hose on the concrete

    The licence

    Termite, fumigation and food-safety work can only go to techs holding the right state licence. 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 installation, maintenance and repair occupations, 3.2% of full-time workers miss part of any given week — and 1.7% of all 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 pest-control branch each no-show is a manual re-plan: the office phones around, licences get guessed, a restaurant's audit window slips, quarterly customers get bumped, and the homeowner 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 — Link zu diesem Abschnitt kopierenLink kopiert

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 ] }

Pest control, modelled properly — Link zu diesem Abschnitt kopierenLink kopiert

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

  • Drill holes along a concrete slab edge with a termiticide injection rod in place, bucket and hose beside it

    Termite / WDO treatment

    Trenching, rodding and bait systems. Long jobs that anchor a route and need a licensed applicator.

    Credential
    Structural / WDO licence
    Duration
    3–5 h
    Window
    Same week
  • Tamper-proof bait station being logged with a barcode scanner on a restaurant back-of-house floor

    Food-safety service

    Restaurants, grocers, processing plants. Documented visits inside the contract window, audit-ready logs.

    Credential
    Food Safety / AIB
    Duration
    60–90 min
    Window
    Hard window
  • Industrial heaters and fans staged in an emptied apartment bedroom with the mattress on its side for heat treatment

    Bed-bug heat treatment

    Equipment-heavy, full-day, tenant prep required. Cannot slide without re-booking the customer.

    Credential
    Fumigation / Thermal
    Duration
    6–8 h
    Window
    Fixed date
  • Copper mesh and sealant being pressed into a gap at the base of a commercial building wall

    Rodent exclusion

    Inspection, sealing and trapping for commercial and multi-family accounts. Often a two-visit chain.

    Credential
    Commercial
    Duration
    90 min
    Window
    48 h
  • Backpack mist blower treating a park perimeter at dawn, fine spray drifting through the trees

    Mosquito & vector control

    Seasonal municipal and HOA programs, weather-dependent, large territory.

    Credential
    Vector / Public health
    Duration
    2 h
    Window
    Weather-gated
  • Hand sprayer treating the foundation line along a front porch, service van parked in the driveway behind

    Quarterly residential

    The volume that fills the route. Flexible by a day, so the solver uses it as slack to protect everything above.

    Credential
    General pest
    Duration
    30–45 min
    Window
    ± 1 day

What happens in those 3 seconds — Link zu diesem Abschnitt kopierenLink kopiert

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, an emergency termite job — 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

  • Licences WDO/termite, fumigation, food safety, vector, general pest
  • SLA windows per contract, hard
  • Drive time live traffic matrix
  • Capacity hours, stops, breaks
  • Territories and customer preferences
Field technicians40
Stops per tech per day10
Average ticketUS$150
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
1.720
10 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$219K

1.720 jobs a year sit on an absent tech's route. At 85% same-day recovery, Crisphive re-sequences 1.462 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 — Link zu diesem Abschnitt kopierenLink kopiert

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