Check Activities

ūüēď Check Opening Hours

Audio / Video   Instant Message (Private Preview)    External Task


Performs a check on the current Opening Hours calendar applied to the service and exits accordingly.

✅ Required Predecessor: None - can work even without accepting a call (e.g. to Transfer to Service, Accept Conversation or Disconnect Conversation immediately)

Configurable Properties

Description

None

Will exit based on currently active Opening Hour rule currently in effect for your General Service Settings.

  • Exits match the¬†period types of opening hours¬†(open, closed, holiday, special 1-4),¬†allowing you to branch out your workflow accordingly.
  • If no opening hours are defined the¬†"default" exit on this activity is taken.

ūüĒć Notes on Opening Hours:

  • If¬†no¬†opening hours calendar is defined in your¬†General Service Settings, the¬†"Default"¬†exit in your activity is taken.¬†
  • Once created, an¬†Opening Hour¬†calendar must have a default opening state (e.g.¬†"Closed") assigned.¬†
  • If¬†both¬†primary¬†and¬†secondary opening hours are defined in your¬†General Service Settings,¬†precedence rules apply:
 Click here to learn more...

‚ėĚ General recommendation: The safe bet is to handle¬†all¬†exits on your workflow activity, as you you may lose tasks otherwise.

All cases in your activity should be handled

Availability Based Routing

Enterprise Routing Contact CenterAudio / Video Instant Message (Private Preview) External Task


Allows to route the call based on overall team availability.

✅ Required Predecessor: None - can work even without accepting a call (e.g. to Transfer to Service, Accept Conversation or Disconnect Conversation immediately)

Configurable Properties
Description
Service

Allows to select the target Service (within your tenant) for which the availability check and routing is performed for.

ūüí° Leaving this at "Current Service" will dynamically check the status of the service currently using this workflow. This allows for multiple services to use the same workflow with an "Availability based Routing" step without having to adapt the step's properties individually to their needs.¬†

ūüí° You can use this workflow step multiple times within the same workflow check different services simultaneously, e.g. to achieve an availability-based escalation and routing routine.

Example: using "Current Service" setting on shared workflows
Error: 404
Current Availability 
(Node Exits)

The activity has 3 exits based on the current overall team status (look-ahead). The availability depends on the User assignment type of your Service.

ūü§Ē How can I determin the type of service I'm in?¬†Team owners can access¬†Distribution Service Settings¬†and inspect the "User Assignment Type". Note that this type is determined during¬†Service Provisioning¬†and cannot be changed.

Service Availability (Exit condition) MS Teams-based Service Skill-based Service
No One Available All users are inactive ‚Äď or active but set "offline" in MS Teams) No users online or available within the service's¬†Distribution Policy¬†levels.
In Time Available All active users are not immediately available e.g. "DND/Away/Busy" or when occupied by another call. No users in the 1st Distribution Policy level are not available, but in any other levels users are available.
Direct Available At least 1 user is available = MS Teams presence set "available" and also set to "active" in Nimbus). At least one in the 1st Distribution Policy is available and ready to take a task.
ūüĒć Notes
  • The "Active" state toggle in a team can make users unavailable regardless of MS Teams presence.¬†
  • Additionally, MS Teams Presence also impacts the service availabiltiy. See note below.
  • The¬†Duty States¬†toggle for each user determines a user's currently applicable¬†Responsibility Profile¬†considered for skill based distribution.¬†
  • Additionally, MS Teams Presence also impacts the service availabiltiy. See note below.

MS TEAMS PRESENCE STATUS IMPACT ON AVAILABILITY

You can adjust Distribution Service Settings to include / exclude users from the availability count, based on their MS Teams presence state.

 

Get Available Users

Enterprise Routing  Contact Center Audio / Video  Instant Message (Private Preview)  External Task


Performs a lookahead-check on the users / Agents available in a Nimbus service and stores the value in a Parameter.

✅ Required Predecessor: None

Configurable Properties
Description
Service

Can¬†either¬†be the "Current Service" ‚Äď e.g. in workflows used by multiple services ‚Ästor¬†a specific service.

Custom Parameter

