> For the complete documentation index, see [llms.txt](https://docs.loopit.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.loopit.co/getting-started/welcome-to-loopit-2.0/loopit-damage-cover-product-overview-australia-only/how-to-lodge-a-claim.md).

# How to lodge a Claim

If you need to lodge a claim under your **Damage Cover** product, follow the steps below to ensure a smooth and timely process.

{% stepper %}
{% step %}

### Step 1: Access the Claims Portal

Once your annual **Damage Cover** fee has been paid, we’ll provide you with access to the online Claims Portal.

To request access, please email **<support@loopit.co>** and include:

* Your **Business Name**
* **Primary Contact Details** (name, email, phone number)
  {% endstep %}

{% step %}

### Step 2: Lodge Your Claim Online

Once you have portal access:

1. Log in to the **Damage Cover Claims Portal**.
2. Complete the **Claim Lodgement Form**.
3. Upload any relevant supporting documents, such as:
   * Photos of the damage
   * Police reports
   * Driver licence or details
   * Repair quotes or invoices
     {% endstep %}

{% step %}

### Step 3: Alternate Method (If Portal Access Is Unavailable)

If you’re unable to access the portal or it's temporarily unavailable, you can still lodge your claim by emailing **<support@loopit.co>**.

Please include the following in your email:

* **Business Name**
* **Contact Details**
* **Vehicle Information** (e.g. registration number, make/model)
* **Incident Summary**
* **Date, Time, and Location of Incident**
* Any **supporting documents** (attachments)
  {% endstep %}
  {% endstepper %}

{% hint style="info" %}
For any questions about the claims process, please reach out to our support team via **<support@loopit.co>**.
{% endhint %}

## FAQ

<details>

<summary>When can I access the Damage Cover Claims Portal?</summary>

Access is granted once your annual Damage Cover fee has been paid. Please email **<support@loopit.co>** with your business name and contact details to request access.

</details>

<details>

<summary>What information do I need to provide when lodging a claim?</summary>

Whether through the portal or by email, please include:

* Business Name
* Contact Details
* Vehicle Details (e.g. registration, make/model)
* Summary of the Incident
* Date, Time and Location
* Any relevant supporting documents (e.g. photos, police report, driver details)

</details>

<details>

<summary>What file types can I upload to the portal?</summary>

You can upload common file formats such as PDF, JPG, PNG, DOCX, and XLSX.&#x20;

</details>

<details>

<summary>What if I can’t access the portal?</summary>

If you’re unable to access the portal, you can still submit your claim by emailing **<support@loopit.co>** with all required information and attachments.

</details>


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.loopit.co/getting-started/welcome-to-loopit-2.0/loopit-damage-cover-product-overview-australia-only/how-to-lodge-a-claim.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.