Reminder Process

General

The collectAI reminder process allows you to model your communication strategy. You can organize various strategies within dedicated workflows. Each workflow is usually tailored for a dedicated target group or business line, defining a set of action steps to execute. An action step can be anything you would like to happen, like sending an e-mail, etc. You can easily A/B test the performance of each workflow with the collectAI Reporting facilities.

In terms of integration the collectAI reminder process can sent you webhooks in real time whenever an action has been executed. This data can also be pulled from our API.

Workflow assignment

A workflow starts with a new claim being created in the collectAI platform. The claim gets then assigned to a workflow of your choice. By default, there is automatic assignment to a workflow, if any assignment rules are defined. Alternatively, it is possible to use the collectAI Assignment API to assign a claim to a workflow of your choice. Once a claim gets assigned, either the upload date or the claim's due date will automatically determine the right starting date to start the process.

Assignment rules allow claims to be assigned to a workflow based on various claim properties, such as the customer's age or year of birth, country, presence of contact information, or custom claim fields.

Process life cycle

At any time, you can intervene the reminder process for a given claim. For example, you can pause and resume a claim, or simply archive its execution completely. Whenever a full payment of a claim has been confirmed, the reminder process ends and any further execution of actions in the workflow is prohibited. If the process ends without any successful collection, the claim will be archived and deleted according to your data retention requirements.