Instant Messaging

An overview of the Instant Messaging modality.

The Nimbus Task Distribution algorithm can also distribute Instant Messaging (IM) modality tasks to users. Such tasks can be created via Interact as the entry channel and be added to the service queue along any regular task. By the use of specific Workflows, an IM task is fed into the queue of any enabled service. As Nimbus user, you remain in your known MS Teams environment, get notified via Adaptive Cards and a chatroom is created by a Nimbus bot.

INC Instant Messaging Preconditions


Instant Messaging (IM) is a user modality feature to be enabled for your tenant. This is done during initial setup with your Luware Customer Success representative and in tandem with License Management for your users and services. You can also read Use Case - Setting Up Instant Messaging for a walkthrough.

☝ Please Note: 

  • Tenant Admin rights are needed to handle Tenant and Service settings and apply the licenses accordingly.
  • Delegated Tenant Admin permissions are required once via grant link. This link can be found under Modalities Tenant Settings  > Instant Messaging > “Grant Permissions”. Refer to Nimbus App Permissions for more details on these permissions.

Licensing and Settings

Note that either Users or Services need a license for Interact to handle incoming messages. Refer to Use Case - Setting up Interact to learn more on how to embed Interact on your website.

  • If a Service has an Interact license assigned, users also need an Instant Messaging modality license to handle IM interactions with outside customers. This is all done within Service Administration and User Administration, respectively. → See Service and User Requirements below.
  • If a User has the Interact license, the service requirement can be skipped. → See User requirements below.

Service Requirements

These requirements apply when you want to distribute instant messages via service queue. 

The service Configuration is done in General Service Settings and Interact Service Settings.


User Requirements

These requirements apply for all users you want to distribute instant messages to. There are two methods for this, either distribution via service queue via service or user directly.

Distribution via Service Direct to User

✅ Service Requirements from above apply.  



The receiving user(s): 

  • Need to be part of the service so they are considered by its queue OR be defined as preferred user in a service Distribution Policy.
  • Needs an “Instant Messaging” modality license assigned in General User Settings.

Without a service being involved, users receive instant messages via Interact.


The receiving user(s):

End-User Permissions

💡Optional - only when using Adaptive Cards: Each receiving user of the Instant Messaging modality needs to register with the IM chat bot once in order to receive Adaptive Cards messages for incoming IM tasks / chat session invitations. This is done via Nimbus Portal > User Preferences.

After registration, the IM Signaling Bot will invite users via Adaptive Cards on incoming chat messages.

Good to know: Chat interactions received via My Sessions, Attendant Console, or Assistant do not require the IM Signaling Bot registration, as the Nimbus UI will handle the distribution.


Interact can be set up for user and for services. If Interact is set up for a user with Instant Message modality enabled, instant messages will be handed directly to the user without any task creation involved.

The following sections refer to the scenario when Instant Messages are received and distributed by a service via Interact.

IM Task Creation

Currently, Instant Messaging tasks can only be created through Interact, either by using the Interact client or the Interact SDK. The customer on the website needs to provide a display name and an email address, and accept the privacy policy. Optionally, the customer can provide an initial message as well. For quick verification or testing purposes, the preview page can be used. This can be found on top of the code box on the user/services interact tab. This applies for users (users can be exposed and enabled as well) and services.

🔍 Refer to Use Case - Setting Up Interact for detailed steps on how to set up Interact.

IM Task Distribution

Instant Messaging tasks are distributed according to dedicated Instant Messaging Workflow definitions, allowing to:

  • Introduce artificial delays in the Workflow itself, in order to allow background Flow Actions to run and retrieve the necessary details.
    🔍 Also see Use Case - Setting Up Instant Messaging.
  • Support simple “Queue” task distribution or to check on task positions and act accordingly, e.g. by
    • transferring the task to another service
    • cancelling the task

IM Task Handling

🔍 For information about IM task handling, refer to Instant Message Handling.


INC Instant Messaging Limitations


  • Engaging in Instant Messaging with Nimbus Services currently requires Interact and its SDK.
  • Supervision is currently not supported for Instant Messaging interactions.

Table of Contents