/
create and process future event

create and process future event

Rules built within Alterian Journey Orchestration are generally designed to react in near realtime. When the rules are used on websites, within apps or in Point of Sale environments getting a rapid CX decision back is paramount to providing the best experience for those customers interacting with the Rules.

In some scenarios it’s important to give the customer time before providing the action. It may be a immediate interaction would distract the user from their current journey or you may need to provide the customer time to think about what they have experienced before they can make use of the action.

Examples where this is commonly used are interaction satisfaction requests or abandon basket emails.

This delay of an action is possible in Alterian CX by using the create future event Public Template or the the create and process future event Public Template.

Obviously the delay created by this Public Template makes this much more appropriate for channels that are not time sensitive, Email, SMS app push etc rather than a banner advert. You may not be able to ascertain whether the customer is still on the web and available to see it.

The create future event Public Template on its own simply creates a trigger for an action to occur at a specified time in the future. The process future event Public Template is needed to read this trigger and provides the mechanism to add actions to it.

In many use cases you only want to pick out the “latest” event created even if you created lots of them.

For example when creating an abandoned basket email you may trigger a Create Future event each time an item is added to the basket. However you only send the single email 30 mins after the last item is added and the basket is not purchased.

To make this process easier simply pull in the is latest future event public template. This will simply tell you whether this event is the latest one allowing you to choose the next action.

Input Data

create and process future event is a Rule Start tile

Field

Description

Example

Field

Description

Example

 

 

 

Field Mapping

 

Configuration

 

Field

Description

Example

Field

Description

Example

tablename

The name of the table to stoer the future event records in

FutureEvent

timeOffset

What timeperiod should pass before this specific event is triggered. this is set in seconds.

60, 120

Output Fields

No fields are created by this Template. All fields are passed through.

Field

Description

Example

Field

Description

Example

 

 

 

Related content