Skip to main content
Real-time queue notifications keep end users informed about queue updates by providing real-time information on their position and estimated wait time. This feature helps reduce anxiety and creates transparency, making end users feel valued and respected. By analyzing the data collected from the queue, you can identify patterns and trends for further analysis. For example, you might identify peak times when the queue is longest or determine the typical wait time for a response from a human agent.

Key benefits

  • Reduced user anxiety. End users receive continuous updates about their queue position and estimated wait time.
  • Increased transparency. Real-time visibility into queue status builds trust and sets clear expectations.
  • Alternative messaging. Automatically sends a customized message when queue conditions exceed defined thresholds.
  • Pattern analysis. Collected queue data helps identify peak times and typical response times.

Prerequisites

How it works

To set up real-time queue notifications, follow these steps:
  1. Configure the following nodes in your flow:
    1. Handover to Human Agent node or AI Agent node with the Handover to Human Agent tool — allows queue position and wait time tracking.
    2. Lookup — routes the flow based on handover status.
    3. If — evaluates queue conditions.
    4. Say — displays queue updates or alternative messages to the user.
    5. Go To — loops back to continue monitoring the queue.
  2. Configure the provider-side settings to enable queue notifications for Salesforce Enhanced Chat or Genesys Cloud Open Messaging.
  3. (Optional) Configure the Agent Copilot workspace.

Configure settings for handover to human agent node or tool

  1. In the flow editor, add a Handover to Human Agent node.
  2. In the Handover to Human Agent node, select Live Agent, Salesforce Enhanced Chat, or Genesys Cloud Open Messaging from the Handover provider list.
  3. For the queue position, configure the following:
    • Queue position — activate the setting to retrieve the end user’s current queue position. This setting isn’t available for Genesys Cloud Open Messaging, which doesn’t provide a queue position. If you use Genesys Cloud Open Messaging, skip this step and go to step 4.
    • Update interval — enter the interval (in seconds) to receive updates on the queue status. For example, set the interval to 30 seconds to receive updates every half-minute. This setting is applicable only to Live Agent.
  4. For estimated wait time, configure the following settings:
    • Estimated wait time — activate the setting to retrieve the estimated wait time for the end user.
    • Update interval — enter the interval (in seconds) to receive updates on the wait time. For example, set the interval to 30 seconds to receive updates every half-minute. This setting isn’t available for Salesforce Enhanced Chat.
  5. Configure alternative update options:
    • Fallback message — activate the alternative update options that trigger when certain conditions are met, such as reaching the maximum queue position or maximum estimated wait time.
    • Maximum queue position — enter the maximum queue position. If you set this to 5, the system sends an alternative message when the user’s position exceeds 5. This setting isn’t available for Genesys Cloud Open Messaging, which doesn’t provide a queue position.
    • Maximum estimated wait time — enter the maximum estimated wait time in milliseconds. Set this to 300000 milliseconds (5 minutes). If the estimated wait time exceeds this time, the system sends the alternative message set in the Message text field.
    • Message text — enter a message that is sent when either the maximum queue position or maximum wait time is reached. For example, Thank you for your patience. We are experiencing higher than usual wait times. Please hold on, and an agent will assist you shortly.
  6. Click Save Node.
When the settings are configured, you can test this configuration by creating a handover via Demo Webchat. In the chat, as an end user, you receive the message in the following format:
In the following sections, you convert this message to make it more accessible and to configure the Message text message output.

Add lookup node

  1. Below the Handover to Human Agent node or tool, add a Lookup node.
  2. Click the Lookup node and select Handover Status from the Type list.
  3. Click Save Node.
  4. In the Case node of the Lookup node, select Queue from the Handover Status list and click Select.
  5. Click Save Node.
  6. Remove the second Case node.

Add if node

  1. Below the Case node, add an If node.
  2. In the If node, click Use Advanced Editor and add the following condition:
    where:
    • {{input.data.request.position}} < 2 — checks if the customer’s position in the queue is less than 2. If true, it means the customer is either in first or second position in the queue.
    • {{input.data.request.estimatedWaitTime / (1000 * 60)}} < 200 — calculates the estimated wait time in minutes. The estimated wait time is provided in milliseconds. Dividing it by (1000 * 60) converts it to minutes. This CognigyScript expression checks if this wait time is less than 200 minutes. If true, it means the estimated wait time is manageable.
  3. Click Save Node.

