# Landing Page

Customers often need more additional information about your product protection program and available plans than you can convey at the point of sale or in marketing materials. When you set up a landing page on your website with comprehensive information about your product protection program, you can link to this page from various locations (e.g., PDP, checkout, marketing materials, email, etc.) to ensure your customers always have access to everything they need to know.

## Content

While the structure and design of the page are entirely up to you, the content should include the following points among others:

* **Program Description**: This should clearly present the details of the product protection program, e.g., what plans are offered, how to obtain them, what they cost, etc.
* **Customer Benefits**: This should explain why customers would benefit from the program. Possible points could include: low or no repair or replacement costs in case of damage, peace of mind, and extended product life.
* **Key Terms**: This should clearly outline all conditions affecting the program, such as coverage, cancellation period, and deductibles.
* **Claims Process**: This should describe how to report claims, what information needs to be provided, and how they are processed.

## Examples

Here are some examples of product protection pages created by some of our partners:

{% embed url="<https://www.globetrotter.de/service/globetrotter-produktschutz/>" fullWidth="false" %}

{% embed url="<https://www.abele-optik.de/unternehmen/service/brillenversicherung/>" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://resources.hellohakuna.com/best-practices-toolkit/landing-page.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.