Privacy settings

Platform · Automation

As soon as a report comes in, the process starts.

One process for claim, breakdown, defect and violation.

The workflow asks partners by your rules and obtains approvals. Approvals are always decided by a person.

Request a demo Try out the process

Requirement: Automation booked.

Four case types

  • Claim
  • Breakdown add-on module
  • Defect add-on module
  • Violation

One process · Stations on this page

01The process

Your rules. One process. Try it out.

Set the rules and play a case through: report, ask partners, approve. The history builds up as you go, step by step.

Clamio orchestrates. Everyone pitches in.

Illustration to try out · not a product image

with Automation

Your rules

Case
Partner selection
Dispatch type
If no partner is found

See the result below

Stations

  1. Triggercurrent
  2. Partner selectionopen
  3. Answeropen
  4. Approvalopen
  5. Endopen

Now

Ready. Report a case, then the process starts.

    History

      No entry yet. The history records every step.

      Partners 1 to 3 are examples. The illustration does not show deadlines, amounts or names.

      02Trigger

      The report triggers the process.

      The conditions under which the process starts, such as damage type, severity or coverage type, determine which process fits.

      • Applies to claim, breakdown (add-on module), defect (add-on module) and violation.
      • The trigger is an event, for example “Claim reported”.
      • Drivers report via the app; you record cases in the portal.

      Starting by hand: for claims onlyWorkflows start automatically. For claims, admins can also start or cancel a process by hand, traceably logged.

      From the interface

      Demo data

      Header of a process in Clamio: 4 steps, auto-start, trigger “Schaden gemeldet” (claim reported), status active, with a condition on the damage type below.
      A process with the trigger “Schaden gemeldet” (claim reported) and auto-start. The condition is shown below.

      03Partner selection

      Fixed or preferred. At once, one after another or at the same time.

      You choose partners as fixed or preferred partners. Orders go to one partner at once, or requests go out one after another or at the same time.

      Which partners are asked

      • Fixed partner

        The step always goes to the same partner.

      • Preferred partners

        The step asks the partners you have marked as preferred.

      Dispatch type: exactly one per step

      • Order at once

        The order goes directly to the first matching partner, without a request round. Platform partners accept or decline it; your own service providers take it on directly.

      • Ask one after another

        If one declines, the next is asked immediately, otherwise once the waiting time has elapsed.

      • Ask at the same time

        As soon as one partner accepts, the request is settled for the others. If one declines, the request to the others stays open.

      For “at once” you define in the template how things continue after a decline. Automatic moving on to the next partner exists for “one after another” and “at the same time”.

      In the editor the step is called “Order a provider”, the choice within it “Partner selection”.

      Your own service providers without an account take part via a protected order link.

      04Response deadline

      Every request has a response deadline.

      You set the response deadline per partner tier. If one declines or does not answer within the deadline, the next is asked.

      This applies to “one after another” and “at the same time”. For “at once” you define in the template how things continue after a decline.

      If no partner is found

      If no partner is found: create a manual intervention or create an order without partner. Which applies, you define in the process.

      Illustration · Example for the dispatch type “one after another”

      1. Partner 1declines
      2. Partner 2does not answer within the deadline
      3. Partner 3declines
      4. No partner foundCreate manual intervention or Create order without partner
      Partners 1 to 3 are examples.

      05Approvals

      Approvals are decided by a person.

      If a step needs an approval, the process waits until the decision is made.

      • The “Approvals” page collects requests from running workflows that need your decision.
      • Approvals concern, among other things, cost estimates, invoices, repairs and settlement decisions. Depending on the step, the fleet, the insurer, the underwriting agent (MGA) or, for a claim, a commissioned partner decides.
      • Optionally the four-eyes principle for cost estimates and invoices from an amount you set.
      • A workflow never decides on coverage or settlement itself.

      Illustration · Approval in the process

      1. Approval requestedThe process waits until the decision is made.
      2. One person decidesApprove or reject.
      3. A second person confirmsOptionally, for cost estimates and invoices from an amount you set.
      4. The process continues
      Dashed: only applies if you switch on the four-eyes principle.

      06Check run and test run

      Check and test first, then activate.

      The check run finds gaps, the test run plays the process through on a test claim – before go-live.

      • Processes are created as a graphical process chain: classify, commission partners, obtain approvals, inform those involved.
      • You can duplicate, archive, export and import templates. You adopt templates from Clamio as a starting point.
      • The “Workflow” tab in the claim file shows every step, every result and every waiting time.

      Illustration · From template to active process

      1. Create templateYour own template or one from Clamio.
      2. Check runFinds gaps.
      3. Test runPlays the process through on a test claim.
      4. ActivateFrom now on the process starts with the report.
      5. History in the fileEvery step, every result, every waiting time.
      Dashed: before go-live. Solid: the process is active.

      07Frequently asked questions

      Quick questions

      Requirement: Automation booked.Breakdown and defect are add-on modules.

      What happens if a partner does not answer?

      Every partner request has a response deadline. If one declines or does not answer within the deadline, the next is asked. If no partner is found, Clamio creates a manual intervention or an order without partner. This applies to “one after another” and “at the same time”. For “at once” you define in the template how things continue after a decline.

      Who decides on approvals?

      Always a person. Optionally the four-eyes principle for cost estimates and invoices from an amount you set.

      Does the workflow decide on the settlement?

      No. A workflow never decides on coverage or settlement itself. It obtains the approval and waits until the decision is made.

      What do we need to book for the workflow?

      The workflow requires Automation to be booked. It applies to claim, breakdown, defect and violation. Breakdown and defect are add-on modules.

      Keeps it rolling.

      In a demo we show you a process from report to closure.

      Request a demo

      Where does AI help in the process? See AI in the workflow