imiconnect v5.6.0 release brings in multiple new features and enhancements to make your platform experience more secure and richer. Here’s a list of the key updates:

• Support for 10DLC (10 Digit Long Codes) numbers for application to person messaging in the US
• Support for MMS channel (limited to the US). Long code and TFN MMS is not supported in Canada
• Ability to send push notifications and in-app messages to Huawei mobile devices (with Android operating system) through Huawei Mobile Services
• Support for a new ‘Form’ Message type on Live Chat / In-App messaging channels
• Support for new Azure TTS voices and languages on Voice channel
• A new mobile wallet app to create and manage passes that can be sent on all channels supported

Please refer to the details below to know about all the changes and enhancements.

Added - Support for 10DLC numbers in the USA

A 10DLC long code is a phone number with the same length as standard mobile or landline numbers (typically a 10-digit number in many countries). In the past, business messaging traffic over long codes was sent over the carriers’ P2P networks, which limited them to very low throughput and restrictions on use from the carriers. With the introduction of 10DLC A2P messaging, carriers in the U.S. have rolled out a verified method of sending A2P traffic which has removed these constraints on business messaging making 10DLC enabled numbers more suitable for lower volume business messaging.

In this release we have introduced several new additions to our number management module to address changes in the messaging ecosystem triggered by the introduction of 10DLC A2P messaging (SMS and MMS) in the United States.

Added - Managing brand Id and campaign Id, Managing resources

In the 10DLC campaign registration process defined by the US operators, the concept of ‘brand id’ and ‘campaign id’ has been introduced which is administered by the third-party registry called “The Campaign Registry” or TCR, which will generate these fields after the sender/brand and the campaign are registered. The TCR is a centralized registry of information on companies who are authorized to use 10DLC numbers to send A2P traffic in the messaging ecosystem. US carriers utilize this registry to verify the origins and declared use cases in the ecosystem which permits for the control of “bad actors” and helps prevent abuse of the 10DLC ecosystem.

Further, brand Id and campaign Id fields are required for the phone number registration into the Netnumber OSR which carriers utilize to identify the messaging traffic associated with a phone number or 10DLC number in the ecosystem. This information is also needed by some carriers to authenticate the traffic on their networks.
The ‘10DLC enable request’ feature can be applied to US phone numbers with SMS capabilities purchased inside of your tenant. Having this designation confirms that the number is authorized for messaging traffic with operators in the US.
From the imiconnect tenant once the request has been submitted to enable 10DLC against the number from the Assets -> Numbers -> Action -> Request 10DLC, you will see the label “10DLC Requested” against the number. The 10DLC label will be applied to the phone number once the brand Id and campaign Id request have been approved with email confirmation to the Tenant owner’s email id.

If a campaign Id is already applied to your tenant, you can immediately purchase and apply the existing campaign Id to that phone number, provided it is the same use case. If it is a request for a new campaign Id based on a new messaging use case, you will need to submit the supporting information on the use case to [email protected] or your account manager for approval and to add the new campaign Id to your tenant. Once this is done, you can purchase numbers and register them against the new campaign Id.

📘

Note

It is recommended that if you have different messaging use cases, then you should secure multiple campaign Ids

Added - Number management capability enhancements

In this release, the direct number purchasing capability for the United States and Canada regions has been added. If you have an imiconnect tenant in the US and Canada, you can buy phone numbers and toll-free numbers by selecting the country as the United States or Canada and then the area code or location. These numbers can be provisioned for Voice, SMS and MMS.

Reach out to your account manager if you would like to enable MMS for your tenant.

Added – Process for supporting number procurement requests

The new number management system provides an option to request existing numbers to be text-enabled by attaching the Letter of Authority (LOA) documents. LOAs provide the necessary authorization needed for imimobile to register a number owned by another service provider for messaging on its network. imimobile staff will authenticate the LOA before text enabling or porting the number.

Additionally, the new enhanced number management system includes following updates:

• Custom requests for MMS Numbers, bulk number purchasing, porting, and searches for vanity TFNs from your tenant.
• Adds the capabilities to buy Phone Numbers with ‘Voice’ and ‘Voice, SMS’ and Toll-free ‘Voice’ and ‘Voice, SMS’ in the United States and Canada
• Usage Reports: In the Numbers section we’ve added ‘US 10DLC Brand ID’, ‘US 10DLC Campaign ID’ and the ‘US TFN Verified Sender’.
• Setting: Added options to manage Notifications in the profiles settings to subscribe for new alerts such as ‘Email for Custom and Bulk Requests’, ‘Email for Text enabling an existing number’, ‘Request to enable 10DLC’, ‘Number purchase order confirmation/ failed’.

