Message Flows

Message Flows

Transsend templates allow messages to be forwarded on to other Mobile accounts using a special AMS route.

Meta and Default Data Requirement

A Meta data and Default Data element is required for this to work as expected.
We recommend using something simple like status in the example below.

This will be used on the routing to control which route fires on send and will be updated as the route fires.

Controlling the route flow

Inside the route example we have 2 routes. One to the Other User and one to theFinal Destination.

The route can be setup as normal in the Summary, but ensure that Include Shared Data is ticked.

A condition must be added for each Route, in the case of the "To other user" route we need to select: "Perform this route only when all the following rules are true"
Then enter the Meta Data name in the first field, is in the second field, string in the third and the current default status in the final field.

This will ensure the route only fires when the Meta Data field "Status" is at its Default Data value of "pending".

On the Final Destination route you need to ensure the condition as follows

A new Route Endpoint of the type AMS needs to be added to allow the message to be forwarded.

Route Endpoint

Route Endpoint should be setup as below, ensure that a valid Mobile User Id is in the To Field, Copy Message is checked and the status data field (or the field you have chosen to use) is updated away from pending.

You will note the change in the status field is done in JSON, we are looking at how best to make this an option field attached to this endpoint in the future.
Format is {"Meta-Data-Field": "Status-Updated-To"}