Turn guest damage into a claim-ready evidence packet in minutes.
Upload incident notes, photos, receipts, and guest or cleaner messages. ClaimPilot classifies the evidence, flags gaps, and drafts a stronger packet you can submit without stitching everything together manually.
What the packet includes
Evidence classification, completeness score, missing-proof checklist, and a reusable packet history.
Why now
Damage claims often start as scattered messages and photos. ClaimPilot turns that mess into a structured claim packet the moment an incident happens.
How it works
1. Capture the incident
Paste the notes and upload the evidence details you already have.
2. Classify the proof
The model sorts receipts, photos, conversations, and policy references into a coherent packet.
3. Fill the gaps
See the missing items and get a clearer checklist before you submit the claim.
Pricing
One claim packet audit to see the output.
For one host managing their own incidents.
For small co-host teams and multiple listings.
Recent packet preview
Incident: broken lamp + stained rug
Photos classified: 4 Receipts found: 2 Messages found: 5 Policy references: 1 Missing proof: time-stamped before/after photo, repair estimate Completeness score: 82/100 Next step: upload the repair estimate and submit the packet.What the audit checks
4 evidence classes
Photos, receipts, messages, and policy references are grouped into one packet.
1 cached packet history
The same input hash reopens the same packet, so repeat reviews do not waste AI calls.
3 plan levels
Free, Solo, and Multi-property pricing keep the first sale path simple.
Evidence types we see most often
Before / after photos
Damage proof with timestamps or file names from the incident folder.
Repair quotes
Line items for replacement, repair, or professional cleaning.
Guest and cleaner messages
Messages that place the event in time and explain what happened.
Start the free claim audit, then move into the dashboard.
The first live slice gives you a clear landing page, durable signup, claim generation, and a support path without making the host learn a new workflow.