✅ Requires at least one Parameter to be defined and available as selectable "placeholder" under the same Organization Unit (or higher up to Tenant level).

ūüĒć This activity stores output into a custom¬†Parameter¬†for processing, which can then be used within the same workflow (e.g. a "¬†Check Parameter¬†" activity). Note that the parameter's default value is being overwritten once it passes through this activity.

Once this activity is reached, it checks the number of available users of the specified Service:

  • ¬†For¬†MS Teams team-based Services¬†all available team members are considered.
  • For¬†Contact Center Services¬†only available users in thefirst¬†Distribution Policy¬†level are taken into consideration.

→ For more information, read our pages on Service Type and the according User assignment method.

Check Parameter

Enterprise Routing Contact CenterAudio / Video Instant Message (Private Preview) External Task


Allows to check and react on system Fields and custom Parameters.

✅ Required Predecessor: None - responds to parameters updated during Trigger Events.

Configurable Properties
Description
Parameter Type

Offers a choice between:

Custom Type

ūüĒć Dependent on the "parameter type" selected:

  • A list of Nimbus¬†Fields and Parameters
  • Custom Parameter¬†of the following¬†type:
    • Context-->¬†$(CustomContextParameters.<Name>)
    • Customer Field¬†-->¬†$(Customer.CustomFields.<Name>)
    • Customer Telephone¬†--> Numbers¬†$(Customer.TelNumbers.<Name>)
Name

✅ Only shown when "parameter type" = Custom is selected. 