Added – Send SMS from 10DLC and TFN numbers

With this release you can send SMS from TFN and 10DLC enabled phone numbers in imiconnect:

• All phone numbers added as a Sender ID with 10DLC enabled label confirmation can be used to send SMS via Messaging API v2.
• All numbers are available to be used in the rules and flows to send and receive SMS in the tenant.
• TFN numbers can also be authorized as a verified sender ID by going through a similar registration process like 10DLC. By sending a mail to [email protected]. Verified sender ID for TFNs permits high messaging and prevents carrier blocks.

❗️

Important Notice

• Effective July 1st, 2021, only the registered 10DLC numbers via “The Campaign Registry” or TCR are authorized for A2P messaging in the USA for SMS or MMS.
• Custom requests will be handled by the number management team
• Please note that only a maximum of 50 numbers can be registered against 1 Campaign ID.
• You may register multiple campaign IDs based on different use cases. Each campaign ID has a limit of 50 numbers which can be attached. If you need to attach more numbers, you must contact your account manager for special exemptions which are handled manually.

Added - MMS channel support

Starting with this release, two-way MMS (inbound and outbound) will be supported over short codes, long codes, and toll-free numbers in the US.
We have added 2 options to send MMS from imiconnect

• In Messaging API v2, we have added 'mms' as a new 'channel'. Please refer documentation on MMS API for more information on how to use this feature.
• A new 'MMS' option is added to Service - Rules > Action section.

Single slide and multi slide MMS with media attachments including Images, Audio, Video and File attachments are supported. These media files are resized / transcoded automatically to meet specifications of various carriers. Following is a summary of supported media attachments:

We have added Inbound MMS support in Rules to receive MMS on MMS enabled Short Code / Long code / Toll free number provisioned for your account. The same media attachments available while sending MMS are supported here. However, only Single slide MMS is supported, and multi-slide MMS sent by customers are split into multiple single slide MMS by few Carriers.

Along with the capability to send and receive MMS, following additions have been made to imiconnect

• Assets - Numbers: Added listing of MMS enabled numbers provisioned for the account
• Service dashboard: Added count of MMS to the traffic snapshot
• Reports: Added MMS channel and corresponding MMS traffic summary charts
• Integrations - Outbound Webhooks: Added MMS channel support to setup webhooks to listen to MMS delivery reports
• Debug & Archive search: Added MMS channel support across query by Transaction ID, query by Destination ID, and query Historical logs for both inbound and outbound MMS
• Tools - Export logs: Added MMS option to both Outbound Logs and Inbound Logs
• Usage report: Added MMS usage summary counts to the monthly usage report on the UI and added a new MMS tab to the exported usage report file.

MMS channel needs to be enabled before you can start seeing the details. Please reach out to your account manager if you would like to enable this feature for your tenant.

❗️

Important Notice

• MMS channel will only be available in the USA.
• We currently do not offer nodes in flow builder for sending and receiving MMS messages.
• Setting up / provisioning a new MMS enabled Short code / Long code / Toll free numbers will involve a few weeks’ lead time. Please reach out to your account manager for more information.

Added - Rules - UI tweaks for supporting MMS trigger & action configuration

Once MMS channel is enabled for the tenant, an inbound MMS can be setup as the 'Rule - Trigger' with conditions configurable on the sender number. Similarly, a 'Rule - Action' can be configured to send MMS as an action. All media types including the multi-slide MMS formats are supported.
Please refer documentation on MMS API for more information on how to use this feature

In-App Messaging and Push notification updates

SDK Updates

We’re releasing the following SDKs as part of the imiconnect v5.6.0 release:

• Android SDK v2.15.0
• iOS SDK v2.15.0
• Cordova SDK v2.3.0
• JavaScript SDK v1.3.0
  The changes made as part of these upgrades are covered below.

Added – Huawei Push Kit support for sending push notifications to Huawei Android devices

