Use this before any AI-assisted entry or lock-change reply
STOP AUTOMATION: do not send access instructions, identify a responsible person, promise a lock change, confirm camera footage, discuss police/legal conclusions, waive fees, blame residents, approve guest access, or summarize a security incident until a manager has verified the lease/occupancy record, authorized-contact list, lock/key/fob logs, access-control history, incident report, resident communication channel, property policy, police/risk/legal routing, and emergency context.
- Escalate active danger, domestic violence, stalking/harassment, child/elderly risk, threats, break-in evidence, law-enforcement involvement, or damaged exterior locks to immediate human review.
- Do not disclose private access logs, camera footage, codes, lockbox details, police-report details, or another resident's information in an automated reply.
- Do not promise lock-change timing, locksmith cost coverage, reimbursement, entry permissions, legal outcomes, or security-camera findings without verified source records and manager approval.
Copy/paste unauthorized entry source card
- Reporter and unit: resident name, unit/building, channel, callback number on file, relationship to leaseholder, authorized-contact status, and any missing identity facts.
- Incident type: suspected unauthorized entry, lock tampering, missing key/fob, access-code concern, guest/roommate dispute, maintenance-entry question, police report, break-in, harassment/stalking concern, or requested lock change.
- Evidence/source fields: date/time noticed, entry point, photos, damaged lock, camera/access-log request, key/fob serial if available, prior work orders, vendor/maintenance activity, police report number if provided, and exact resident wording.
- Policy and routing sources: lease/house rules, key/fob/access policy, lock-change policy, fee schedule, security-camera/privacy policy, police/risk/legal routing, vendor/locksmith procedure, and official communication channel.
- Stop-rule notes: immediate safety risk, suspected crime, domestic conflict, harassment, unauthorized occupant/guest dispute, request for private footage/logs, request to accuse another person, fee/reimbursement demand, or pressure to bypass identity/security checks.
- Safe owner and CRM label: property manager, security/concierge, on-call maintenance, locksmith/vendor, risk/legal, law enforcement, or resident-services lead; labels:
unauthorized_entry_report,lock_change_review,access_log_privacy_review,security_incident_human_review, orstop_automation_access_sensitive.
Resident-safe snippets
Initial acknowledgement
We received your report about possible unauthorized entry or a lock/access concern for [unit/building]. For resident safety and privacy, we are routing this for human review before confirming access records, lock-change options, fees, camera/log details, or next steps.
Access-log or camera request
We cannot share private access logs, camera footage, or another person's information through this channel. The property team will review the approved privacy/security process and let you know what can be confirmed or escalated.
Safety concern or suspected crime
If there is immediate danger, evidence of a break-in, threats, or a safety risk, please use emergency services or the property's emergency process now. We are escalating the report and will avoid guessing about responsibility, footage, lock-change timing, fees, or legal outcomes until source records are checked.
AI audit prompt
Review this draft resident update about suspected unauthorized entry, lock tampering, key/fob misuse, access-code concern, police report, camera footage, lock change, fee, or security incident. Flag invented claims about who entered, access-log findings, camera evidence, legal liability, police status, lock-change timing, reimbursement, fee waivers, emergency status, or resident blame. Rewrite it as a source-backed acknowledgement with verified-channel routing, privacy limits, clear unknowns, human review, and STOP AUTOMATION guardrails.
Why it connects to Local Lead Rescue
Local Lead Rescue System packages intake, follow-up, CRM-label, and human-review patterns for local-service and property-management teams. This free worksheet applies the same source-card approach to access-sensitive security incidents: respond fast, route correctly, protect privacy, and keep unsupported security, legal, or fee claims out of automated drafts.
See Local Lead Rescue System Start with the free missed-lead checklist