Add say nodes

  1. Below the condition Then, add a Say node.
  2. Click the Say node and enter the following text into the Text field:
    where:
    • input.data.request.position — the user’s current position in the queue.
    • input.data.request.estimatedWaitTime / (1000 * 60) minutes — the estimated wait time in minutes. The estimatedWaitTime is initially provided in milliseconds. It’s divided by 1000 to convert it to seconds, and then by 60 to convert it to minutes.
  3. Click Save Node.
  4. Below the condition Else, add another Say node and configure the following:
    • Text — enter {{input.handover.data.alternativeText}}. This CognigyScript expression returns the text from the Message text field of the Handover to Human Agent node or tool that you configured earlier.
    • (Optional) Label — enter Alternative text.
  5. Click Save Node.

Add go to node

  1. Right-click the Lookup node and select Set Entrypoint.
  2. Below the Say nodes, add a Go To node.
  3. In the Go To node, configure the following:
    • Select Flow — select the current flow.
    • Select Node — select Lookup.
    • In the Advanced section, select Go to Node and wait for Input from the Execution Mode list.
  4. Click Save Node.
Flow configuration for real-time queue notifications with Say and Go To nodes

Configure settings in Salesforce Enhanced Chat

If you use Salesforce Enhanced Chat as your handover provider, activate queue notifications in the Salesforce settings:
  1. In Salesforce, go to the Setup page, enter Messaging Settings in the Quick Find box, and click Messaging Settings. Alternatively, go to Feature Settings > Service > Messaging > Messaging Settings in the navigation menu.
  2. In the Channels section, find the channel you want to configure, click the arrow-down icon, and select Edit.
  3. Go to the Queue wait time and position section.
  4. From the Notification list, select one of the following options:
    • Estimated wait time — sends the estimated wait time to the end user.
    • Queue position — sends the user’s current position in the queue.
  5. Click Save.

Configure settings in Genesys Cloud Open Messaging

If you use Genesys Cloud Open Messaging as your handover provider, real-time queue notifications rely on the Amazon EventBridge integration. Complete the following configuration in Genesys Cloud.
Genesys Cloud Open Messaging doesn’t provide a queue position. Estimated wait time is the only parameter available and is calculated internally by Genesys Cloud Open Messaging.
Cognigy needs to receive the event indicating when a human agent accepts (answers) a conversation. This event is delivered through the Amazon EventBridge Source’s event stream.
  1. In Genesys Cloud, go to IT and Integrations > Integrations.
  2. On the Integrations page, select the Amazon EventBridge Source that you created previously.
  3. Open the Configuration tab.
  4. Go to Properties > Topic Filtering.
  5. Select v2.detail.events.conversation.{id}.user.start.
  6. Click Save and Activate.
For more information, see the UserStartEvent documentation in the Genesys Cloud Developer Center.
Estimated wait time is only calculated once an agent has reached maximum capacity and additional conversations are placed on hold.
  1. In Genesys Cloud, go to Digital and Telephony > Interaction Assets > Utilization.
  2. On the Organization tab, go to Channels.
  3. In the Message row, click Edit in the Actions column.
  4. Set Maximum Capacity to 1, or the value needed for your setup.
When a human agent reaches this capacity, any additional conversation is placed on hold, and Genesys begins polling and returning an estimated wait time for it.
A direct transfer between human agents overrides maximum capacity. Skipping the hold and estimated-wait-time behavior is a native Genesys Cloud Open Messaging capability and can’t be changed in Cognigy.

(Optional) Agent Copilot

If you use the Agent Copilot workspace and Agent Copilot is active in your contact center, the Agent Copilot flow needs additional configuration to send queue update messages. To configure the Agent Copilot flow for sending queue update messages, complete the following steps:
  1. Add a Handover to Human Agent node to the Agent Copilot flow. Configure this node the same way as the Handover to Human Agent node in your main flow.
  2. Add a Lookup node for the Queue status, followed by an If node, Say nodes, and a Go To node. Mirror the logic you already configured in the main flow:
  3. In the main flow, below the Case node that checks the Queue status, add a Go To node that points to the Agent Copilot flow’s Lookup node.

More information

Last modified on November 11, 2026