In this release, we are adding support for sending push notifications to Huawei Android devices via Huawei Push Kit. Huawei Push Kit is part of Huawei Mobile Services which replaces Google Mobile Services in Android devices built by Huawei for sending messages to apps on users’ devices in real-time.
On the imiconnect app configuration interface, you will need to configure the Huawei In-App ID and In-App Secret under Android Push Notifications configuration section. Please refer docs for more info.

Added - Support for ‘Form’ Message Type on Live Chat/In-App Messaging

A new message type called ‘Form’ is being introduced for Live Chat/In-App Messaging channel. ‘Form’ message can be used to collect customer data such as name, contact information, reason for contact, etc. over Live Chat/In-App messaging channel.
Forms can be configured from within Tools -> Template section and can be used in the In-App Send node within flows. Once a Form message has been sent, you can capture customer response by waiting for ‘Form Response’ within the receive node.
Along with the capability to send and receive Form Message type, following additions have been made to imiconnect:

• Outbound Webhooks - ‘Form Response’ has been introduced as a new event in outbound webhooks.
• Receive Node - Receive Node has been enhanced to fetch and display the form fields as output variables.
• In-App Send Node - Now you can select the message type as form and it'll let you select one of the forms pre-configured as a template, to be used in the flow.
• Flows - For flows using In-App messaging as the channel, while making the flow live, it'll now verify if the app asset being used for the flow has in-app messaging enabled and throw an error if it's not enabled.
  Please refer docs for more information on how to use Form Message type.

Added – New API ‘Delete Device App Profile by Customer ID and Device ID’

Introduced a new API endpoint to delete an app profile for a given combination of customer ID and Device ID. This is useful for situations where a customer with a given customer ID is using more than one device and you want to delete the profile for one of the devices.

Added - Option to download SDK initialization config file from mobile app asset configuration page

The app asset configuration page has been updated to allow downloading the complete config file required for initializing imiconnect mobile SDKs (Android, iOS, and Cordova SKDs). App developers can now directly embed the downloaded config file in their app code.

Added - Option to download SDK initialization config file from web app asset configuration page

Starting this release, the JavaScript SDK will have a single file containing all configurations required to initialize the SDK. For more details on how to initialize it in your app, please refer to the JavaScript SDK QuickStart guide

Changed – Interface to configure the Firebase config object for JavaScript SDK

We’ve updated the web-app asset configuration section to allow app developers to copy the complete ‘Firebase SDK setup and configuration’ JSON object and paste it in the newly introduced text box (as against individual fields that we had earlier for various parameters).

For existing assets that have web push already configured, the two fields namely, 'Server Key' and 'Sender ID' will be available in the new unified text box as a JSON object to ensure backward compatibility.

Added - Including AppID as output variable for all In-app message events in Flows Start node

Starting with this release, we have introduced a new output variable called inappmessaging.appid to capture and surface the app ID corresponding to the incoming event.

Added - Introduced ‘on Thread Closed’ as an Event Trigger in the Start node for Live Chat/In-App Messaging Channel

In this release, we have introduced a new trigger event for Live Chat/In-App messaging channel called 'On Thread Closed'. This event can be used to trigger a workflow in cases where an agent has resolved a client query and marked the conversation as closed, or if a customer has abandoned a chat and the chat is marked as closed due to it being timed out. Alongside this change, we have also introduced a new output variable called reasonForThreadClosure that allows you to pass the reason for closing a thread. This a new parameter in the Thread object.

Removed – Previously deprecated event triggers from the Start node for Live Chat/In-App Messaging Channel

We are hiding from Start Node UI the event triggers that were discontinued in an earlier release for Live Chat/In-App messaging. The following trigger events will no longer be shown:

• Interactive message response
• On location change
• On link click
• On Network change
• On web push click
• On connect
• On disconnect
• Roaming change
• Time zone change
  Please refer documentation for the updated list of event triggers for Live Chat/In-App messaging channel.

❗️

Important notice:

Live flows that are already using any of these events will not be affected by this change, these flows will continue to function to maintain backward compatibility. However, if the event trigger is edited in the start node, the discontinued events will no longer be available for use.

Enhancements in JavaScript SDK

We’ve introduced a new method _deleteMessage _in JavaScript SDK to allow you to delete an In-App message previously posted to a thread by passing the transaction id.

Additionally, we’ve introduced new attributes to the response callback of _uploadFile _method to surface the preview and URL of the uploaded file.

This apart, _MessageStatus _is now available as an enumeration on the ICMessage object. This was previously available in string format.

