Inbound SMS Support is now provided for inbound SMS to create an overall more robust SMS offering. An inbound SMS is receive when a consumer replies to a shortcode with a keyword. This may be simply to STOP messages and unsubscribe, but may also be in relation to more response based criteria. Action can be taken in a Custom Journey in relation to the received inbound response, e.g. trigger and email to confirm unsubscribe for SMS being successful. Inbound events are created and managed in the Data Exchange.
We have added a Wave Component to the Journey tools options, which enables sending bulk messages in waves. The waves can be calculated based on the number of contacts or the number of waves. You can also specify the interval between two waves. Every time a Wave is sent, the contacts for the next one is recalculated to take into account new contacts that may have been added in between. This functionality is supported in both Single Batch Journeys and Custom Journeys
We have added a Single Batch Component to allow Custom Journeys to be executed in bulk mode. Single Batch Journeys were already available through the Journey Wizard but only supported a single message to be sent out in bulk. Now users can create more complex Single Batch Journeys and add audience filters, perform database updates and more.
Custom Components are now available as two separate components within the Journey tools options. Custom Channel has been added to the Interaction tools, and Custom Component remains within Data tools. The latter supports Stored Procedures and Web Service Calls within the Journey.
Enhancements were made to Tasks to enable Tasks, Export and Imports to be run on a different scheduler when required, so that long running tasks do not impact other tasks. SQL Tasks can also now be designed using a drag and drop interface, in the same manner as exists for Batch Tasks. Validation is provided indicating missing links, names, etc.
Support for folders has now been extended beyond Content and Journeys now to support Lists. When folders are created for the segments of a specific list, these folders are only available for that specific list. Users can search for items is subfolders. Folders are returned in the search results and clicking takes you directly to the corresponding item. The Folder structure is available from the fly-out menu too. Movement of bulk assets to a folder is completed via the dashboard.
CRM messages are part of the CRM Integration and allow you to manage CRM records from within a Selligent journey. Depending on the CRM environment you are integrated with (e.g. Salesforce Sales Cloud, MS Dynamics CRM, Sugar CRM, etc.), different messages can be designed to update, create or delete an item in the CRM environment as a result of a journey event. CRM messages are available as a dedicated component in the journey but some configuration is required prior to their use.
Advanced export options have been added that allow you to define what happens when the target file to which you are exporting already exists, or if there is no data to export. You can now also export data in 1:N linked lists. When mapping the fields from the Selligent list to columns in the export file, you select the scope of the field and this can be the master list, 1:1 or support 1:N linked lists. relations with data export.
Other additions include providing details on the duration of an execution on the Data Exchange Dashboards for Tasks and Imports / Exports. When a user changes Lists after a mapping has been defined for an Import / Export, they will receive a warning that this will undo all settings defined for the mapping. Also, now when performing an export, users can use calculated fields by the means of expressions which can be manually entered, or selected from a personalized dialog.
AB Journey reports are now available from the journey report pages. On top of the standard journey information, they also provide details on the target audiences to which the different versions are sent and the criterion that is used to define the winning version. A pie chart as well as textual report is provided. Message and Campaign Analytic Tags are also included in the reporting, along with some minor changes to Transaction Journey reports, such as email activity details and Custom Journey Reports which now have the same interface and toolbar as the Custom Journey designer, with buttons to switch to the Properties and Design Mode.
The record count is now available not only on the global level but also on the nested sub-levels of the audience filter. Users can also now use grouping in nest 1:N levels and apply operators (AND/OR) to support advanced filtering, e.g. select all contacts with an order in the last 30 days where a Dress or Coat was included within the order. 1:1 linked data in nest 1:N level data is now available, which means users can use Profile Extensions on nested 1:N linked lists. This also now means when building constraints using interaction history in Journeys, this supports both Campaign journey interactions as well as Transactional Journeys.
Content, Lists, Journey, Data exchange and Home dashboards have been reorganized to reflect the new UI. One of the changes comprises the action buttons to be placed in the upper right corner of the dashboard. You have access to the Create button that takes you straight to the wizard. Or, select immediately the required type of element to create from the associated drop-down. Filter buttons for the dashboard are now displayed on the right-hand side and are presented as text.
The create folder option can be found on the new drop drown menu on the top right hand side. The current selected folder path is visible from the breadcrumb trail. In the Custom Journey section, the toolbar has been updated as well and looks like this. Action buttons are displayed in the upper right side. For AB-journeys, Single Batch Journeys and Recurring Batch Journeys, the properties of the journey are accessible through the left-side navigation. The action buttons (such as Save, Launch) are accessible from the upper right side of the toolbar. When editing lists, the different elements of the list are accessible through links in the upper left corner and no longer via steps in a wizard. When a specific list element has sub-elements, these are accessible from a left-side menu.
New capabilities have been added to the API Explorer.
Apps can now be filtered on organizations so that API calls only work for those organizations
The Facebook PageUID and AppUID can now also be used for Facebook Custom Audience matching.