OperationsRequested Feature

Damage Tracking

Damage Tracking lets you record property damage caused by guests, send structured notifications requesting compensation, generate a Stripe payment link, and track the case through to resolution — all from a single record linked to the reservation.

⚠️
Damage Tracking is not included in the standard product distribution. Contact support to have it enabled for your workspace.

Where to find damages

All damage records are listed under Ops → Damages in the left navigation. The list shows each damage title, the linked reservation, the amount, the current status, and who reported it.

Click any row to open the damage detail page, where you can edit the record, send guest notifications, generate a payment link, and link coordination tasks.

Creating a damage record

Click Report Damage on the Damages list page. You will be asked for:

  • Title — a short description of the damage (e.g. “Broken bathroom mirror”)
  • Reservation (Internal ID) — the internal reservation ID shown on the reservation detail page under the label Internal ID. This is not the Hostaway or PMS reservation ID — using the wrong ID will cause the record to fail to save.
  • Amount — the compensation amount in full units (e.g. 350 PLN)
  • Currency — PLN, EUR, USD, or AED
  • Reported by — whether the damage was identified by the Operator (your team) or by the Owner (a property cohost)
  • Description — optional additional detail

The record is saved with status Open and is attributed to the team member who created it.

⚠️
The reservation field requires the Internal ID — the number shown on the reservation detail page next to the tag icon, labelled “Internal ID”. Do not use the Hostaway ID (the number visible in the PMS URL or the Hostaway dashboard).

Damage statuses

A damage record progresses through the following statuses:

  • Open — damage recorded; no guest contact yet
  • Notified — at least one guest notification has been sent
  • Payment Pending — a Stripe payment link has been generated and sent to the guest
  • Paid — payment has been collected
  • Waived — the claim has been dropped (no payment required)
  • Disputed — the guest has contested the charge

Guest notification flow

Enhanced Rentals sends up to three escalating notification emails to the guest, each more urgent than the last. Notifications are sent manually — you choose when to trigger each step.

  • Step 1 — Initial notice: informs the guest that damage was identified and states the compensation amount.
  • Step 2 — Follow-up reminder: sent if the guest has not responded; reiterates the claim.
  • Step 3 — Final notice: last escalation before other action is taken.

Each notification is sent in the guest's language where possible (Polish, English, German). The timestamp of each sent notification is recorded on the damage record.

💡
Use the three-step flow to give guests a clear, documented opportunity to pay before escalating. The timestamp trail provides evidence if the case proceeds further.

Stripe payment link

After notifying the guest, you can generate a Stripe payment link directly from the damage detail page. The link opens a hosted Stripe checkout for the damage amount and currency.

Once a payment link is generated, the damage status moves to Payment Pending. When the guest completes payment, the status updates to Paid and the collection timestamp is recorded.

ℹ️
Stripe must be connected to your workspace before payment links can be generated. Contact support if Stripe is not yet configured for your account.

Waiving a damage claim

If you decide not to pursue a claim — for example, because the damage was minor or the guest relationship is more important — set the status to Waived from the damage detail page. The waiver timestamp is recorded for your records.

Linking coordination tasks

Operational work associated with a damage — a repair, a replacement delivery, a post-repair inspection — can be linked to the damage record as coordination tasks.

From the damage detail page, enter the task ID in the Linked Tasks field and click Add. Multiple tasks can be linked to a single damage. Linked tasks remain fully independent — completing or cancelling a task does not change the damage status.

ℹ️
Tasks are created separately under Service → Task List. Linking connects an existing task to a damage record; it does not create a new task.

Reported by — Operator vs Owner

The Reported by field distinguishes who first identified the damage:

  • Operator — your team identified the damage during a check-out inspection or cleaning.
  • Owner — a property owner (cohost) reported the damage after visiting or reviewing the property.

This field is for internal reference and reporting only. It does not affect the notification flow or payment logic.

Notes

The Notes field on each damage record is a free text area for internal use — add context, photos of the damage, guest correspondence references, or any other information relevant to the case. Notes are never sent to the guest.