How to get a useful answer
Two habits do most of the work. First, give it the role and the audience — "you are the office manager at a commercial HVAC contractor, write this for a property manager who is not technical" — because the same facts read very differently for a tenant, a controller, and a tech. Second, keep the input to what you would be comfortable emailing a stranger: no customer names, service addresses, account numbers, or pricing. Paste the shape of the problem, not the customer's file.
Planning the week
1. "Here is my open work list for the week, grouped by customer and site. Propose a plan that keeps the agreement customers' committed visits on schedule and batches work in the same area. Flag anything that will not fit."
2. "Turn these recurring maintenance obligations into a weekly checklist with the customer, the site, the frequency, and anything due in the next fourteen days."
3. "I have three techs off and two emergency calls on the board. List the trade-offs I should weigh before I move anything, and what I should tell the affected customers."
Talking to customers
4. "Rewrite this update in plain language for a property manager: shorter sentences, no jargon, say what we found, what we did, and what happens next."
5. "Draft a service agreement renewal note for a customer whose rooftop unit is twelve years old and has had four repairs this year. Be factual, not pushy, and give one clear next step."
6. "Turn this internal note into a version I can send to a tenant who is unhappy about the timing. Acknowledge the inconvenience, explain the constraint, and give them a specific window."
Documenting the work
7. "Turn these three tech notes into a single work-order summary a customer can read, and a separate internal version with the technical detail kept intact."
8. "Take this scribbled service note and produce a clean record: what was found, what was tested, what was replaced, and what should be watched on the next visit."
9. "Tidy this checklist so each step is one action, and mark which steps need a reading or a photo to count as done."
Solving a problem
10. "Walk me through a systematic diagnostic sequence for a rooftop unit that runs but does not cool, from the simplest checks to the least likely, and note what to record at each step."
11. "I suspect the same failure across several units at one site. List the common causes worth checking before we treat them as separate repairs."
Note the limit here: a general-purpose assistant is a good thinking partner for a sequence, but it does not know the unit, the readings, or the history. Treat its answer as a checklist to work through, never as a diagnosis.
Reporting
12. "Summarise these numbers into a short paragraph a service manager can read in one sitting: on-time arrival, first-time fix, callbacks, and utilisation, with the direction each moved and the one thing to look at next."
These twelve cover the ground the office asks for most often. The full prompt book — forty prompts across the same five jobs, with the wording for each one and the rule for what never goes into a prompt — is in preparation.