AI prompts for pest control office coordinators

I work in pest control office coordination. Help me create one work order summary that I can review and edit before use.

Relevant context:
- Role: Pest Control Office Coordinator
- Work context: You schedule the recurring treatment routes, log what a technician found on a service visit, answer calls from customers who spotted something between visits, and renew annual contracts before they lapse.

Task:
Turn a garbled voicemail about a recurring equipment problem into a complete work order.

Source material:
Voicemail transcript, front desk mailbox, 7:42 a.m.: "Hey it's Dale from receiving -- the roller door on dock 3 is doing that grinding thing again, same as last month, somebody sprayed it down but it's back. Now it's sticking about halfway up so we've been propping it with a pallet, which I know is not great. We've got a delivery at eleven and if it drops on somebody that's a whole different problem. Whoever comes out needs the code for the loading yard gate, it changed last week. Can somebody get me a work order before that truck shows up?"

Return only the finished work:
1. work order summary
2. priority
3. safety flags

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in pest control office coordination. Help me create one short safety reminder with the hazard that I can review and edit before use.

Relevant context:
- Role: Pest Control Office Coordinator
- Work context: You schedule the recurring treatment routes, log what a technician found on a service visit, answer calls from customers who spotted something between visits, and renew annual contracts before they lapse.

Task:
Write one short safety reminder that names the hazard, the location, what to do, and who to tell.

Source material:
Text from Otis, night shift, sent 4:20 a.m.: "delivery ramp behind Building C is solid ice, a produce driver almost went down on it around 4, scared the hell out of me. salt truck's not coming till after 6. threw a cone out there but the whole ramp's glazed, cone's not gonna cut it. day shift starts loading in at 6:30 and I guarantee somebody eats it if nobody says anything. can you get something posted before then, and loop in Rosa since she runs receiving."

Return only the finished work:
1. short safety reminder with the hazard
2. location
3. who to notify

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in pest control office coordination. Help me create one plain-language status update that I can review and edit before use.

Relevant context:
- Role: Pest Control Office Coordinator
- Work context: You schedule the recurring treatment routes, log what a technician found on a service visit, answer calls from customers who spotted something between visits, and renew annual contracts before they lapse.

Task:
Turn a repair-delay heads-up into a plain-language status update kitchen staff can read without tracking you down.

Source material:
Marcus, 8:52am, #maintenance channel: "just got off the phone with the supplier -- the compressor relay for the walk-in cooler in the cafeteria kitchen, unit CW-3, is back-ordered until Thursday. rigged the backup condenser fan as a stopgap and it's holding temp fine, so the cooler's safe to load and use like normal in the meantime. Ace Refrigeration is coming Friday at 7am to swap the part once it lands -- Deb in the kitchen already knows to expect them. one thing: if anyone hears grinding or smells anything burning off that unit before Friday, they need to call it in to me at ext. 4412 right away, don't wait for the morning huddle. can someone turn this into something I can post for the kitchen staff so they're not asking me the same three questions all week?"

Return only the finished work:
plain-language status update

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in pest control office coordination. Help me create one troubleshooting checklist that I can review and edit before use.

Relevant context:
- Role: Pest Control Office Coordinator
- Work context: You schedule the recurring treatment routes, log what a technician found on a service visit, answer calls from customers who spotted something between visits, and renew annual contracts before they lapse.

Task:
Create a troubleshooting checklist for the exhaust fan breaker trips that stays within safe first-pass limits and tells the crew exactly when to stop and call someone in.

Source material:
Wade from days catches you by the breaker panel before he clocks out: "the exhaust fan over fry station 2 tripped breaker 14 again around 10:40 this morning, that's the third time this week. Kitchen staff just keep flipping it back on themselves so they can keep cooking, nobody's logging it. Panel door was hanging open when I got there too. I don't want anyone messing with that breaker again before someone who knows what they're looking at gets eyes on it. Can you put together something the crew can actually follow next time it trips instead of just flipping the switch?"

Return only the finished work:
troubleshooting checklist

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in pest control office coordination. Help me create one parts request summary that I can review and edit before use.

Relevant context:
- Role: Pest Control Office Coordinator
- Work context: You schedule the recurring treatment routes, log what a technician found on a service visit, answer calls from customers who spotted something between visits, and renew annual contracts before they lapse.

