> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/guest-experience/guest-journey/about-protection.md).

# About protection

This page explains why a damage waiver can protect you better than a deposit, and how to choose a protection level.

## How protection works

A large refundable deposit puts guests off: a family worried that a child might mark a wall would rather pay €40 for a 4-night stay than risk a €1,000 hold on their card. A damage waiver gives them that choice. The guest pays a small fee, accidental damage is waived, and you earn on every waiver sold while you stay protected.

Behind the scenes, Truvi, the insurance partner, checks each guest with the details of the check-in form. The check usually resolves in moments and approves the vast majority of guests. There is no extra charge for the check of an approved guest, because you already pay Truvi for the insurance. Only a rejected guest costs a small administration fee. Rejections are rare, about 0.001% of guests.

## Choosing a protection level

Most managers choose **Basic protection**. They replace small items, such as a plate or a few forks, themselves instead of filing small claims, and they earn more per night. **Full protection** costs more per night but covers damage from the first euro. **Self Insured** suits large portfolios that are willing to carry the risk for a higher margin.

The price of the waiver decides whether guests choose it. If the waiver fee feels close to the deposit, guests choose the deposit. A modest fee per night, around €10, is a common sweet spot: charge €10 per night, and about €5 per night stays as profit after the premium.

The names changed in July 2026: **Full protection** was *Per Night*, and **Basic protection** was *Per Night (Excess)*. The new names match what guests see.

## Always protect

**Always protect** turns the waiver from a choice into a rule. Every reservation of the journey is insured, also when the guest skips the waiver or pays a deposit, and you pay the premium on every booking. Managers use it in two ways:

* **Guaranteed coverage:** every booking is insured, for example in busy periods or in buildings with a higher risk.
* **Always charge the guest:** a damage waiver fee on every booking, like a cleaning fee. The guest pays it on every stay, so you are protected and earn on every reservation.

## Why ID verification comes last

Guests settle protection, fees and extras before they are asked for a document. Fewer guests stop halfway through verification, and fewer payments stay unfinished.

## Keep the journey short

Shorter journeys get better completion rates. If a field does not drive a decision, a task or a legal requirement, leave it out.

## Related

* [Guest journey](https://docs.guestway.io/guest-experience/guest-journey.md)
* [How to set up protection](https://docs.guestway.io/guest-experience/guest-journey/how-to-set-up-protection.md)
* [How to file a damage claim](https://docs.guestway.io/guest-experience/guest-journey/how-to-file-a-damage-claim.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guestway.io/guest-experience/guest-journey/about-protection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
