← Back to library

Pick the nearest eligible tech for a recall or callback

Tyler Griffin (@TylerGriffin) wrote that an assistant worked out which technician was near enough to take an installation recall and helped his office team book it. The article gives no eligibility or travel rules, so we wrote a procedure that filters on skills, certifications, area and availability, ranks by drive time and leaves booking to a person.

  • OutcomeFrom a recall or callback record and a roster that includes skills, certifications, service areas, availability and drive-time estimates, get one recommended technician and one backup, with ineligible people excluded and reasons given, ranked by drive time rather than straight-line distance, plus a booking draft for the office to confirm. Nothing is booked and no one is contacted until a dispatch lead approves it.
  • SetupUnder an hour
  • LevelIntermediate
  • CreditTyler Griffin (@TylerGriffin)
View original
Works with
Grok BotClaudeChatGPTClaude CoworkCustom agent

Published Nov 16, 2026Updated Nov 16, 2026AI dry run on sample input: passed Nov 16, 2026Source verified Nov 16, 2026

When should you use it?

  • A recall or callback needs a technician who can legally and practically do the work, not merely the closest pin on a map
  • Your office already keeps a roster with skills, areas and some form of travel estimate
  • You want a recommendation and a booking draft, with the office still confirming the visit

Not for: Letting an assistant book the visit or message the customer on its own; Jobs with no usable address or coordinates when you also have no way to estimate travel; Repair or diagnostic instructions; this workflow only recommends who might go; Assuming live GPS or a dispatch-board API; last-known location and a travel estimate you already use are enough to start

What do you need, and what do you get?

You need

  • The recall or callback: job id, address or coordinates, required skills and certifications, urgency, and any requested window
  • A technician roster with skills, certifications, service areas, availability, overlapping jobs, and current or next-free time
  • Drive-time estimates from each candidate's current or next location to the job, not only straight-line miles
  • The name of the dispatch lead who must confirm the booking

You get

  • A short list of eligible technicians, with exclusions and the reason for each exclusion
  • One recommendation and one backup, ranked by drive time, with the reason they beat the next option
  • An escalation banner when urgency is an emergency, including when the location is missing
  • A booking draft marked not booked; no customer or technician message is sent

How does it work, step by step?

  1. Flag the jobGive the assistant the recall or callback, the required skills and certifications, the urgency and the site address.
  2. Attach the roster and travel timesInclude who is qualified, who is on shift, who already has overlapping work, and estimated drive minutes to the site.
  3. Read eligibility before proximityCheck the exclusion list first. A nearby person without the right certification should not appear as the pick.
  4. Confirm the rankingMake sure the recommendation used drive time. If only straight-line miles were available, the assistant should have asked for travel estimates instead of picking a winner.
  5. Office books itThe dispatch lead confirms with the technician and the customer and books the visit in your system. The assistant does not send those messages or move other appointments.

The prompt

Our own prompt, inspired by Tyler Griffin (@TylerGriffin) and written to work in Grok Bot, Claude, ChatGPT and others. Values in lime are placeholders.

Prompt0 variables
You recommend who could run a recall or callback. You do not book the visit, contact the customer, or move other appointments.

Inputs:
- JOB: id, address or coordinates, required skills and certifications, urgency (routine, same-day, or emergency), original install notes if any, requested time window
- TECHS: for each person: id, name, skills, certifications, service areas, shift availability, current or next-free time, and current or last-known location if known
- TRAVEL: a drive-time matrix or a list of estimated drive minutes between each technician's current or next location and the job. If only straight-line distance is available, say so and do not treat it as drive time.
- APPROVER: the dispatch lead who must confirm

Eligibility (all must pass):
- Has every required skill and certification
- Job location is inside a listed service area, or service areas is listed as "all"
- Has open time that can cover the estimated on-site window plus drive time
- Not already assigned to an overlapping job
Exclude anyone who fails a check, and state the reason. Do not recommend an ineligible person because they are nearby.

Ranking:
- Rank only eligible technicians.
- Rank by estimated drive time, shortest first. Never rank by straight-line distance when drive times are present.
- If drive times are missing for everyone, do not pick a winner. Ask for travel estimates.
- If the job has no usable location, do not recommend a nearest technician. Ask for the address or coordinates and, if urgency is emergency, escalate immediately.
- For emergency urgency (no heat in freezing weather, suspected gas leak, carbon monoxide alarm, overflow causing damage): put an ESCALATE TO {APPROVER} banner first, still list eligible options if you can, and do not delay the report to hunt for a perfect match.

Output:
- Decision needed at the top, including any escalation.
- One recommended technician and one backup, each with eligibility notes, drive minutes, arrival estimate, and why they beat the next option.
- A booking draft for the office to confirm with the technician and the customer, marked DRAFT — NOT BOOKED.
- If no eligible technician exists, say so and list the nearest exclusions and what would make someone eligible.

