Accept

Accept

Description Accepts an incoming task (of any modality) and establishes the corresponding communication channel between caller and user.
Required Predecessor

Essential: Disconnect AND Accept in a Workflow

☝ This activity is essential and cannot be disabled. 

MUST CAN
  • … be connected to the Start node to form a valid workflow. 
    Some activities may run in front, but limitations apply → See below.
  • … be part of any and every workflow to ensure service session tracking, Task Queue and Distribution handling and Statistics reporting.
  • … be used in conjunction with a “Disconnect” activity to form the opening and closing brackets of a workflow and related session in the Nimbus Reporting Model.

… have the following Check Activities activities before it: 

1 LIMITATION: Microsoft will wait for 15 seconds for a Nimbus answer triggered by the Accept activity. 

⮑ After that the task will fail. 

⮑ Note that during this time, the call will still ring for the customer.

⮑ As Nimbus cannot control how long external systems need to recover data (e.g. via Nimbus Power Automate Connector) we recommend smaller routines for checking essential parameters. Afterwards you can Accept and handle further checks during a customer announcement or IVR. 

 
License
Advanced Routing Enterprise Routing Contact Center
Modalities Audio / Video Instant Messaging Email External Task

Common Properties

Configurable Properties Description
None

Controls when your task will be marked as “Accepted by System” in a Nimbus Reporting  session, both for the Nimbus Reporting Model and later KPI evaluation purposes in the Nimbus Power BI Template.

🔎 This activity is part of the Trigger Events in the Nimbus Power Automate Connector.

 
 
 

Audio / Video

 
 

Instant Messaging

 
 

Email

 
 

External Task

 
 

Table of Contents