Support for unread in-app messages and unread threads count in Android, iOS, and Cordova SDKs

We’ve introduced support for getting the count of unread messages and unread threads in Android, iOS, and Cordova SDKs. This feature is not enabled by default and needs to be activated for concerned app asset by sending an email to your regional support team. Once enabled, the count of unread messages will be available as part of the Fetch Threads call. To get the count of unread threads, we’ve introduced new methods. Please refer docs for more information.

❗️

Important notice

The unread message and thread count feature apply only from the date of enabling the feature for the concerned app (using the latest version of Android, iOS, and Cordova SDKs).

Added - Handling failures on RCS channel

In this release we have created a pathway to return error information from carrier MaaPs to imiconnect via a new set of RCS gateway error codes. This will allow user to distinguish failed messages from the total number of submitted messages.

Please refer documentation on RCS API for more information on these new error codes.

Added - Handling SENT IMDNs from RCS Gateway

Starting with this release, we have created the ability to understand when a message has been passed off to the MaaP from the RCS gateway. This will allow user to understand how many messages out of the total number of submitted messages were passed to carrier MaaPs from the routing gateway.

Added – Support for Smart links in messaging API v2

Messaging API v2 now supports Smartlinks for SMS. Developers can add a Smartlink to message content by inserting the variable in the format {smartlink_id} where id is the identifier of the Smartlink.

Added – Support for customer name identification in WhatsApp events

Added support for capturing sender’s username received as part of a WhatsApp incoming message payload. This is available within the receive node, start node, outbound webhooks and notify URL in rules.

Changed - Messenger Graph API version upgrade

We have integrated with the updated version of the Facebook Messenger Graph API. With this upgrade we have moved from version v6.0 to v8.0. This is applicable for default platform Facebook Developer apps and for Messenger API endpoints.

Changed – Restrict Facebook Messenger page configuration changes to Tenant Owner user role

Starting with this release, only the Tenant owner user role will be allowed to make changes to Facebook Messenger page configuration from ‘Assets > Apps’ listing page. This has been done to avoid disruptions in case of accidental / unintended changes by other platform users.

Added - Support for additional Azure voice types in TTS

In this release we’ve extended support for the newly released Azure voices and languages. With this update we now support more than 250 voices and 70 languages.

Please refer to the Azure TTS documentation for the complete list.

Added – Collect input Voice node captures DTMFs in error outcomes

In the Collect input Voice node, starting with this release we are capturing the DTMFs pressed on the call for all outcomes including onError and failure cases. Currently the collect.input variable stores the DTMFs pressed onSuccess. With this update the DTMFs will be available in all outcomes.

Added - Call Patch Voice Node enhancements

In this release we’ve added the ability to customize the Number and Name to be displayed on the B-party’s handset. This is subject to the approval/acceptance of the Carrier.

Reach out to your account manager if you would like to enable this feature for your tenant

Added – Option to lock Template edits to the creator / tenant owner user role

We have added the option to lock templates to allow the creator of the template and the tenant owner to prevent unintended changes and/or deletion of the templates by other users. Once a template has been locked, a lock icon represents that the template is locked. This feature can be used to prevent users from deleting or making any updates to a template that’s being used in flows or with the messaging API.

❗️

Important Notice

Added – Mobile Wallet app in App-tray

Mobile Wallet is a new tool to create ‘passes’ which can be sent to consumers using any one of the channels supported by imiconnect. These passes can be installed in Apple Wallet and Google Pay apps. You can create different types of passes like Coupons, Loyalty cards, Tickets etc. You can also update the pass after it has been issued.

This tool will be available as an add-on in imiconnect App tray.

Added - Access control permissions for App Tray apps

We have added the ability for the apps in the app-trays to add two different types of access permissions for their platform on imiconnect. One is single select and the other one can be multi-select. These permissions will be passed to app-tray when the user log-in from imiconnect to app-tray.

Added - Safeguarding token-based login process for App Tray utilities from security attack

We have added mutually shared key-based hashing of an access token for app tray login of users from imiconnect. This feature is optional and can be used by apps in app-tray to avoid a Domain Name System attack.

Changed – Introduced restriction on number of methods that can be added in a Custom Node

The number of methods allowed to be setup within a single Custom node will be limited to a maximum of 25 starting with this release. Existing custom nodes will not be affected by this change; however, you will not be able to add additional new methods to a custom node already using 25 or more methods.

