Our accounting, maintenance, and guest communications teams each hold a different piece of the same claim. We use a simple Slack workflow to move those pieces into one reviewable record before the filing deadline passes.
The workflow started with a recurring operating problem. Accounting would receive a maintenance invoice. The guest communications team knew which reservation might be connected to the damage. Maintenance had the photos and repair context. Nobody had the whole file.
Emailing the invoice to another person did not solve that. It moved the document, but it did not assign the research, collect the evidence, or show whether anyone filed the claim.
Start with a dependable trigger
Each Friday, accounting uploads the relevant maintenance invoices to a dedicated Slack channel. The schedule matters because it creates a regular handoff instead of relying on someone to remember an unusual line item during a busy week.
On Monday, the reviewer goes through the invoices, identifies repair items that may relate to a recent guest stay, and prepares the potential claim record. The review is deliberately framed as a screening step. An invoice does not prove that a guest caused the damage, and the workflow does not decide whether a charge is covered.
Put the claim facts in the form
For an item worth reviewing, the team opens a Slack form and records:
- The reservation link and property
- The booking platform and applicable claim method
- The checkout date
- A short item summary and damage description
- Available photos and invoice excerpts
- The estimated repair or replacement cost
The form creates a new Slack thread and a row in the tracking sheet. The thread is where the team resolves missing information. The sheet gives management a simple view of every open item and its current status.
Separate preparation from submission
We use automation to assemble information, identify missing fields, route the task, and remind the owner. A person still reviews the reservation history and supporting documents before anything is submitted.
That distinction is important. The goal is to document legitimate damage consistently and submit complete claims on time. The workflow should never invent a cause, overstate the evidence, or turn every maintenance invoice into a guest claim.
Guesty's current guidance says a Damage Protection claim should include a detailed description, an estimated repair or replacement cost, photos, and supporting documents such as receipts, invoices, or estimates. It also says claims must be submitted after checkout and within 30 days of the checkout date. We use those requirements as checklist items, but the platform's current terms and the specific reservation still control.
Make follow-up visible
After the Monday review, the workflow follows up during the rest of the week on records that are still missing evidence, awaiting review, or ready for submission. Status changes stay in the claim thread instead of disappearing into direct messages.
A useful status list is short: needs review, needs evidence, draft prepared, submitted, more information requested, approved, declined, paid, or closed. The owner and next action should be visible with the status.
Why this works outside short-term rentals
The same pattern applies anywhere one department receives the bill and another department owns the underlying event. Think warranty claims, insurance submissions, vendor chargebacks, tenant damage reviews, or construction back charges.
The workflow needs five things:
- A regular intake point
- A structured record tied to the original event
- Supporting documents in one place
- A named owner and deadline
- A status that someone else can audit
Slack is useful here because the team already works in it. The bigger lesson is to build the handoff around the evidence and the deadline, not around the department that happened to receive the first document.