Allows you to define the a name used for the parameter. This name must match the dynamic value when using the Nimbus Microsoft Power Automate Connector. 
ūüí° Note that the parameter name depends on your "Custom Type" choice above, e.g.¬†$(Customer.CustomFields.YourExampleName

Checks 
(Node Exits) 
(1...10 allowed) 
 

Allows to define one or many regular expression checks on the "parameter type / name" chosen above.

ūüĒć Notes:¬†

  • By default 1 "Check" exit is defined. Up to 10 can be defined each with individual node exits. ūüí° Note that you can also nest several¬†"Check Parameter"¬†activities if you need to handle more parameters.
  • Checks will be performed in your defined order. The¬†first¬†valid check will determine the activity exit. Any further matching expressions are ignored.
  • Regular expressions cannot be empty. By default ".*" will allow anything as a parameter content = Parameter is present.

Show me some Regular Expression examples...

ūüĒć These are some common¬†Regular Expressions (RegEx) we recommend to use¬†within Nimbus.¬†To test your own regular expressions please consider using this online tool:¬†RegExr: Learn, Build, & Test RegEx.

Description

Regular expression

Check perform on Fields and Parameters

Incoming Call is from an external PSTN number ^\+[1-9]\d{1,14}$
  • MicrosoftCallerId
Incoming call is from an internal Teams account (UPN) ^[^@]+@.+$
  • CallerUPN

Incoming number is from Germany/UK

  • Germany +49
  • UK +44

Check country code

^([+]49)\d+

^([+]44)\d+

  • MicrosoftCallerId
Caller is anonymous ^Anonymous
  • MicrosoftCallerId
The incoming call is from Switzerland OR Germany ^([+]49)|^([+]41)\d+
  • MicrosoftCallerId
The value equals 1 ^[1]$
  • Queue Position
  • Custom Parameter
The value equals 2 ^[2]$
  • Queue Position
  • Custom Parameter
The value equals or is greater than 3 ^[3-9]$|^([1-9]\d|[1-9]\d{2,})$
  • Queue Position
  • Custom Parameter
No user is available ^[0]$
  • Available Users
  • Custom Parameter
One or more users available ^[1-9]$|^([1-9]\d|[1-9]\d{2,})$
  • Available Users
  • Custom Parameter
The value is true ^(true|True|1)$
  • Custom Parameter
The value is not Empty ^.
  • Custom Parameter
The lenght of the string is in between 5 or 10 and not less or more ^.{5,10}$
  • Custom Parameter
The lenght of the string equals 3 ^.{3}$
  • Custom Parameter

ūüĒć Also refer to¬†System Fields and Parameters¬†for a comprehensive list on parameters handled by Nimbus.

 
 

Check Queue Position

Enterprise Routing Contact CenterAudio / Video Instant Message (Private Preview) External Task


Performs a lookahead-check on the (potential) queue position in a Nimbus service and stores the value in a Parameter.

✅ Required Predecessor: None

Configurable Properties
Description
Service

Can either be the "Current Service" for workflows commonly used by multiple services or a specific service.

Custom Parameter

✅ Requires at least one Parameter to be defined and available as selectable "placeholder" under the same Organization Unit (or higher up to Tenant level).

ūüĒć This activity stores output into a custom¬†Parameter¬†for processing, which can then be used within the same workflow (e.g. a "¬†Check Parameter¬†" activity).¬†Note that the parameter's default value is being overwritten once it passes through this activity.

Once this activity is reached, it checks the number of available users of the specified Service

  • ¬†If the call was already added in queue (-‚Üí "Queue Task"¬†activity)¬†the current position¬†is saved into the parameter.
  • If call was not added,¬†the queue length +1¬†of the selected "Service" is saved into the parameter.

ūüí° By default this activity does not create a "visible" outcome. We recommend to follow up with a "Check Parameter" activity and route your customers according to the queue position value (e.g. add further¬†announcement, voicemail, play music¬†activities).

Wait for Parameter

Adds a wait time to the workflow to allow external systems to update a previously defined Parameters.

This activity stores output into a custom Parameter for processing, which can then be used within the same workflow (e.g. a follow-up "Check Parameter" activity).

  • The Nimbus Power Automate Connector ¬†"UpdateTask" Flow Action needs to be involved.
  • Upon entering the activity, a comparison against the default value of the Parameter is made.
    • When the Parameter already differs from the default or gets updated anywhere within the specified "Max Wait time" - the "Updated" exit is taken.
    • After the specified "Max Wait time" the¬† "Timeout Reached" exit is taken regardless if the parameter was updated.
    • When the activity is disabled the "Max Wait time" will be ignored and the "Timeout Reached" exit is taken immediately upon reaching this activy.
 
Configurable Properties
Description
Parameter Type

Currently locked to previously "Custom Parameters". To be defined and available as selectable "Custom Type" parameter.

Custom Type

ūüĒć Dependent on the "parameter type" selected:

  • A list of Nimbus¬†Fields and Parameters
  • Custom Parameter¬†of the following¬†type:
    • Context-->¬†$(CustomContextParameters.<Name>)
    • Customer Field¬†-->¬†$(Customer.CustomFields.<Name>)
    • Customer Telephone¬†--> Numbers¬†$(Customer.TelNumbers.<Name>)
Name

✅ Only shown when "parameter type" = Custom is selected. 

Allows you to define the a name used for the parameter. This name must match the dynamic value when using the Nimbus Microsoft Power Automate Connector. 
ūüí° Note that the parameter name depends on your "Custom Type" choice above, e.g.¬†$(Customer.CustomFields.YourExampleName

Max Waiting Time
  • Default: 5 seconds
  • Max: 1 mins
  • Min: 1 sec

¬†ūüí°When "Max Wait time" is reached (or this activity is disabled), the "Timeout Reached" exit is taken.

Play Announcement (optional)

Plays an announcement during the wait time. Default: disabled

  • TTS / ressource
  • preview of music
Announcement Type
  • Text-to-Speech¬†(with Language Select & Text Field)
  • Audio Resources.

✅  Audio resources can be added via Configuration > Resources 

Add Parameters
( Toggle )

Will allow the use of Custom Parameters and System Fields and Parameters in the "Prompt Text" Field. 

 

¬†ūüí° Note that with this option enabled the will "Preplay" feature is disabled as paramaters are dynamically resolved during a call.

Prompt Language Allows to select the locale / voice to use when using the Text-to-Speech engine.
Prompt Text

✅   Only shown when Announcement Type = Text to Speech is selected. 

  • Allows you to add text to the box that will be read in the prompt language / locale.
  • The announcement can be a mixture of text and Custom Parameters and System Fields and Parameters.
  • Announcements will be generated on-the-fly and cached if continously re-used.

 

Table of Contents