Task:
Draft a complete parts request summary from Danny's voicemail.

Source material:
Voicemail from Danny in Maintenance, left at 7:40 this morning: "Hey, it's Danny -- the door closer on the east dining entrance, door 4, is leaking hydraulic fluid again and now it's slamming closed way too fast, almost caught a guy's arm yesterday. I already got the yellow caution sign taped up by the frame. This is the second complaint today, first one came in around 6:15 from the breakfast crew, second one right before I called you. I pulled the cover off and the part number's rubbed off the housing, can't read it. Door's a good fifteen years old at least. Can you get a parts request going so I'm not standing here holding the door for people all day?"

Return only the finished work:
1. parts request summary
2. urgency rationale
3. missing info

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in pest control office coordination. Help me create one reusable inspection checklist organized by equipment category that I can review and edit before use.

Relevant context:
- Role: Pest Control Office Coordinator
- Work context: You schedule the recurring treatment routes, log what a technician found on a service visit, answer calls from customers who spotted something between visits, and renew annual contracts before they lapse.

Task:
Build a reusable preventive maintenance plan template and fill in a sample September schedule using it.

Source material:
Email from Terrence, subject "PM plan -- still need this": "Following up on that PM plan you said you'd put together. After the water heater on the loading dock side went out on us in July with zero warning, corporate wants an actual preventive schedule, not just us reacting. Cover the big stuff: HVAC filters in both AHUs, the emergency lighting on floors 2 through 4, the door hardware on the loading dock roll-up, walk-in cooler temps in the kitchen, the two water heaters, and the parking lot and stairwell lighting. I need a template I can reuse every month, plus lay out what an actual September looks like so I can hand it to the night crew. Have it to me by the 28th so I can get it in front of Denise before the budget meeting."

Return only the finished work:
1. reusable inspection checklist organized by equipment category
2. sample September schedule with a specific day or frequency for each item
3. short rationale for why each item's frequency was chosen

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in pest control office coordination. Help me create one shift handoff message ready to send to the incoming tech that I can review and edit before use.

Relevant context:
- Role: Pest Control Office Coordinator
- Work context: You schedule the recurring treatment routes, log what a technician found on a service visit, answer calls from customers who spotted something between visits, and renew annual contracts before they lapse.

Task:
Turn a shift's worth of scattered maintenance notes into one shift handoff message the incoming tech can act on without tracking you down.

Source material:
"Handing off to whoever's on tonight -- room 214 had a ceiling tile drip, we mopped it up but never found the source, so keep an eye on it. Room 118's thermostat is still reading five degrees warm, ticket #4471 is already in, Frontline HVAC says Thursday morning. Fixed the wet floor by the east stairwell -- cones are still up till it fully dries, pull those around 10. The floor buffer in the equipment closet needs a new drive belt, it's on order, ETA Wednesday, don't run it before then. And the compactor room door closer is busted -- I've been propping it with a trash can all shift so it doesn't swing shut on someone. Mateo, that one can't wait till Wednesday too."

Return only the finished work:
1. shift handoff message ready to send to the incoming tech
2. open-item list with ticket numbers
3. safety flags that need attention before the next shift

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in pest control office coordination. Help me create one repaired work-order handoff prompt that I can review and edit before use.

Relevant context:
- Role: Pest Control Office Coordinator
- Work context: You schedule the recurring treatment routes, log what a technician found on a service visit, answer calls from customers who spotted something between visits, and renew annual contracts before they lapse.

Task:
Inspect the weak work-order handoff prompt provided. Identify what is missing, use AI to repair that prompt, then review and edit the AI-repaired prompt. You are not creating a brand-new prompt from scratch. You are repairing the weak prompt provided. The repaired prompt must include role, workplace context, task, boundaries, output format, completion criteria, review rules, and a "STOP FOR NOW" escape phrase (a line that tells the AI when to stop and summarize instead of continuing).

Source material:
the boiler in the mechanical room short-cycled again this morning, same as last Tuesday, just tell me what's wrong and put together whatever the tech needs to fix it

Return only the finished work:
repaired work-order handoff prompt

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in pest control office coordination. Help me create one reusable work-order triage prompt that I can review and edit before use.

