Skip to main content

๐Ÿ“Š Statistical Reasons โ€” internal claim reasons for reporting

Jeppe Oestergaard Hansen avatar
Written by Jeppe Oestergaard Hansen
Updated over a month ago

Statistical Reasons let your team assign internal reasons to each claim, giving you structured insights into why claims happen โ€” without exposing anything to the customer.


What it is

  • Internal only: Never shown in the customer portal.

  • Global setting: Applies across all Markets (no per-market localization).

  • One per claim: You can select exactly one reason per claim.

  • Locked after review: Once you Complete Review, the reason cannot be changed.

  • Analytics-ready: Reported in Analytics โ†’ Claims โ†’ Claim Reason and included in CSV export.


Enable or disable

Go to Settings โ†’ Claims โ†’ Statistical Reasons
Toggle Enable/Disable to show or hide the field for staff during handling.


Create, edit, and delete reasons

  1. Open Settings โ†’ Claims โ†’ Statistical Reasons

  2. Click Add Reason, name it, then Add

  3. Use โ‹ฎโ‹ฎ to reorder (optional)

  4. Use โ€ฆ next to a reason to edit or delete

Naming tips

  • Keep it short and unambiguous (e.g., Product defect, Missing parts, Transit damage).

  • Use consistent language for comparable data over time.


How to select a reason while handling a claim

  1. Open the Claim Details page

  2. Locate Claim Reason (Only visible to staff)

  3. Select one reason from the dropdown

  4. Optionally add an Internal Note for context

  5. When you click Completed Review, the selection becomes locked


Analytics and export

  • Go to Analytics โ†’ Claims โ†’ Claim Reason (chart) to see distributions over time and by reason.

  • Use Export to CSV for further analysis (BI, spreadsheets, etc.).


FAQs

Is this visible to customers?
No โ€” itโ€™s internal only.

Can I select multiple reasons on a claim?
No โ€” exactly one.

Can I change the reason later?
Only until you mark the claim as Completed Review โ€” then itโ€™s locked.

Does it affect customer flow or the decision?
No โ€” itโ€™s purely for reporting.


Best practices

  • Start simple (3โ€“6 reasons) and iterate after 2โ€“4 weeks of data.

  • Make reasons mutually exclusive to avoid overlap.

  • Review top reasons monthly as part of your quality process.

Did this answer your question?