Hard limits:
- Do not message the customer or the technician.
- Do not change the schedule.
- Do not give repair instructions.
- If asked to book now or notify the customer, refuse until {APPROVER} confirms.

Inspired by Tyler Griffin (@TylerGriffin): X Article: how an HVAC and plumbing owner actually uses an AI assistant. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Ranking by miles as the crow flies when a river, traffic or a highway makes a farther person faster to reach.
  • Leaving last-known location hours out of date. A travel estimate is only as good as the starting point you give.
  • Skipping the emergency escalation because a good candidate is already on the list. The banner still belongs at the top.
  • Letting the assistant shuffle other customers' appointments to make a slot.

Our take

The useful idea in Griffin's account is not 'pick whoever is closest.' It is 'narrow the list to people who can actually do the work, then help the office finish the booking.' We made that concrete. Skills, certifications, service area and availability are hard filters. Drive time, not straight-line distance, decides the order among the people who remain. A missing address or missing travel estimates should stop a nearest-person pick rather than produce a guess. Emergencies escalate first. None of those rules appeared as a reusable prompt in the article, and we have not run this against a live dispatch board. It will work when the roster and travel estimates you paste are trustworthy; it will not make a bad location feed safe. In our rule-engine dry run on synthetic fixtures, a farther-in-miles but shorter-drive technician was recommended, ineligible people were excluded, missing location and missing drive times blocked a pick, emergencies escalated, and booking stayed a draft.

Where the time goes back: Choosing who can run a recall usually means checking skills, area, the board and travel, then sending several messages. The assistant does the filter and the ranking in one pass and hands the office a short recommendation to confirm, instead of starting from a blank board.

FAQ

What if two eligible people have the same drive time?
The prompt asks for a recommendation and a backup with reasons. If drive times tie, the office should pick using your own tie-break, such as who finishes a nearby job sooner.
What counts as an emergency here?
Cases such as no heat in freezing weather, a suspected gas leak, a carbon monoxide alarm, or water causing damage. Those escalate immediately; the assistant still may list eligible options, but it should not delay the report.
Will this book the visit in our field-service software?
No. It prepares a draft for your dispatch lead. We did not assume API access and we did not test a live booking.

Source and credit

Inspired by Tyler Griffin (@TylerGriffin). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
X Article: how an HVAC and plumbing owner actually uses an AI assistant
Creator
Tyler Griffin (@TylerGriffin)
Published on
X
Original date
Nov 14, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Grok Bot
AI dry run
Nov 16, 2026: passed. Dry-run tested by our AI test agent on sample input. Eligibility before proximity, drive time over miles, booking left to a person.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Nov 16, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Set your agent's autonomy from your last ten approvals

Have your agent review the last ten times it handled a job you approve, sort what you accepted as written, edited or turned down, recommend one of four delegation levels (find out, draft, send after approval, or act within a rule), write the exact standing instruction, and replay it against those same cases before anything changes.

Credit: Michael Fenech (@Michael_Fenech_)

Minutes
Operations & AdminWorkflow✓ AI dry run

Log every agent action as ok, failed or unknown

Give each write an agent makes one structured log line with its attempt ID, request key, an outcome of ok, failed or unknown, and what the agent did next, then keep one saved query for the combination that should never happen, an unknown outcome the agent confirmed to the customer, so a repeat of the incident shows up in minutes.

Credit: ccch713

Under an hour
Operations & AdminWorkflow✓ AI dry run

Pin your agent's write path with one contract test

Build a single fast test workflow that sends the same request key to your agent's booking or order write twice against a stand-in backend, then confirms from an append-only log that exactly one write happened, that the repeat ends as a deliberate skip, and that a forced timeout still lands as unknown and reaches a person, so refactors cannot quietly bring back duplicate writes.

Credit: ccch713

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Set To, Cc and Bcc rules for your assistant's own mailbox

Give an AI assistant its own address and a written rule for each way it can appear on a message: when it is the direct recipient it prepares an unsent draft for you, when it is copied it may give a short reply as itself with no promises, and when it is blind copied it only records the message, with dates going to the calendar and dateless requests to the task list.

Credit: u/carlosrudriguez

Under an hour
Operations & AdminRoutine✓ AI dry run

Tidy your agent team's memory and keep a decisions log

Have your assistant review everything it has saved about you subject by subject, propose which outdated, repeated or conflicting entries to merge or remove, move standing decisions into a dated decisions page, and run a weekly tidy-up that changes nothing until you approve it.

Credit: Michael Fenech (@Michael_Fenech_)

Minutes