Best fit: property managers, leasing teams, maintenance coordinators, handyman services, HVAC/plumbing/electrical vendors, and small operators that receive maintenance requests by portal, email, text, voicemail, or web form.
Before using these templates
- Separate emergency/safety requests from routine maintenance before sending any automated reply.
- Confirm property address, unit, contact method, access permission, pets/parking notes, and photos before dispatch.
- Do not promise arrival windows, repairs, pricing, warranty coverage, or landlord approval until a human confirms.
- For habitability, water, electrical, gas, lockout, or safety issues, follow the company’s approved emergency policy instead of relying on AI.
1. Fast maintenance request acknowledgment
Hi [First Name], thanks for sending the maintenance request for [property/unit]. We received it and are reviewing the details now. To route it correctly, could you confirm [missing detail: access permission / best phone / photos / urgency]?2. Access and scheduling question
Thanks, [First Name]. Before we schedule the next step, can you confirm whether maintenance/vendor access is allowed during [window]? Please also note any pets, alarm codes, gate instructions, parking limits, or areas we should avoid.3. Photo/details request for unclear maintenance issues
To help the team avoid guessing, could you send 2–4 clear photos or a short description of what changed, when it started, and whether the issue is getting worse? We will add that to the work note before routing it.4. Vendor handoff update
Update on [request]: we have routed this to [vendor/team] for review. The current next step is [inspection / scheduling / quote review / parts check]. We will share another update by [time/date] or sooner if the status changes.5. Tenant/resident close-the-loop note
Hi [First Name], this request is marked [completed / waiting on approval / waiting on parts / not approved yet]. If anything still looks unresolved, reply with a photo or note before [date] so the team can review it.6. Not-enough-information closeout
We have not received the missing details needed to move this request forward: [details]. We are pausing the request for now so the team does not dispatch with incomplete information. Reply with those details when you are ready and we can reopen/review it.Simple CRM / work-order labels
- maintenance-new — request received; first review needed.
- needs-access-info — waiting on access, pets, parking, or entry notes.
- needs-photos-details — unclear issue before routing or quote review.
- vendor-routed — sent to vendor/team; next update date assigned.
- waiting-approval-parts — not ready for scheduling yet.
- closed-confirmed — closeout note sent and no further action pending.
AI prompt to draft a safe maintenance update
You are helping a property manager or local service team draft a maintenance-request update.
Confirmed facts only:
- Resident/contact: [name]
- Property/unit: [property/unit]
- Request type: [issue]
- Urgency bucket: [emergency/safety, same-day, routine, unclear]
- Known access notes: [notes]
- Current status: [new / needs details / vendor routed / waiting approval / waiting parts / completed]
- Next human owner: [person/team]
Draft one SMS under 450 characters and one email under 140 words.
Rules:
- Do not invent diagnoses, arrival windows, repair promises, warranty/payment decisions, legal language, or emergency instructions.
- If safety/emergency risk is possible, tell the human reviewer to use the approved emergency policy before sending.
- Ask for only the missing detail needed for the next step.
- Include a human review checklist before the final message.Human review checklist
- Does the message use only confirmed facts from the request/work order?
- Does it avoid unauthorized promises about arrival, repair, approval, price, or legal obligations?
- Does it give the resident, owner, or vendor exactly one clear next action?
- Does a safety/emergency issue need manual handling before any automated reply?
For broader local-service lead and request routing, start with the free AI lead response quickstart and the Local Service Lead Response Resource Library. The paid Local Lead Rescue System expands this into scripts, qualification questions, stale follow-up, and workflow templates for service operators.