Added - Custom node - OAuth 2.0 Grant type Client Credentials and 'Client authentication' field

We have added support for the OAuth 2.0 Client Credentials grant type in the Custom node for machine-to-machine (M2M) authorizations.

Added – Reminder alerts on validity for Certificates used in Custom Node Integration, & Push/in-app channels

When a key store / trust store certificate is setup in custom node or an APNS certificate is setup for Push / in-app messaging, imiconnect now generates automated certificate expiry notifications based on the certificate validity. The notifications will be sent to all user’s setup under the tenant with following user roles: Owner, Full-access, and Limited access user roles.
Multiple reminder notifications will be sent 30, 15, 7, 3, 2 & 1 day before expiry (valid till) date and 1 & 7 days after certificate expiry or until the certificate is renewed.

Added - Notify URL validation

We have added URL validations for the ‘Notify URL’ feature in SMS node, Email node, call user node, Flow settings - Flow outcome, Logbooks, Voice recording, and Messaging API. Users will not be allowed to enter invalid URLs. If an invalid URL is passed in API request or via a variable, then such request will not be considered eligible for retries.

Added – File export processed notifications over E-mail and URLs for Logbooks & Voice Recordings

You can now provide an email / a notify URL to get notifications on the file exports scheduled on Logbooks and Voice Recordings. The notification is triggered at the end of each export cycle relaying the outcome of the file export process.

Added - Support for private key upload for SFTP file destinations

We are adding the support to upload the private key file for the SFTP based file destinations configurable at Logbooks, Export logs, and Voice recording. You can now upload the file while configuring an SFTP file destination if a key exchange is required.

Added – x-hub signature validation for inbound webhooks

We are adding additional support for signatures within headers of inbound webhooks that trigger flows. This is in addition to the already existing authentication using a service key or JWT tokens in the header and will remain optional while setting up your inbound webhooks. It will add an additional layer of security to your inbound webhook requests and help prevent man-in-the-middle type attacks.

Added – SHA256 and SHA512 support for Outbound Webhook

We have now added support for SHA256 and SHA512 signatures while setting up outbound webhooks. This is in addition to the SHA1 signature supported currently.

Changed - Tenant Owner login via SSO - restriction removed

We have removed restriction from Owner persona to always login via password. Owner can now login via SSO or password depending on SSO configurations.

Changed – User roles that can access Profile key

Starting this release, the permission to read and/or copy the profile key for a given tenant will be available only to the following user roles: Owner, Full-access, and Limited-access roles.
Users with ‘Restricted Access’ user role can no longer view / copy profile key.

Changed – Role based Access Control permission for creating Groups and Teams

Starting this release onwards, the ability to add new Groups and Teams will be restricted to Owner user role. Other user roles will not be able to add new Groups or Teams.

Added – Support for using underscores in Logbooks custom attributes names

We now allow underscores in the custom attribute names of logbooks. User can define the custom attributes with underscores for new logbooks and existing logbooks as well.

Added - Option to select ‘None' for Logbook file destination

Setting Logbook -File destination is now optional if a logbook is created for Embedded BI reporting. Users are no longer required to mandatorily choose a ‘File destination’ while creating a Logbook for Embedded BI.

Added – Enhancements to Usage Report

We have updated our ‘Usage Report’ to include additional usage information covering:

• Node execution count: Displays the cumulative count of number of times each node has been executed across all flows within your account.
• Custom node & Pre-built integration node count: Displays the name and cumulative count of number of times each integration node was run across all flows within your account
• Add-on features usage: Displays the list of add-ons optionally enabled for the tenant along with the associated usage metrics such as disk space used for logs / recordings against the individual add-ons
• Export usage report now shows 10DLC number details in SMS usage sheet for USA. We have added 3 new columns indicating the 10DLC brandID, CampaignID, and whether the number is ‘US TFN verified sender’ (Yes / No)
• Embedded BI Logbook usage: Displays the count of users segregated by ‘view-only’ access and ‘edit’ access for the advanced reports paid add-on. The same detail is also made available in the ‘Export usage reports’ excel file in a separate named ‘Logbook Reporting’. This usage detail is shown only to tenants with embedded BI add-on enabled.

Added – Control for managing Descriptive logs from Admin portal

We are bringing in a new control to enable descriptive logs at the tenant level. The update allows the imiconnect operations team to selectively enable capturing detailed descriptive logs as per the client’s license terms.

