When to use it
- A resident reports an after-hours leak, lock, no-heat/no-cooling, electrical, pest, appliance, entry, noise, parking, or access issue.
- The on-call team needs to acknowledge the message without promising diagnosis, repair time, fee waiver, entry rights, or legal/habitability conclusions.
- The property manager needs a handoff record for the next business day: who replied, what was verified, what is still open, and what needs owner/vendor review.
STOP AUTOMATION: do not let AI or a front-desk script promise emergency status, vendor arrival, reimbursement, lease/legal interpretation, habitability findings, access rights, fees, or repair completion. Route those items to the property manager, owner, approved vendor, or legal/process reviewer.
Copy/paste on-call escalation log
| Field | What to capture | Example |
|---|
| Resident / unit | Name, property, unit, preferred official contact channel. | Resident: [name], Unit [#], Portal/SMS allowed: [yes/no] |
| Issue type | Leak, no heat, lockout, appliance, pest, noise, parking, access, safety, other. | Water dripping from ceiling under upstairs bath. |
| Source evidence | Photos, video, portal thread, prior work order, vendor note, call recording, access log. | 2 resident photos + prior WO #1832. |
| Resident-safe acknowledgement | Only confirm receipt and next verified process step. | We received this and are routing it to the on-call process now. |
| Escalation lane | Emergency review, vendor dispatch, manager review, owner approval, legal/lease review, next-business-day queue. | Vendor dispatch review + manager copied. |
| Promises blocked | What must not be promised until confirmed. | No arrival time, no repair scope, no fee or reimbursement promise. |
| Owner/vendor handoff | Who owns the next step, due time, and source records attached. | On-call vendor to call resident; manager reviews by 9 AM. |
| CRM label | Tracking label/status for the open item. | after-hours / escalation-open / manager-review |
Resident-safe acknowledgement snippets
We received your message about [issue] at [time]. We are routing it through the on-call maintenance process and will update you through [official channel] when the next step is confirmed. Please do not use this message for life-threatening emergencies; contact emergency services if anyone is in immediate danger.
Thanks for the photos. We are attaching them to the maintenance record so the property manager/vendor can review the issue. We do not want to promise a repair time or diagnosis until the correct reviewer confirms the next step.
We are logging this as [issue category] and assigning it to [team/person] for review. If you have new photos, access notes, or safety details, please add them in [official channel] so the record stays complete.
Safe AI handoff prompt
Paste only verified facts into the prompt. Do not include private details that are not needed for the work order.
Create an on-call maintenance escalation summary using only the verified notes below.
Return:
1. Issue category and resident-safe acknowledgement draft.
2. Source evidence already attached.
3. Missing information to request, if any.
4. Escalation lane and recommended owner/vendor handoff.
5. Promises that must be blocked until manager/vendor/owner review.
6. CRM label and next check time.
Do not invent diagnosis, emergency status, fees, lease/legal interpretation, vendor ETA, repair completion, reimbursement, or habitability conclusions.
Verified notes:
[PASTE NOTES]
Human-review rule: a property manager or approved on-call lead reviews the summary before any resident-facing message includes access, vendor, fee, schedule, safety, lease, reimbursement, or repair-scope language.
Product connection
This is a practical free resource from Horizon Flow. The paid Local Lead Rescue System expands the same response discipline into missed calls, resident/service inquiries, follow-up scripts, CRM labels, handoff rules, and human-review guardrails for local-service and property-management teams.