Relevant context:
- Role: Pest Control Office Coordinator
- Work context: You schedule the recurring treatment routes, log what a technician found on a service visit, answer calls from customers who spotted something between visits, and renew annual contracts before they lapse.

Task:
Create a reusable work-order triage prompt that turns vague repair notes into complete, actionable entries without diagnosing beyond available facts.

Source material:
"Grabbed the queue before shift change -- WO 4417 just says 'AC not working, 2nd floor,' WO 4422 says 'noise from unit again,' and 4425 is 'leak by breakroom, maybe faucet?' None of these have a location past the floor number or say if anyone's already looked at them. Priya's covering nights and needs to know what's actually urgent before she walks in. Can you turn these into something she can act on without calling me at 11pm?"

Return only the finished work:
reusable work-order triage prompt

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in pest control office coordination. Help me create a set of risk scoring dimensions that I can review and edit before use.

Relevant context:
- Role: Pest Control Office Coordinator
- Work context: You schedule the recurring treatment routes, log what a technician found on a service visit, answer calls from customers who spotted something between visits, and renew annual contracts before they lapse.

Task:
Turn this work-order backlog into a risk-based rubric the night shift can apply on their own, without paging you to referee every ticket.

Source material:
Text from Curtis, evening shift lead, sent at 6:40pm: "Hey -- worklist's a mess again and I'm off in twenty. WO-4519 is a flickering breaker panel light near the loading dock. WO-4488 is the break room ice machine, still not cooling, third day now. WO-4502 just came in -- a guest called about a hot handrail on the 3B stairwell. And WO-4467's been sitting since Tuesday, ceiling tile down in the hallway outside 142, not dangerous but it looks bad every time someone walks by. Vendor's booked for the freight elevator Thursday morning and I honestly don't know if that jumps ahead of the handrail or not. Naomi's covering nights this week and she keeps texting me asking what goes first -- I need something she can just look at and decide herself."

Return only the finished work:
1. risk scoring dimensions
2. numeric ranking scale
3. worked examples scoring two of the open work orders above

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in pest control office coordination. Help me create one safer revised work-order handoff draft that I can review and edit before use.

Relevant context:
- Role: Pest Control Office Coordinator
- Work context: You schedule the recurring treatment routes, log what a technician found on a service visit, answer calls from customers who spotted something between visits, and renew annual contracts before they lapse.

Task:
Review an AI-generated work-order handoff draft for accuracy, missing context, unsafe assumptions, unsupported promises, and human review needs. Then produce a safer revised version. As a Lead deliverable, also write a short review standard your team can reuse: what to always check, what to never accept, and who signs off.

Source material:
Work order 4552 is closed out. Diagnosed the rooftop unit RTU-3 as a failed compressor, swapped it out this morning, and suite 220 is back to normal temperature -- the tenant should notice a difference within the hour. Since the compressor was the only issue, you can tell tenant relations this fully resolves both the warm-air complaint and the intermittent shutdown from two weeks ago, so that ticket can close too. System's running fine, safe to sign off without a follow-up visit.

Return only the finished work:
safer revised work-order handoff draft

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in pest control office coordination. Help me create one work-order handoff escalation branch plan that I can review and edit before use.

Relevant context:
- Role: Pest Control Office Coordinator
- Work context: You schedule the recurring treatment routes, log what a technician found on a service visit, answer calls from customers who spotted something between visits, and renew annual contracts before they lapse.

Task:
Work through a changing work-order handoff scenario. Create a branch plan for what to do if the facts change, what to ask next, what to draft, and when to escalate. As a Lead deliverable, add a short team standard: the rule others should follow, who owns review, and one signal that tells you it is working.

Source material:
Room 412's bathroom ceiling has been dripping on and off for three weeks. Ramirez patched it two Fridays ago and it held for four days before starting again. Now there's a brown ring spreading across the ceiling tile, and the vendor, Delgado Plumbing, wants photos plus access instructions before they'll lock in a Thursday morning slot.
Branch 1: The tenant in 412 says the drip now smells faintly chemical, not just like water, and it's tracking toward the light fixture -- you can't yet confirm whether this is a plumbing leak or something electrical.
Branch 2: Delgado Plumbing calls back and says they need building access instructions, a working phone number for the site contact, and clear photos of the ceiling stain before they'll confirm the Thursday 7am slot.

Return only the finished work:
work-order handoff escalation branch plan

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.