Added – A richer Reports and Insights section (Beta release)

As part of the reporting and analytics enhancements to the platform, we are introducing interactive reports and insights capability as a beta release. This feature provides a richer reporting experience allowing you to analyse your customer interactions better. Some of the key capabilities include:

• Rich data visualisations
• Drill through reports
• Cross highlighting and filtering between report visuals
• Customizable views
• Export report pages as PDF files
• Export summarized data from individual visuals into CSV, XLS files

❗️

Important Notice

This is a controlled beta release. Please reach out to your account manager if you would like to enable this feature for your tenant.

Added - Access control permissions for Embedded BI Logbook reports

We now support the ability to control the user access permissions to the advanced reporting (Embedded BI logbook reports) by the tenant owner. With this update, the tenant owner can provide view only access and edit reports access to the advanced reports to other users in the tenant.

❗️

Important Notice

Advanced reporting is an add-on feature, and it needs to be enabled before you can start seeing the details. Please reach out to your account manager if you would like to enable this feature for your tenant.

Fixed - Security fixes and upgrades

• Passive mixed content vulnerability – Fixed a minor issue where few sub resources in platform webpages (images, audio, video etc.) were loading over HTTP URLs. We have moved these resources onto strict secure HTTP (HTTPs) URLs
• Upgraded jQuery to v3.5.0 and Bootstrap to v4.3.1 in accordance with the security advisory by respective libraries to address known vulnerability issues.
• Fixed a vulnerability issue related to Stored XSS in flows by appending the page name as text instead of directly inserting into HTML
• Added additional validations to Input XML in inbound webhook API to fix a vulnerability related to XML External Entity (XXE) injection.
• Removed references to JSP version being disclosed while loading webpages to prevent attackers from potentially exploiting known vulnerabilities.
• Removed all references to internal application IPs which were disclosed in some of the backend API responses.
• Removed references to session / access tokens in few application URLs and moved them to the encrypted request headers to prevent man in the middle type attacks

FIXED – Flows: Output variables in Start & Receive nodes for Incoming Messages on Messenger

Some of the output variables such as messenger.attachmentUrl, messenger.locationUrl and messenger.locationTitle had incorrect or missing details.

This has now been fixed and the variables will now have the intended information. For more information on these output variables, please refer to documentation on Start nodes and Receive nodes.

❗️

Important Notice:

Please take note of this change in case you are using messenger.attachmentUrl or _messenger.locationUrl _output variables in Start / Receive nodes and make relevant changes to avoid disruptions.

Important Additional Notes

• The changes made to Output variables in Start & Receive nodes for Messenger is a potential breaking change. If any of your current flows are using messenger.attachmentUrl or messenger.locationUrl output variables in Start / Receive nodes for processing data, we recommend you to verify the flow configuration.
• We are hiding previously deprecated event triggers from Start Node UI for Live Chat/In-App Messaging channel. Existing flows that are already using any of these events will not be affected by this change. However, if the trigger event is edited in the start node, the discontinued events will no longer be available for use.
• In JavaScript SDK, MessageStatus is now available as an enumeration on the ICMessage object. This was previously available in string format. This is a breaking change however this comes into effect only once you update to the latest version of the SDK.
• We’re deprecating some of the previously supported integrations such as NICE inContact. Please refer documentation for more information on the latest integrations.
• Upcoming SDK change alerts: In future, Cordova SDK will no longer support Android OS v5.0 and below and iOS v10.0 and below as we will be moving to a recent version of Cordova framework.
• Following features, add-ons require additional configuration for you to start seeing them. Please reach out to your account manager if you would like to enable this feature for your tenant.
  • MMS channel for the USA. Procuring a new MMS enabled Short code / Long code / Toll free numbers will involve a 6–8-week lead time.
  • Customizing the Name / Display number in voice call patch node requires approval by carriers and it supported in limited regions.
  • The new Mobile Wallet App is an add on feature.
• Following Beta feature releases need to be enabled for your tenant for you to start seeing them. Please reach out to your account manager for further details. imiconnect standard SLAs do not cover the Beta features.
• Consent management App in app tray which provides a central interface for acquiring and managing customer consent preferences such as opt-in / opt-outs, contact channel preferences and contact frequency settings.
• A richer Reports and Insights interface which offers an enhanced reporting experience.

Change log