Introduction to Reactions

Reactions allow us to either do something simple as a reaction to a real-life event, or completely change the strategy and direction of a claim.

Let’s take the example that we use in sales calls:

A consumer gets an email, goes to the landing page and checks the instalment options. Then, our customer closes the browser. That triggers an event, and you can setup a reaction to it. Let’s say in this case you'd like to have a set of steps inserted into the main strategy that’s being executed for this claim. You would simply select 'insert path' and then proceed to choose a specific path.

The reaction would look like this:

Reaction Types

Main Types

Payment Providers	Change the payment providers available to the claim
Update Claim Content Template	Change the Landing Page’s content
insert Path	Inserts the selected path into the main journey being run by the claim
Switch Path	Completely REPLACES anything upcoming in the main journey
Create separate strategy	Creates a parallel execution track for the claim. This is handy to do things with a short delay. Not really intended to let things sit for days, where another event may throw this away.
Send Debtor SMS	Send an SMS to the debtor
Send Debtor Email	Send an Email to the debtor
Send Client Email	This sends an email to whatever emails the client puts in there. This is helpful is there is no deep integration and then the notifications can simply go to their inbox to process.
Delete Claim	This is then the trigger to anonymize data in the system for that claim. It should trigger cleanup actions in the various services.

Primarily Triage Usage

Recreate Claim	Should really only be relevant in the file integration case, but in the event that all the claims are ruined, then this allows them to be recreated in the main account domain, which triggers a re-setup in the other services.
Reassign Strategy	This will take a stuck claim and put it back into the strategy selected. Typically used when things were stopped on accident.
Reset Claim Lifecycle	The reporting is listening for things like the claims being stopped. So if it was stopped on accident, and you reassign it, to get the reporting correct (if desired) then this is issued to get the status and such corrected in the reporting domain.