Next Best Action

What is it?

A web based API for Next Best Action Platforms. Its follows the purest form of Next Best Action where each proposition is scored and then ranked against each other. The Highest ranked proposition(s) is presented.

It enables the selection and presentation of more contextual and relevant propositions to existing or recognisable users

In the example above a customer can be presented with 3 insightful , eligible and relevant propositions. The channel can only present one. Which one should it be? The "Over drawn account warning" proposition would be presented

Features

• Simple interface

• Highly configurable

• Interaction history

• Journey based customer interaction

• REST / JSONP / COMETD interface

Simple interface

Uses the REST or JSONP interface for simple integration.

How easy is it to execute JXS BRE ?

It’s as simple as this,

http://localhost:8080/awasr/bre/getdata?userid=nick&age=40&breuserid=aetuk&channel=web&brecontext=firstpage

This line is calling the service with 2 parameters, userid and age with values of nick and 40 respectively.

These parameters are not fixed, they can be anything – so as long as its is HTTP request Call compatible.

its is schema-less. It is up to the rules developer to ensure that the input values are put to the desired use

Mandatory parameters

There are a number of mandatory parameters shown in the above example

breuserid

The user id of the BRE user

channel

Channel used to invoke the service (Currently web and mobile)

brecontext

Context used to invoke the service

Extendable

Extendable JXS configuration.

Interaction History

• Impressions and responses are captured in the same table, called the interaction table.

• This table is accessed on every invocation to the BRE service and returns a summarised overview of the interaction - its properties will be touched on within this and other sections.

Synchronous interface

The interface is synchronous – a call to the service will return a result instantly. An asynchronous Web Socket version is in the works

Response / Response format

Required REST Request format

https://localhost:8443/awasr/bre/getdata?userid=nick&age=40&operation=response&propid=2&breuserid=aetuk&channel=web&brecontext=firstpage

'operation = response'

These keywords lets the engine know that we are dealing with a response

'propid=?'

The proposition id of the response which is being captured

https://localhost:8443/awasr/bre/getdata?userid=nick&age=40&operation=response&propid=2&breuserid=aetuk&channel=web&EventId=books&brecontext=firstpage

Event capture

Responses can be seen as events which can be invoked when a customer performs an action on a given channel. Currently these actions are assumed to be 'clicks' but there is nothing stopping the system integrator from capturing other event types.

Request format

https://localhost:8443/awasr/bre/getdata?userid=nick&age=40&breuserid=aetuk&channel=web&brecontext=firstpage

Important note : To capture a response for a given proposition, its rules will still need to be true.

For example, if EventId="books" on request then EventId="books" on response.

Using the initial example the EventId=books check has not been included, as have the other criteria (age, etc). If there is no response data returned - this means the response has not been captured

POST Request

https://localhost:8443/awasr/bre/postdata

POST JSONP Request

https://localhost:8443/awasr/bre/postdatajsonp