Properties
Alerts needing action
What needs attention now: cases nobody has taken on, records to complete, and iPads or property settings to fix before the next guests.
Every case opened in the period, newest first. Click a row to open its timeline. The CSV opens in Excel; each download is recorded in the activity log.
| Opened | Property | Type | Status | Claimed by | To first contact | To completed | Outcome |
|---|
Noise and guest call cases opened in the period. Response times are medians from the signal (when the case opened). Night = the property's quiet hours. Guest contact is a call the guest answered, or a phone call or visit; messages on the iPad are counted separately, staff and automated apart. Offline iPads are counted, not timed.
Response times
| All hours | Night |
|---|
Cases per property per week
| When | Property | Issue | Reporter | Status | Reply to neighbour |
|---|
Opinions residents sent about how short-term rentals in their area are handled. Every 事業者 and 帳場 sees every opinion; the distance is to your nearest property. Your answer is shown to the resident under your organization's name.
| When | Opinion | Resident | Answer |
|---|
Neighbours within 500 m of your properties see these in their app, under your organization's name.
Visits
| Date | Visit | Who visited |
|---|
Notices to the neighbourhood
| Date | Type | Notice |
|---|
Requests to monitor
Your properties
| Property | Reception | Invites |
|---|
Properties you monitor
| Property | Owner | Since |
|---|
History
| When | Property | Owner | Reception | Result |
|---|
Admins manage properties, devices, the team and settings. Staff handle alerts and cases.
| Name | Role | Last sign-in |
|---|
Pending invites
Everything done with your company's data, including any access by Community Guard platform operators (always with a stated reason).
| When | Who | Action | Target | Reason |
|---|