An Airbnb reimbursement below the amount requested can reflect a denied item, a lower valuation or an adjustment for money already recovered. A request for another document can leave an item undecided. Read the disposition of each item before preparing a response.
Airbnb’s HDP terms allow approval in whole or in part and provide for notification of the calculation. HDP terms, §§4.3–4.4.
Identify the item and the disputed question
Copy the stated reason into a short item list beside the requested and approved amounts. Mark anything the message leaves unclear. If it announces only a total, ask which items were approved, reduced or denied.
The following categories organize a host’s response; they are not official Airbnb denial codes.
| Stated issue | Question to resolve | Focus of the response |
|---|---|---|
| Timing | Which step was considered late? | The dated request, notification or submission confirmation for that step |
| Guest responsibility | What connects the condition to this stay? | Earlier condition, discovery sequence and relevant observations |
| Excluded loss | Which provision applies to the described work or damage? | Facts bearing on that classification |
| Unverified evidence | Which document or fact could not be verified? | Its source, original record or an acceptable alternative format |
| Valuation | Which calculation produced the reduction? | Item details, repair scope, comparable cost and identified offsets |
Sending another full bundle can obscure the answer when one specific record addresses the issue. Start with the missing connection.
Match the response to the reason
Suppose, hypothetically, Airbnb accepts that a damaged rug is eligible but approves less than the requested amount. More photographs of the damage may add little. The question is how the amount was calculated.
Ask for the calculation and identify the input you dispute. For example, an incorrect acquisition date would call for the purchase record. A dispute over repair cost would call for the scoped estimate. Airbnb’s valuation provisions use category-specific calculations and account for other recoveries. HDP terms, §7.
A different response is needed if the reason is wear or maintenance. Identify the physical finding behind that classification and the evidence addressing it. The companion guide to damage versus wear and tear explains how to separate condition, timing and cause.
For an unreadable or unverified document, ask which file is affected and what source or format would resolve the problem. Keep the answer narrow enough to act on.
Clarify the status before asking for review
An evidence request, a final denial and a payment still processing call for different follow-up. Ask whether the item remains under assessment if the message does not say.
For certain initially automated HDP outcomes, Airbnb publishes an option to request human review and provide further evidence or context. That statement does not establish a universal appeal deadline or a right to repeated reviews of every manually decided claim. Airbnb’s reimbursement process.
Where that option applies, identify the result you want reviewed and the additional context. For other decisions, request clarification of the item and reason without assuming the same procedure applies everywhere. Use any case-specific response date supplied by Airbnb.
Send a response someone can resolve
A focused follow-up might read:
Please confirm whether the rug item was denied or approved at a reduced value. If reduced, please identify the calculation and any offset applied. The purchase record identifies the acquisition date; the repair estimate separates the proposed work and charge. Please identify which input remains unresolved.
This hypothetical message addresses an uncertain valuation. It would need different facts if the issue were responsibility, timing or eligibility.
Retain the response, the records supplied and the subsequent decision together. For the broader system of evidence indexing, submission receipts and payment reconciliation, see Airbnb Damage Claim Documentation: From Photos to Payment.
Host questions this article answers
Check lead time, booking pace, day type, gap shape, and revenue context before choosing the pricing move.
No. It may be early in the booking window, blocked by shape, or isolated to weak day types.
Tools can suggest numbers. The decision still needs context from the host calendar and KPI history.