Compliance
London's 90-day rule explained
Understand the short-let limit, what counts, and how a compliant operating plan can use longer stays.
Big Ben Suite Host Club
Check the rules before you list, compare your letting options and learn from real hosting stories. The guides are free to read and open without an account.
Browse the host guidesHosting storiesPublished host guides
These guides are free to read. If one matches the problem in your own property, send us the link and your question on WhatsApp.
Compliance
Understand the short-let limit, what counts, and how a compliant operating plan can use longer stays.
Strategy
A practical comparison of short, mid and long stays, with the assumptions behind the published example.
Operations
See the published arithmetic and the operational questions to check before listing rooms above a pub.
Send your London postcode district, how many bedrooms you have and any question you want to discuss. If you want management help, we can discuss what we could take on, which checks are still needed and whether a property visit makes sense.
Host Club guides are free to read. Property management is a paid service with a maximum management fee of 9%, including applicable VAT. The initial standard property visit and standard setup are free. Physical costs are separate and need your prior approval.
See how the management fee is calculatedWhy a claim is decided before the guest ever checks out.
Which tool a deposit really is, and where hosts assume too much.
Building your own payout trail before you need it.
Three questions, asked the same way, before you confirm.
How to document the stay instead of arguing about it.
Protecting the calendar without punishing the guest.
Already have a property in mind? Try the monthly scenario calculator.
A cancelled booking can leave more than an empty calendar. Damage can leave a repair bill, and a payout can raise more questions than it answers. These stories come from our own Airbnb hosting correspondence: the problems we faced, the evidence we brought and the decisions that followed. Some decisions changed. Others did not.
The first answer is a starting point to check. Does it address the problem you raised? Does it match your records? Has each question actually been answered? Keep your evidence, ask for a clear explanation and follow your rights and your case through to the outcome. That preparation matters before the next difficult booking arrives.
A lease ended before the bookings did. Check how long you can host and agree who will block dates or handle existing reservations if circumstances change.
A guest disputed a damage claim. Agree who takes condition photos, who keeps the record and when a problem needs to be escalated.
A confirmed booking disappeared because of a problem with the guest’s payment. I had held the dates for that reservation. Being told why it was cancelled did not answer the question I was asking: what would happen to my payout?
The first explanation also discussed a calendar sync issue. I brought the conversation back to the cancelled booking, explained that I could not control payment collection, and asked for the basis of the refusal. After an explicit payout rejection, I requested a senior review and the exact policy reference in writing. A representative said a senior manager would give the same answer. I continued with the request.
The senior manager reviewed the payment security cancellation and approved a one-time exception for the full payout. I checked the amount in upcoming payouts and confirmed it.
Stopping at the refusal could have left the booking without that further review. My lesson is to keep the confirmation and availability record, state the financial question precisely, and ask for a documented review when the answer does not address it. The exception in this case was a result, not a promise that every escalation will pay.
I kept asking where my payouts were. The explanation that finally mattered was specific: they had been paused pending a tax information update. I told support that the previous exchanges had not made that obstacle clear to me.
I first asked for a temporary release while I completed the update. The representative said that was not possible and identified the account action required. I completed the requested information, then reported that the payout had been released. Support also confirmed release and acknowledged the delay in identifying the actual issue.
I asked what would be done about the time lost. The response offered to record the experience as internal feedback; it did not approve compensation. Release of the payout and compensation for the delay were different questions.
Without identifying the hold, I could have continued waiting for a transfer that still needed action from me. Keep account notices alongside your payment records, and ask whether the money is awaiting a host action, an internal review or a transfer. A reassuring reply is useful only when it identifies the stage that is actually blocking payment.
A guest could no longer travel, and support asked me to make an exception to the reservation terms. Later, the same booking returned as a request to shorten the stay. These were not abstract policy questions: I had already held the dates, and reducing the booking could reduce the income I had planned around.
I acknowledged the guest’s situation without agreeing to a refund or alteration outside the booking terms. When support asked again about a full or partial goodwill refund, I stated my decision clearly rather than leaving a sympathetic reply open to interpretation.
Support confirmed that it would uphold my decision. In the earlier conversation, it said the guest would receive only the partial refund available under the cancellation policy. A later payout enquiry produced a future release date. A separate request for host credit was declined.
The lesson is not that compassion and commercial boundaries are opposites. It is that an exceptional refund, a shorter booking and the timing of your payout are separate decisions. Keep the original terms and record exactly what you approve. In this case the written boundary was respected.
A lift outage first led to a suggestion that I could offer a goodwill refund. I explained that the lift was managed by the building and was not included in my listing’s amenities. Support suggested making the floor level clearer in the description. Later, another message announced a partial refund of £238.50 to be adjusted from my payout.
I did not treat the new announcement as the end of the discussion. I objected in writing, referred back to what the listing offered, explained the building-wide problem and reported that the lift had been repaired. I then asked for the final position in writing for my records.
Support withdrew the partial refund decision for the lift issue. A further manager repeated that no partial refund would be made on that basis. The partial refund announced at the start was no longer the decision on file.
Had I left the announcement unanswered, the proposed deduction could have remained the operative decision. Keep the version of the listing relevant to the stay and the earlier case messages. If a later answer appears to contradict them, identify the precise contradiction and ask for a written correction. The useful evidence here was what had actually been offered, not simply that the outage was outside my control.
In another lift failure, I told support that the building’s management controlled the equipment and that I had reported the problem immediately. I wanted the reservation income retained. The guest wanted to leave and receive a full refund.
Support’s response focused on a different fact: the lift was listed as an amenity for that booking. I declined to provide a full refund and repeated that the apartment itself was available. Support nevertheless said it had cancelled the reservation and refunded the guest.
I kept the conversation open, requested written communication and asked Airbnb to consider compensation for the dates and income I said I had lost. The final review maintained the guest refund and said no further support would be offered. There was no approved replacement payout for me in that correspondence.
The risk was not only a broken machine. It was a promised feature becoming unavailable while I still depended on the booking income. Keep records of the listing and the repair response before a dispute develops. Pursue a review when needed, but assess its answer honestly: persistence created a written record here, not a financial reversal.
A guest asked support to cancel after a disagreement about the booking. I said I was ready to host and believed the guest was still coming. Support said its review of the messages showed that the guest had already said they did not want to proceed before I accepted the reservation.
I disputed the outcome, explained the preparation and last-minute vacancy risk, and asked Airbnb to cover the payout. When the representative refused, I requested a manager. The case was transferred.
The senior manager acknowledged the effort I had put into preparing the property but maintained the cancellation and full refund. A later written summary confirmed that no host payout would be processed for that booking. My account of events did not become an accepted finding simply because I repeated it or escalated it.
An unresolved disagreement about whether a guest still wants to book can leave a host preparing for income that may not survive review. Preserve the sequence of the guest’s messages and the acceptance, rather than relying on memory. Ask for a review when the sequence is disputed, but do not build your cash planning around the assumption that a senior title guarantees a different decision.
The property owner wanted the rental agreement ended early, leaving upcoming bookings I could no longer host. I warned guests and asked support for help. In linked cancellation messages, responsibility was moved to me and financial consequences were announced. Telling a guest first had not, by itself, protected the account.
I explained the lease situation, said I did not accept the cancellation charges, and described the termination correspondence and agreement I was providing. Support asked for documentation and the reservations involved. The issue needed a case-specific review, not just the statement that the circumstances were outside my control.
Support later listed five reservations it had cancelled and confirmed that their cancellation fees had been removed. A further reservation was separately approved for cancellation without fees or other consequences. I also reported that money had reached my account and thought it was a return of deducted charges.
Unaddressed bookings could have become a chain of cancellations, charges and disappointed arrivals. Keep the loss-of-access documents and a reservation-by-reservation record before requesting action. A fee waiver for one booking is not a blanket answer for all the others; ask what has been changed on each affected reservation.
Support contacted me about a guest’s complaints concerning appliances and the bathroom. I replied that it was late where I was and that I would send the details the following day. The representative said the case could not remain open for long. Before my detailed response, support announced a partial refund.
I reopened the conversation and submitted a formal objection. I challenged the timing, said I had not been given a proper opportunity to respond and asked for a senior review. Support investigated again but said the guest had raised the request earlier and had tried to resolve the problems with me.
The final response maintained the refund. The two accounts of the earlier contact were not reconciled by a guest message history in this record. My objection was real, but it did not establish that no complaint had ever been made, nor did it reverse the decision.
The practical risk was that the decision could move forward with only a short holding reply from me. Keep complaint messages and appliance records ready before you need them. If you cannot provide a full answer immediately, a brief factual response and the evidence you already have may be more useful than a promise to explain later. That is a preparation lesson from the sequence, not a guarantee that a faster reply would have changed the refund.
A guest reported a possible pest problem and left. I told support that I had attended promptly, replaced mattresses, carried out steam cleaning and taken preventive action. I also said my own inspection had found no signs. Those were my account of the response and my observations, not a professional finding that the complaint was false.
Support acknowledged the effort but initially proposed refunding the unused nights because the guest had checked out. I objected to carrying the lost nights after taking action, explained the work again and asked Airbnb to consider compensation. When a call was suggested, I asked to continue in writing.
A senior manager then said Airbnb was handling the guest concern and that my payout for the reservation would not be affected. I thanked the team and closed the conversation.
Without a clear account of my response, the financial discussion could have remained at the proposed unused-night refund. Document what you did, when you did it and what you can actually substantiate. Ask separately how the guest’s departure affects your payout; do not assume either that remedial work guarantees payment or that a departure automatically settles the financial question.
A disagreement about the number of people staying and information requested before arrival ended in a cancellation. I told support that the guest had cancelled, yet the cancellation appeared to be attributed to me. My request kept getting mixed with advice about guests and listing details.
I repeated the point that needed a decision: the cancellation record and its consequences. Support eventually said it would waive the cancellation penalties, listing the fee, calendar and automatic review consequences separately. I thanked the representative, but the work was not finished.
I then reported that the cancellation still appeared in my Superhost progress report and asked again. Support later confirmed that the performance position had been updated and the cancellation no longer affected it.
A waiver could have sounded complete while another part of the account still showed a consequence. Keep the cancellation notice, the waiver and the affected performance record together. Check the specific consequence you challenged and pursue a precise correction if it remains. A helpful sentence in chat and a change applied throughout an account are not always the same stage.
A future guest was worried about nearby construction. I had informed guests about the works and told support I could not promise what the future noise would be. The first response said the guest was eligible for a full refund.
I asked for my position to be recorded and requested a senior review. Other reservation complaints had entered the discussion, so the resolutions representative separated this upcoming booking from those cases and asked about the current conditions and possible alternatives. I did not turn uncertainty into a guarantee of silence.
The later decision said check-in had not happened, there was not yet an actual stay issue to address, and the guest had booked elsewhere. Support processed the cancellation from the guest’s side and said I would receive the full payout with the dates available again.
Without separating future risk from a problem already experienced, the booking could have been assessed on the wrong factual basis. Keep your advance disclosures and identify which reservation each complaint concerns. Be accurate about uncertainty, then ask support to decide the case on those facts. The result here does not make construction harmless or remove the need to disclose it.
Support asked whether I would give a guest a full goodwill refund. I said I would agree if Airbnb covered the loss of those dates. The representative said no additional amount could be provided and that a full refund required my consent. It was a conditional proposal, not an unconditional approval.
In a later conversation about the same booking, I challenged a payout I believed was too low. The representative initially understood that I wanted to offer a refund. I corrected that misunderstanding: I was asking why I had received less, not offering money back.
Support calculated a three-night payout and attributed it to an alteration initiated by the guest. I said I had not accepted that change and asked how it could have happened without my approval. Support maintained the calculation and closed the thread in favour of another open case. This record does not resolve how approval was obtained or show an additional payment.
The risk is that a goodwill discussion and a disputed booking change can leave an unclear financial trail. Keep the original booking, every alteration request and your exact response. If an amount changes, ask for both the calculation and the approval record. Correct the description of your request before debating the answer to a question you never asked.
A guest left early after reporting nearby construction noise. I rejected a deduction, explaining that the road and bridge works affected the neighbourhood rather than being work inside my building. Support initially announced a £905.29 guest refund and an expected host payout of £597.68.
In a linked conversation, support then said the reservation was still active, no adjustment was being made and I was receiving the full payout. I challenged the calendar position: I said the departed guest still appeared to occupy the dates, preventing me from offering them again. When the availability changed, I said it was too late to find replacement guests.
The financial answer changed again. Support reported a processed adjustment of £844.02 and a new host payout of £369.27. Those figures differed from its first calculation, and the messages did not reconcile them. I asked for the guest’s evidence, compensation for the lost nights and a senior review in writing. The senior manager upheld the refund decision and declined to reverse it.
The risk was being left with an empty home while relying on an assurance of full payment that a later decision contradicted. Keep the calendar status, each refund calculation and every payout assurance together. Ask which decision now applies and why the amounts changed. A confident reply should not end your enquiry while the account tells a different financial story.
Support contacted me after a guest said I had asked them to cancel. I explained that another reservation conflicted with the dates and that I believed the system should have prevented the overlap. That was my explanation of the problem, not an established technical fault.
The representative offered to help cancel without a cancellation fee and asked for my confirmation. I gave an explicit approval. The conversation then moved to thanks and closing messages.
The distinction matters: this record contains an offer of fee-free cancellation and my permission to proceed. It does not contain a separate statement confirming that the cancellation was completed or a fee entry showing the final result.
Leaving an overlap unresolved could put two arrivals against one available home. Keep both booking records and obtain clear authority for the action you want. Then check the completion record, rather than treating a courteous closing message as proof that the reservation and charge have changed. Agreement, processing and the final account result are separate checkpoints.
I agreed to refund a guest after a booking overlap. The automated guidance suggested there would be no cancellation penalty, but the human response warned of a £490 fee, blocked dates and a Superhost consequence. Later, support said the cancellation had been made with those penalties applied.
I sent screenshots and explained that several listings represented the same home, with linked calendars that I said had failed to block the overlapping dates. I expressly rejected the penalties and asked for the circumstances to be reviewed.
The later written decision said the cancellation qualified for the fee and other consequences to be waived and that the record had been updated. The same message expressly said the calendar would remain blocked for the cancelled dates. The fee decision improved; saleable availability did not follow from it.
Without challenging the applied penalties, the announced charge could have remained. Keep evidence of how the linked listings appeared when the conflict arose. When a waiver comes, read its limits: ask separately about the fee, performance record and calendar. Calling the whole case “fixed” would have hidden the blocked dates that the final answer itself preserved.
The next two accounts involve the same earlier reservation but different financial questions: a later net-payout calculation and the original cancellation after a lift problem. They do not describe two separate recoveries.
I questioned a payout that was smaller than I expected. I knew an earlier cancellation amount was due to be deducted, but the net figure still did not make sense to me. The first list of entries was not enough, so I asked for the calculation in detail.
Support identified two booking credits, £775.06 and £740.35. Together they made £1,515.41. It then listed adjustments of £1,081.61 and £33. Subtracting those amounts produced the £400.80 shown in its explanation.
That arithmetic explained the net figure; it did not answer whether each deduction was justified. The conversation closed without a further acceptance from me.
The risk in an unexplained net payout is missing a deduction or disputing the wrong booking. Keep a ledger that links each credit and adjustment to its reservation, and ask for the actual arithmetic when the total is unclear. Understanding how a number was calculated is the starting point for checking whether its ingredients belong there.
A reservation had been cancelled by agreement after a lift problem. When the lift worked again, the guest wanted to stay at the same price. I asked how to proceed because the guest had already paid. A repaired building feature did not answer what happened to the cancelled booking and its money.
Support said that this reservation could not be reinstated and that the guest needed to book again. I asked for help reaching the guest and explicitly authorised the full refund of the old reservation. Support then reported that the refund had been processed and that I would receive no payout for that cancelled booking.
The guest’s rebooking was not confirmed in the messages. After the response took too long, I told support I had accepted another reservation.
Waiting on an assumed reinstatement could have left the property unsold. Keep the old refund and any new reservation as separate transactions, and establish which booking actually exists before holding dates for it. In this case the operational recovery was a reported different booking, not revival of the cancelled one.
Support said a guest had cancelled by mistake and wanted to book the same property again. I did not want to host that person again and asked the representative to read the messages that concerned me. But whether I would host again and whether I would refund were different questions.
When the representative asked specifically about the remaining refund, I gave an explicit full-refund approval while repeating that I did not want the guest back. Support said it processed the cancellation and refund and that the calendar would open.
The payment explanation was important: support said the host payout had not yet been released, so the refund was a payment adjustment. Support also suggested a booking-setting change; the record does not show that I made it.
If those decisions were left in one vague refusal, a further booking or an unresolved refund could have complicated the situation. State the hosting decision and the financial permission separately, keep the exact approval, and check the relevant booking controls. Do not assume that declining a guest automatically changes your account settings or settles the old payment.
This payment-delay account may be related to the earlier story, “The payout delay with a missing explanation”. The records do not establish that connection, so I have not treated them as either a single continuous case or two proven independent incidents.
I asked about a payout that had not arrived. In one conversation, support said it was scheduled and suggested waiting, then proposed closing the issue as resolved. I returned to say the money was still missing.
In the linked conversation, the representative repeatedly said the payout had been released and referred to processing time. I pointed out that my account still described it as planned, not sent. I challenged the booking details used in the explanation and asked for a more experienced review.
The representative said the team had been consulted and predicted receipt by the end of the day. I later reported that the transfer still had not arrived and asked again for someone with authority to take over. This exchange ends with the disagreement still open; it does not establish a completed transfer or its eventual cause.
The risk was letting a completion label replace the actual transaction stage. Keep the payout status and the supporting messages together, and ask which specific transfer the answer refers to. A request to wait can be reasonable, but it does not reconcile “scheduled” with “sent” or prove receipt. Record the discrepancy before agreeing that a missing-payment case is resolved.
The stay had sounded like a success. The guest described the home as comfortable and thanked me for a good experience. After checkout, I reported damage to a glass coffee-table set and requested £750. The guest refused, arguing that the tables were already damaged and the amount was too high.
I asked Airbnb to review the request. I explained that I had recorded the home before arrival and inspected it after departure. I also explained why I treated this as more than ordinary wear. Because the furniture belonged to a set, I described the replacement issue and offered to return the difference if I found a cheaper replacement.
The claim page later recorded that Airbnb Support had paid £750. The initial refusal came from the guest, not from Airbnb.
Without a record of condition, this could have remained one person’s account against another’s. Photograph and describe the property before a dispute exists, then explain the specific damage and the basis of the amount. A guest’s refusal is a stage in a claim, not necessarily its final answer.
The next two accounts may concern the same damage claim. I have kept the claim-page outcome and the support correspondence separate because their connection is not confirmed.
A comfortable stay can still end with a difficult checkout. After this one, I reported stains across bedding, curtains and the sofa, along with washing-machine and window problems. I requested £570. The guest declined, disputing both the extent of the mess and the amount.
I asked Airbnb to review the request and explained the cleaning I had done myself and the window mechanism that I believed needed professional repair. My early suggestion about what might have affected the washing machine was a possibility to investigate, not a technician’s finding.
The claim timeline shows a request for more information, followed by closure. The page says additional information was needed and no response was received. It does not show a £570 payment. That page description is not a complete audit of every conversation about the work.
The risk is doing the recovery work while the evidence trail falls behind. Record the condition before cleaning, distinguish a suspected cause from a diagnosis, and track exactly what information the claim handler still needs. A submitted amount and a closed status do not establish reimbursement.
My claim involved several different problems, but the follow-up document lists kept returning to the washing machine and cleaning. I was also claiming damage to an aluminium window mechanism. I did not want that item to disappear simply because the conversation had moved on.
I asked for the claim to remain open, pointed out the missing window item and requested confirmation that a specialist’s quote could still be submitted. I explained a separate difficulty: I had cleaned the machine and stains myself, so I did not have the same paperwork as a completed contractor job. I also proposed existing message evidence as an alternative to one requested form of evidence.
The visible support exchange ends in temporary closure for insufficient documents. It says the file could be reopened when documents arrived within the stated case window. It does not expressly confirm that the window mechanism remained included or that my proposed alternative evidence was accepted.
If I had treated a generic follow-up as confirmation of the whole claim, an important item could have gone unanswered. Keep a list of every claimed item, its evidence and its last written response. Distinguish an estimate for proposed work from an invoice for completed work. A question sent is not an answer received.
A reported bed-bug problem put more than one stay at risk. Airbnb said the current reservation had been cancelled and requested a professional inspection, with documents needed before the listing could return to bookings. Leaving the matter unresolved could have affected upcoming reservations as well.
I arranged a pest-control visit and later told support that inspection and treatment had been completed. I sent an invoice and treatment report and asked for the listing to be reactivated. Support said it could return to bookings. My invoice was £360; support limited its reimbursement to £300, distinguishing inspection from treatment, and later said that reimbursement had been processed.
A later exchange about the same reservation raised a separate refund deduction. Support then made an exception, saying Airbnb would cover the unused-night refund and my payout would not be affected. I reopened the conversation for clarification before accepting that explanation.
The practical lesson is to follow the operational and financial questions separately: what restores availability, which costs are accepted, and whether a later adjustment changes the payout. Keep the report and the written decision together.
The guest reported that the dishwasher was not working. I went to the property, found that it would not run and asked Airbnb how much of the service cost it could cover. At that point I knew the appliance had failed; I did not know why.
Support asked about the cause and distinguished maintenance from guest-caused damage. I said I would investigate and asked to keep the discussion in writing. When support followed up, I was still waiting for the technical service to finish its research and said I might buy a replacement.
The conversation closed with directions for a damage request if there was evidence of guest-caused damage. There was no technical finding, approved repair amount or reimbursement in the visible exchange.
A replacement bought in a hurry could leave a host paying for the appliance without having established what happened. Record the fault and obtain a factual diagnosis before presenting a suspected cause as proven. Technical evidence should answer what failed; it does not automatically establish guest responsibility or guarantee payment.
Several complaints arrived together: cleanliness, key handover and mould in the bathroom. I believed the guest had been looking for problems and said so. Support did not treat that belief as an answer to every reported condition. It distinguished complaints it could not substantiate from the mould it considered supported by the guest’s material.
I said I wanted to inspect the home, but I was away. The discussion then widened to an advertised carbon monoxide alarm and the promised arrival greeting. I later said I had attached alarm photographs, explained the late-arrival key handover and refused a refund.
Support discussed a possible partial refund rather than a full one. The visible record does not establish a final refund amount or deduction. Nor does it establish that my suspicion about the guest’s motives was correct.
A dispute about intent can consume the time needed to answer a specific condition or amenity question. Prepare evidence for each issue separately: what was advertised, what was present and what was checked. Challenge an allegation with facts; do not let an unproven theory about the guest substitute for them.
I reported a broken bed support and asked for £700 towards a replacement. I said the damage had not been there before. From my perspective this was a substantial failure, not a minor mark to ignore between stays.
I repeated that the damage had not been there before. Support transferred the conversation. The next response said the reimbursement request had previously been declined and directed me to a liability-insurance intake form.
That is where the visible outcome stops: a different application route. The record does not show the form being submitted, an insurer accepting the claim or £700 being paid.
A damaged essential item can create both a replacement cost and a readiness problem for the next stay. Preserve the condition evidence and ask which route is actually being considered, what it requires and whether the original decision still stands. Being given a form is progress in routing, not an award.
A guest raised a cleanliness complaint while I was also chasing the reservation payout. In the payment exchange, support first said the payout was under verification. The complaint required a separate answer: did I agree to a refund?
I described welcoming the guests personally, their initial response to the apartment and the later conversation about needing a different bedroom arrangement. I believed the complaint followed that change in requirements, but that remained my interpretation. I refused a full refund and asked support to share any evidence behind the allegation so I could respond.
Support said it respected my decision and reported that the payout had been sent. It later repeated in writing that it respected my decision not to refund. There was no finding that the guest had fabricated anything.
Without a clear account of the arrival, the decision could have rested on a thinner picture. Keep the actual sequence, listing details and relevant messages together. State exactly what you accept or refuse, ask to address the evidence, and track the payout separately from the complaint decision.
The guest had reported a door-lock problem. I told support I had checked the property and found no problem, then asked where to send my video. Having evidence on my phone and delivering it to the case turned out to be different tasks.
Support first replied that I could send the video through that email. It later said the video had not arrived within the response windows and proceeded with the guest’s reported issue. I objected that I still had not been given a usable submission route and asked for a manager. Another representative said a reply-enabled email had been sent. I then reported that the file would not upload. Support suggested a shorter video and asked for an error screenshot.
The visible exchange never confirms receipt of the video or a reversal of the decision. The problem was not resolved simply by saying that an email had been sent.
If a submission route fails, the decision may move forward without material you intended to provide. Test the route early, record the error and request written confirmation that the evidence has reached the correct case. Keep the full original even if a smaller copy is suggested. Those are practical safeguards, not proof that an appeal will succeed.
It was checkout day, but the guest was not answering messages or calls. I told support that the cleaning team was waiting outside and that I was paying for their time. I could not confirm from unanswered messages alone whether the guest had left or the keys were available.
I asked Airbnb for help making contact. Support tried too, then asked whether the problem was a guest still inside or missing keys. I relayed what the cleaning team could actually observe: they rang the bell and nobody answered.
Support said the waiting time and other relevant costs could be requested through the Resolution Center. The conversation does not show an approved amount, a completed entry or a reimbursement. A suggestion made by a representative is not evidence that the suggested action happened.
An uncertain checkout can delay preparation and put a later arrival at risk. Keep attempts to contact the guest, the cleaner’s attendance and any actual cost documented. Separate observations from assumptions about occupancy, and get the access position resolved through an appropriate safe process. A route to request costs is not a promise that every cost will be paid.
Support contacted me because the guest said the spare key would not open the apartment. I said a spare had been provided and that I was travelling to the property. The guest had already arranged a locksmith. Support then said a receipt and messages showed that I had agreed to pay; I disputed that account.
I went to the home and continued the discussion through support. Later, after a partial refund was announced, I reopened the case and said the other key had been left inside. Those competing explanations were not independently settled by the visible text.
Support eventually said the locksmith reimbursement to the guest had been processed. I asked the question that still mattered to my accounts: had anything been taken from me, and was anything due to me? The answer reported £285.12 in trip earnings sent to my payout method. It did not provide a complete final allocation of the locksmith cost.
An access incident can leave several different financial questions hidden under one reassuring closing message. Keep the key handover and the actual cost evidence, then request an itemised account of guest reimbursement, host deductions and host earnings. Do not turn an insurance referral into assumed coverage.
A heating complaint led to an early departure. Support described refunding the unused nights, leaving the guest paying for only the night spent. I then raised a separate practical cost: preparing the apartment again. I asked for £45 for cleaning alongside the night’s payment.
The first answer pointed out that my listing did not have a cleaning fee. I acknowledged that and explained that I still had to clean the home before another guest could use it. Support said it would consult the team, then wrote that £45 compensation had been processed and would be added to my payout.
That was a specific written response to the extra cost, not a reversal of the unused-night refund. It did not confirm that the calendar had reopened.
If I had stopped at the first answer, the preparation cost could have remained unaddressed. Explain the work and the amount separately from the nightly rate and the booking’s displayed fees. Ask for a decision on the actual cost. This outcome does not make every unlisted cleaning charge payable; it shows why a precise, practical explanation matters.
Support asked whether I agreed to a guest’s €215 refund request. I did not. I asked for the earlier problems and correspondence to be read and made my objection clear.
My response also questioned the guest’s intentions. That was my view, not a finding established by the case. Support later acknowledged that I had addressed the reported issue promptly, but still announced a £33 refund for the affected night.
The amount requested and the amount decided were different, and they were written in different currencies. I cannot describe the outcome as the whole request being approved, or as my refusal preventing any refund. The record shows a limited adjustment decision, not a checked bank transaction.
A host needs to be ready for an answer that is neither a complete win nor a complete loss. Preserve the messages and the remedial work, ask how the affected period and amount were assessed, and read the actual decision before closing the file. A clear objection records your position; it does not itself guarantee a veto.
Support said it had accepted the guest’s cleanliness evidence and asked whether I could resolve the issue. I disagreed with the complaint and explained that I had prepared the home myself. That disagreement did not stop me offering a practical response.
I said a cleaner could attend, then arranged a visit for the next morning and said I would be there too. The following day support reported that the guests had confirmed I came to the property and it had been cleaned.
That follow-up matters. It moves the record beyond a promise to send someone and into a reported completed action. It does not establish a refund decision, an admission of fault or an independently inspected standard of cleanliness.
If the argument had replaced the response, the reported problem could have continued throughout the stay. A host can dispute an allegation and still act to reduce disruption. Put the proposed visit in writing, coordinate it appropriately, then seek confirmation of what was actually done. Keep the service response separate from any later financial decision.
After checkout, I reported heavily soiled or damaged textiles. I described separating affected items and cleaning the home so it could be ready for the next stay, then asked for compensation.
Support transferred the conversation and explained how to make a Resolution Center request. That was useful routing, but the visible exchange does not show the request being completed or assessed. There is no accepted damage amount or payment decision to add to the story.
The pressure to turn a home around can create an evidence gap: the work gets done, but the original condition and the cost of putting it right become harder to show. The record demonstrates the work I said I had done, not an independent inspection of every item.
Before washing, separating or replacing affected textiles, document their condition and identify what needs cleaning versus replacement. Keep a factual account of the work and any real cost. Then follow the claim through to an actual decision. Restoring the home and obtaining reimbursement are separate jobs.
At the booker’s request, I had handed the keys to another person. The booker then became unreachable. I told support that I did not know with certainty who was staying and asked for help contacting the guest. Silence alone did not tell me what had happened.
Support transferred the case, asked me to keep using Airbnb messages and said it would contact the guest too. Later it reported speaking with the guest, who said they were now replying to me. The explanation passed back was a connection problem. I thanked support.
That was a communication update, not independent verification of everybody in the home. The visible record does not establish that the property was being misused or that an identity check had been completed.
A handover without a reliable communication plan can leave the host unsure how to coordinate the stay. Before a third-party collection, clarify the arrangement through the booking conversation and make sure the booked guest remains reachable. If contact breaks down, record the attempts and ask support to help; do not turn uncertainty into a claim of wrongdoing.
I had not handed over the keys. While I was asking Airbnb to clarify changing guest arrangements, a senior support message said the guest remained at the property. That sentence changed the question completely: was this an inaccurate note, or did support know something about access that I did not?
I challenged the precise statement. I explained that I had authorised no entry, asked what information supported the occupancy claim, and requested a correction. When the first reply apologised for a system glitch, I asked again for an explicit answer about whether anyone had entered.
Support then confirmed that the guest had not entered, attributed the confusion to a system glitch and typing error, and said the details were documented. That was a correction to an important case fact. It was not a specific payout approval.
An inaccurate occupancy statement could send a safety discussion in the wrong direction. Read the factual assumptions in a support reply as carefully as its conclusion. If one is wrong, name it and ask for the corrected position in writing.
I challenged a guest review after a dispute about the stay. I believed it conflicted with the messages exchanged and asked Airbnb to examine that history. The first decision found no policy violation and left the review in place. I reopened the request instead of treating that first reply as the end.
The later answer said the guest review had been removed because it did not contain enough relevant information. That was the reason given. It did not establish that every allegation I had made about the guest was true, or that a retaliatory motive had been proved.
There was another side to the same stay. Airbnb later removed the review I had written, citing personal information about another person. I argued that other hosts needed to know about the conduct I had reported. Support maintained the removal; my review was not restored in the visible exchange.
The risk runs in both directions: an unsupported challenge can leave a disputed review standing, while an over-detailed warning can lose its place altogether. Defend your position with relevant records, and keep private information out of the public account. A successful appeal on one review does not settle the other.
I use earnings reports to understand each property, so a reporting error matters even when the total payout can be explained. In one support conversation, I initially sent the wrong screenshot. I acknowledged that mistake, found the CSV I meant, and identified the row I was questioning.
Support then acknowledged an error in the summary report and said it had been reported for correction. I explained that I relied on these reports for my accounts and would now have to check the figures manually. The record does not show a completed technical fix.
In a separate reporting conversation, the answer kept returning to a combined payout for several reservations. I kept explaining that my question concerned the report for one property, not the arithmetic of the batch payment. By the end I wrote that it seemed fixed, but there is no independently checked replacement report in the record.
Left unchallenged, a report that answers the wrong question could distort a property’s apparent performance. Be precise about the filter, the row and the expected result. Correct your own evidence when necessary, and distinguish a plausible explanation from a verified repair.
The message code arrived, but entering it and my PIN sent me back to the beginning. I could not open my earnings in the app, and I needed to deal with incoming payment routing. Repeating the same loop could have left that work waiting.
I described exactly where the process failed and told support I was using the app. The representative suggested opening the desktop version in a browser. I tried it and reported that the browser worked while the app still did not.
That was a useful, confirmed workaround. It was not proof that the app had been repaired, and the conversation does not confirm that I completed the intended payment changes.
A practical support result can be narrower than a complete fix. Identify the failing step, test an alternative access route, and record what actually worked. That gives you a way to keep operating without confusing restored access with a resolved underlying fault.
I wanted to update a review I had written. The support flow told me editing was no longer available in that situation and offered removal instead. That distinction mattered: the same screen warned that removal would not let me publish it again or write another review for that reservation.
The visible flow then displayed confirmation that the review had been removed, and I selected that I had received the help I needed. There is an actual action confirmation here, not just a menu offering an action.
This concerned my own review of a guest. It was not an appeal against a review the guest had written about me. Nothing in this record confirms a change to a review received from the guest.
Before accepting an alternative button, check the consequence attached to it. Otherwise a request to improve your wording could end with the whole contribution removed. Keep separate records of the object you are changing and the action the interface actually confirms.
I could no longer find the short-stay discounts I had used before. On the new listing, I could see a weekly option instead. If I assumed the pricing setup was complete, the offer I intended might never reach a guest.
Support discussed custom promotions, but that did not answer my exact question about discounts tied to the number of nights. I reopened the conversation and asked whether access to professional hosting tools was the difference.
The later reply gave a general calendar route. The visible exchange does not contain a clear answer to that eligibility question or confirmation that the intended discount worked.
Two features can both reduce a price without doing the same job. Name the feature, describe the result you want and ask the representative to confirm that exact behaviour. A link to another pricing tool is useful only if it solves the question you actually raised.
I could not find an available property in search, and support sent back evidence that it appeared on the map. Then I noticed the search was for a different month. I restated the period I had asked about rather than accepting a reassuring screenshot of a different search.
The representative acknowledged the mismatch and later attributed the restriction to a remaining-night limit on the account. That was the explanation in the exchange. The exchange did not include an independently checked night ledger.
In another visibility conversation involving several properties, I again challenged the dates used in support’s search. The reply moved towards promotions and availability advice, but the record does not show a matching search for my intended dates or bookings arriving afterwards.
Had I accepted either answer without checking the parameters, I could have acted on the wrong diagnosis. A visibility test needs the same property, dates, guest count and filters. Being found somewhere in search is narrower than being bookable for the stay you are trying to sell.
I wanted to adjust the price for an empty night, but the calendar would not let me. Support first said the configured check-in time had already passed, so editing was no longer possible.
I challenged that explanation with a concrete example: a guest had previously booked and arrived much later. I referred support to the reservation and screenshots, explained that I was trying to avoid leaving the property empty, and asked to continue in writing.
The case was transferred. The later reply acknowledged a technical issue affecting calendar changes and said work was under way. It did not confirm that I could make the change, and the separate search-visibility concern I had raised was not shown as repaired.
Without challenging the explanation, I might have mistaken a fault for a normal limitation and stopped trying to manage that night. A specific counterexample can be more useful than a broad complaint. It can improve the diagnosis even when it does not produce a verified fix.
A guest praised my welcome but criticised the apartment’s size, lack of a living area and cramped showers. I believed the description and photographs had already made those features clear, and I disputed the low rating.
I asked for removal, then appealed after the first refusal. I explained the listing details again and why I thought the overall impression was misleading. Support reviewed the request twice and maintained that it had not identified a policy violation.
The review stayed. A professional public response was suggested, but there is no record here that I posted one. The decision also did not determine that my account of the listing was false; it was a refusal to remove this review.
A host can face a reputational risk without having a removable review. The useful distinction is between something you consider unfair and a specific ground for removal. Preserve the description and photographs, make the focused appeal, and do not build your next business decision on an assumed reversal.
A prospective guest expected to arrive, but neither of us had a clear answer about whether the reservation was confirmed. The dates appeared blocked. I told support that an earlier explanation did not match what I could see and asked it to check the actual status.
The representative said the reservation had failed because the guest had not completed the required information. I then saw the blocked dates become empty and reported that change. Support explained that the temporary hold had ended when the reservation failed.
That is a stronger result than an assurance alone: I described the changed calendar myself. It still does not show that the guest stayed or that a payment was made.
Had I treated the blocked dates as a completed booking, I could have planned access or availability around a reservation that did not exist in confirmed form. Ask separately about the booking status, the calendar hold and the payment. One screen should not be made to answer all three questions.
I was trying to contact a guest, but a system warning made it unclear whether my messages were getting through. I asked support whether I was being blocked and whether the guest had seen what I sent.
General instructions on opening the inbox did not answer that question, so I asked for a person and described the warning again. The representative acknowledged a system issue and said the technical team was working on it.
The exchange ended without a successful sending test or confirmation that the guest had read the messages. Acknowledging the fault was useful, but it did not prove communication had resumed.
Without checking, I could have mistaken a delivery problem for an unresponsive guest and allowed an avoidable misunderstanding to grow. Describe the warning and the action that triggers it. Keep the guest’s intent separate from a technical symptom until you have evidence connecting them.
I believed I had done enough to earn Superhost status and asked for it to be added without waiting for another assessment. The first reply pointed to general performance information. I wanted my actual progress examined, not another list of links.
I requested an interim assessment and continued the discussion through several representatives. Support referred to assessment timing and eligibility figures, but ultimately said it could not add the badge. The written outcome remained a refusal.
Without a clear statement of what was missing, I could have kept planning around a badge I had not been awarded. The exchange does not establish that persistence produced an early award.
A host should be able to ask how a decision was reached. Ask for the relevant assessment and the unmet criterion in writing, and separate that factual question from a request for an exception. Neither effort nor repeated escalation is proof that a particular status has been approved.
I told support that reservations were not coming despite a large price reduction. After asking which listing I meant, a representative told me to find a deactivation email and republish the home. I replied that I could see my listing; the problem was that bookings were not arriving.
The later answer said the listing was in good standing and cited search and page-view figures. It suggested updating photographs. The exchange moved from an account-status explanation to performance advice without showing that new reservations followed.
Had I acted on the first diagnosis without checking it, I could have spent time trying to repair the wrong thing. On the other hand, seeing my listing myself did not establish how well it was reaching or converting potential guests.
Clarify the layer of the problem: publication status, search exposure, page views or bookings. Ask what evidence supports each explanation. A support reply that changes diagnosis should help you identify the next question, not become proof that the commercial problem has disappeared.
I asked how to host in the name of a company and requested a simple explanation. The support flow offered professional hosting tools. I asked for a person because the company question was more specific than access to another set of controls.
After a call, the written response again directed me to the professional-tools article. It did not confirm that a business identity had been changed or that the listing was now registered to the company.
If I had treated that link as confirmation of the requested change, my account records and my assumptions could have parted company. The visible result was guidance to a tool, not a completed company transition.
State separately what you want changed: the available tools, the account’s business details or the listing’s recorded operator. Ask which of those the reply actually covers. Similar language is not enough to establish that the administrative task has been done.
I wanted my hosting payments sent to a company account and asked about the connection to the company and invoices. Support explained payout methods and routing, but the same reply also moved into marking a reservation as a business trip and dealing with a travel receipt.
Those are different sides of the platform. Advice about a traveller’s booking did not establish how my hosting business should be recorded. I later said that the business payout method I had added was still pending and asked whether it could be approved.
The available record ends with that message shown as sending. It does not confirm the final delivery of the question, approval of the method or receipt of money.
Had I accepted the whole response as one complete solution, I could have assumed that an unresolved payout setup was ready. Keep the host task, the guest-travel task and the payout-method status separate. A detailed answer can contain useful information and still leave your actual request unfinished.
I had already reduced the nightly price and still was not getting bookings. I asked why the listing was not being highlighted. General suggestions about photographs did not settle my concern, so I provided the listing and asked to keep the discussion in writing.
Support then said the address information was incomplete and asked me to confirm the location. I supplied the details it requested. Later messages asked for further confirmation, while the final recap said the listing was receiving views and suggested market pricing and nearby attractions.
There is no completed location correction or subsequent booking result in the visible record. Nor did the exchange prove that the platform had deliberately withheld exposure.
Had I kept cutting the price without separating location accuracy from demand, I could have changed the offer without understanding the problem. Ask what is being tested and what has actually changed. Price, map placement, page views and bookings are related, but they are not interchangeable evidence.
I created a new listing, then could not find it in search or on the map. That gap mattered: a page I could manage was not necessarily a page I had confirmed a prospective guest could discover.
I raised the specific problem with support. The representative explained that new listings could take time to appear in search and gave me a waiting-period explanation. I selected that I was finished with the conversation.
The record does not contain a later search test proving that the listing appeared. Closing the chat was my response to the guidance, not evidence that visibility had been restored.
Without a separate guest-view check, I could have mistaken publication for a completed launch. Keep evidence of the publication state and test discoverability separately. Use any waiting period support gives as a case-specific explanation, then verify the result rather than assuming that the clock alone has solved it.
I wanted to offer a new Airbnb Experience, but the creation route appeared closed. I asked whether I could do it through my Superhost account. The automated response about editing a profile did not address that question, so I requested a person.
After several handovers, the written explanation finally identified the obstacle: at that time, Airbnb had paused new Experience submissions. Support said an existing hosting account or badge did not provide a way around that pause.
No Experience was created or approved in the visible exchange. The answer described the product situation then; it is not a statement about what applications are available now.
If I had kept treating the blocked route as a profile error, I could have spent more time trying settings that could not remove the stated obstacle. Before investing further work in a new platform offering, establish whether the entry route is open and what kind of approval is actually possible. An existing badge is not itself confirmation of access to a different product.
Discuss which checks, records and handover arrangements make sense for your property before taking bookings.
Discuss your property