> For the complete documentation index, see [llms.txt](https://docs-old.telematicssdk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-old.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/how-it-works.md).

# Get started

**The service consists of 4 standalone services:**

| Item                                               | Link                                                                                                               | Description                                       |
| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------- |
| Profiles                                           | [Profiles](https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/authorization) | Auth service & customer's data                    |
| FNOL                                               | [Claims](/platform-features/fnol-inspections-and-damage-recognition/claims-service.md)                             | API to create a claim profile                     |
| Vehicle Inspections                                | [Screens](/platform-features/fnol-inspections-and-damage-recognition/screens.md)                                   | API to link a bunch of photos to a claim          |
| <p>Photo processing &</p><p>Damage recognition</p> | [Quotes](/platform-features/fnol-inspections-and-damage-recognition/quotes.md)                                     | API to process bunch of photos and detect damages |

## Dependencies

There are several main objects in the process:

| Object      | Description                                                                                                                                                                                                                                                                                           |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| DeviceToken | <p>Device token that is used in Telematics SDK or can be received via User management API.</p><p><a href="https://docs.telematicssdk.com/platform-features/back-end-as-a-service"><https://docs.telematicssdk.com/platform-features/back-end-as-a-service></a></p>                                    |
| Token       | <p>Authorization Token that can be received via Auth Service.</p><p><a href="https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/authorization"><https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/authorization></a></p> |
| CarToken    | <p>Car service has to be used to create a vehicle and/or get vehicle details, including Make, Model and other fields.</p><p><a href="https://docs.telematicssdk.com/platform-features/car-service"><https://docs.telematicssdk.com/platform-features/car-service></a></p>                             |
| Claim\_ID   | Claim ID will be provided when a claim is created.                                                                                                                                                                                                                                                    |
| Screen\_ID  | This is a bunch of photos (vehicle photos).                                                                                                                                                                                                                                                           |
| Quote\_ID   | This is a system object that confirms that we've received a screen for processing and damage recognition and it is currently in processing.                                                                                                                                                           |
| Damage\_ID  | This is a bunch of processed photos with recognised damages.                                                                                                                                                                                                                                          |

![](/files/-MKGbLquUyx4Ye5P0kzp)

## API Usage Scenario

{% hint style="warning" %}
**Note:** FNOL, Inspections and Damage Recognition services are closely integrated with [Vehicle management Service](/platform-features/car-service.md).\
You have to create a vehicle first to register a claim.
{% endhint %}

1. [Authorize](https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/authorization) in Service. You need a user "*deviceToken*". Get it via [registration](https://docs.telematicssdk.com/platform-features/back-end-as-a-service/registration), [refresh](https://docs.telematicssdk.com/project-setup/manage-service/user-registration#refresh-token) or via [search](https://docs.telematicssdk.com/platform-features/back-end-as-a-service/management).
2. [Create a claim](https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/claims-service#create-a-claim). You need a [*vehicleToken, Make and model*](https://docs.telematicssdk.com/platform-features/car-service/vehicles#get-a-list-of-users-vehicles). A new claim with a **Draft** status will be created. You need to save "*claim\_id*".
3. [Create a screen](https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/screens#create-a-screen) (a bunch of images). You need a "*claim\_id*". You can create only one screen per each claim. You need to save "*screen\_id*".
4. [Change claim status](https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/claims-service#update-claims-state) according to the [**Statuses workflow scheme**](https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/how-it-works#statuses).
5. In **Draft**, **Processing** and **Pending** statuses you can [update the claim](https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/claims-service#update-a-claim).
6. In **Draft**, **Processing** and **Pending** statuses you can [update the screen](https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/screens#update-a-screen).\
   Validations:\
   Screen attribute **CanEdit == true**.
7. [Create quote](https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/quotes#create-a-quote). You need a "*screen\_id*".\
   Validations:\
   **Claim state == 'approved'**\
   Screen attribute **CanQuotation == 'true'**
8. Wait for Damage Report processing (**quote\_processing** state set up automatically). When Damage Report is created (after 30-60sec), the claim will get state **Executed** and you can [get Damage Report](https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/quotes#show-damage-reports). You need "*claim\_id*" and "*screen\_id*".

{% content-ref url="/pages/-MKB5h80JebYNZ9nuqhb" %}
[Broken mention](broken://pages/-MKB5h80JebYNZ9nuqhb)
{% endcontent-ref %}

## Overall workflow and statuses (states)

![](/files/-MKp44K4OqKcUO34pQnT)

## Statuses

![](/files/-MK6CkmUlMspIsgeQk-U)

1. All new claims are created by customers with a **DRAFT** status.
2. When your manager starts to work with a new claim, he can transfer the claim to **PROCESSING** status.
3. If there is not enough details from a customer, a **PENDING** status can be used.
4. **HOLD** and **REJECTED** statuses can be used by your manager if the claim is not allowed for further process.
5. If the claim is appropriate for further damage recognition process, status **APPROVED** can be used.
6. In **QUOTE** status the photos processing for automatic damage recognition starts.
7. When the damage recognition process finishes, status **EXECUTED** is used.

## Case study - [Zenroad app](https://www.raxeltelematics.com/telematics-app/)

#### FNOL

![Example of workflow](/files/-MKGf2lKupJk9IIDRtR4)

#### Vehicle inspection

![Example of workflow](/files/-MKGh4pwe0RQeEarc4oR)

#### Photo processing and damage recognition

![Original photo and result of processing](/files/-MKGjTshyqC-sHuPCOdY)

## Photo processing

To proceed with photo processing it is required to provide at least one photo from a mandatory type of photo. The full list of screens and guide are available here: <https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/screens/vehicle-photos-dictionary>

| Type of photo                                                                                                                                                                                                                        | Flag                                            |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------- |
| <ul><li>Front</li><li>Back</li><li>Left front wing</li><li>Left front door</li><li>Left rear door</li><li>Left rear wing</li><li>Right rear wing</li><li>Right rear door</li><li>Right front door</li><li>Right front wing</li></ul> | Mandatory. At least one photo must be provided. |
| <ul><li>Front left diagonal</li><li>Front right diagonal</li><li>Back left diagonal</li><li>Back right diagonal</li><li>Left</li><li>Right</li><li>Windshield</li><li>Dashboard</li></ul>                                            | Not mandatory.                                  |


---

# 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-old.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/how-it-works.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.
