When to use this checklist
Use it when a resident asks to reserve a clubhouse, pool, gym, elevator, loading dock, parking area, package room, grill area, rooftop, community room, or another shared amenity, or when they ask about cancellations, guest counts, deposits, cleaning fees, access fobs, quiet hours, alcohol/food rules, or event exceptions.
- Separate approved amenity rules from guesses about availability, deposits, refunds, cleaning obligations, insurance, guest limits, parking, noise, or access rights.
- Capture the source record before an AI draft turns a resident preference, staff memory, old flyer, or calendar note into a resident-facing promise.
- Route accessibility/accommodation requests, safety issues, alcohol/event liability, fee disputes, damage deposits, security, and rule exceptions to manager/legal review.
- Create a neutral resident update with the next owner, next check time, approved channel, and STOP AUTOMATION guardrails.
Copy/paste amenity reservation triage card
Amenity reservation / rule question triage card
Property/community: [property name]
Resident/account: [name or account id]
Amenity involved: [clubhouse / pool / gym / elevator / loading dock / package room / parking / grill / rooftop / community room / other]
Request type: [new reservation / change / cancellation / rule question / access issue / deposit or fee question / exception request / complaint]
Requested date/time/window: [date/time/timezone]
Source record checked: [amenity calendar / lease addendum / community rules / fee schedule / manager note / maintenance schedule / resident report only / other]
Availability verified? [yes/no + source]
Deposit/fee/refund terms verified? [yes/no + source]
Guest count, parking, noise, cleaning, security, or access limits verified? [yes/no + source]
Safety, accessibility, accommodation, or legal-sensitive trigger? [yes/no + details]
Approved resident wording available? [yes/no]
Next owner: [leasing / resident services / property manager / maintenance / security / vendor / accounting]
Next update due: [date/time]
CRM/PMS label: [amenity-reservation / amenity-rules / access-review / fee-review / manager-exception / resident-update-needed]
STOP AUTOMATION if the message involves accommodation/accessibility, discrimination/fair-housing concern, safety, alcohol/event liability, security, deposit/refund/fee dispute, damage responsibility, legal notice, lease consequences, access rights, or an unverified amenity rule.
Resident-safe reply templates
1. Request received, calendar/source check pending
Hi [Name], thanks for your note about [amenity]. We are checking the approved amenity calendar and community rules so we do not guess about availability, fees, guest limits, access, or cleanup requirements. We will send the next verified update by [time/date] or sooner if the manager confirms the details.
2. Reservation details verified
Hi [Name], the current approved record shows [amenity] is [available/reserved/blocked] for [date/window]. The verified next step is [reservation form/payment/deposit/access pickup/manager approval]. Please review [approved rules link or attachment] before the reservation is confirmed.
3. Exception or sensitive request
Hi [Name], because your request involves [exception/sensitive item], we are routing it to [manager/team] for human review instead of sending an automated answer. We will follow up through [approved channel] after the relevant rule, record, or approval path is checked.
AI review prompt
You are helping a property-management team triage an amenity reservation or amenity-rule question. Use only the verified facts below. Do not invent amenity availability, community rules, fees, deposits, refunds, guest limits, access rights, parking, safety requirements, accommodation decisions, lease consequences, or manager approvals. If a required fact is missing or the issue is sensitive, output NEEDS MANAGER REVIEW.
Verified facts:
[property/community]
[resident message]
[amenity involved]
[source record checked]
[requested date/time]
[availability status]
[deposit/fee/refund terms]
[rule limits]
[safety/accessibility/legal-sensitive trigger]
[next owner]
[approved resident wording]
Create: (1) internal triage summary, (2) missing facts, (3) escalation bucket, (4) resident-safe draft under 120 words, and (5) CRM/PMS note.
Human-review stop rules
- STOP AUTOMATION before promising availability, waiving fees, refunding deposits, approving exceptions, granting access, changing quiet-hour/event rules, interpreting leases, or assigning damage responsibility.
- NEEDS MANAGER / LEGAL REVIEW if the message mentions fair housing, disability accommodation, discrimination, safety hazard, security incident, alcohol/event liability, injury, property damage, police, insurance, or repeated disputes.
- Do not paste private resident, guest, access-code, payment, fob, or security details into public AI tools.
- Keep resident updates tied to approved calendars, community rules, fee schedules, lease addenda, and manager records; include the next update owner/time when available.
This is a practical free resource from Horizon Flow. The paid Local Lead Rescue System expands the same approach into lead capture, response, qualification, follow-up, resident issue triage, and safe CRM handoff workflows.