Dialogue Studio User Guide

Open Dialogue Studio

Open your browser and go to the Dialogue Studio editor URL provided by your AnywhereNow contact or available in OnePortal.

The basics

You start on an empty canvas. The right sidebar lists available building blocks called nodes. Drag nodes from the sidebar onto the canvas to build your flow. The empty canvas you see is called a flow. The flow tabs appear in a bar under the page header. Select + to add a new flow or select the list button to view all flows.

To learn what a node does, select it and open the Node information tab in the right sidebar. Use the Debug tab (bug icon) to view logs and errors while you test.

When you make a change, the Deploy button in the upper-right turns red. Select Deploy to apply changes.

AnywhereNow Core nodes

These nodes control when your flow starts and how it reacts to contact-center events.

Icon	Description
	Incoming call Triggers when an audio conversation enters the Unified Contact Center (UCC). Use this as the starting point for IVR and initial routing. For text conversations, see: Incoming message
	Waiting queue Triggers when an audio conversation is enqueued. Use this as the starting point for queue messages.
	InDialogue Triggers after a audio conversation connects to an agent. Use it for automations during the live session, such as whisper prompts, transcription, or translation.
	PostDialogue Triggers when one participant disconnects in a audio conversation. Use it for after-call actions like post-conversation messages or updates. End the PostDialogue phase with a No action node.
	QM Question Triggers once PostDialogue ends—one event per configured Quality Monitor question. Use QM Answer to send responses and proceed.
	Event Bus Triggers on generic events received from the Core service event bus. These events are not scoped to the connection's UCC name.

Create your first flow

This example uses Core nodes connected through the HTTP/SignalR plugin. Confirm that this is the provisioned connection path for your UCC. The steps do not specify connection settings for other transports.

Build a simple flow that plays a message and then disconnects.

1. Drag an Incoming call node to the canvas.

2. Double-click the node to open settings. Select Audio/Video in Filter, not IvrQuestion (Audio/Video).

   

3. Under Server, select an existing connection.

   If your administrator already configured the server connection, select it here and skip the sub-steps.

   If no connection is available, select Add new any-red-config, then select the edit (pencil) icon.

   Before configuring a flow, confirm the selected node's transport and the active configuration source for your environment. Use the connection details provided during provisioning. Applicability depends on that transport and configuration source, not the connect model alone.

   For Core nodes using the HTTP/SignalR plugin connection, configure Server with the Core service URL, including the plugin listener port, and the UCC name. Use the HTTP or HTTPS scheme configured for that listener. The editor URL you open in your browser is not this service endpoint. For another transport, use its provisioned connection details rather than assuming these listener settings apply.

   For the HTTP/SignalR plugin path, OnePortal assigns a separate Dialogue Studio plugin port to each UCC during provisioning. Use the assigned port with the service URL and UCC name. Sharing a listener port is also supported for this plugin path, but is not standard OnePortal provisioning. Do not change an assigned port without coordinating with AnywhereNow. Align all affected connections and dependent network configuration when changing it.

   Configure the connection:

   1. Enter the provided service URL, for example http://<internalServiceUrl>:<assignedPort>. Use the internal service host, assigned plugin port, and HTTP or HTTPS scheme provisioned for this plugin connection. If your active configuration source is the Ucc.Creator SharePoint template, the port is also visible in the UCC's Plugin Settings.

   2. Enter the UCC name provided for this connection. It scopes normal callflow events and actions, but not generic Event Bus events.

   3. Select Done.

4. Drag a Say node to the canvas. Double-click the node to open settings. Set Message to “Welcome, we will disconnect you in a moment.” Select Done.

5. Connect the output port of Incoming call to the input port of Say.

   

6. Drag a Action node to the canvas. Double-click the node to open settings. Set Action to Disconnect. Select Done.

7. Connect Say to Disconnect.

8. Select Deploy to apply changes.

Your canvas should look like this example:

Call your UCC. You hear the message, then the call disconnects.

Keep learning

Explore end-to-end examples in Dialogue Studio Scenarios.

Browse community samples in the DialogueStudioFlows GitHub repository.

Import sample flows to explore common patterns.

1. Select the menu in the upper-right and choose Import.
2. Open the Examples tab and select the Anywherenow-red samples for UCC scenarios. Each sample indicates whether it targets chat or audio.
3. Follow the comment nodes in the sample for required setup steps. Make sure the UCC connection is configured before testing.

Advanced information

The right sidebar contains several tabs. If the sidebar is collapsed, use the arrow to expand it.

Node information

The Node information tab shows metadata for the selected node or flow: identifier, name, type, and description. To edit the description, open the node and use the Description tab. Developers can also provide Node help that explains usage and options.

Debug

Use the Debug tab to view errors and log messages. To test quickly, connect an Inject node to a Debug node and deploy. Select the Inject button to send a test message and observe output in the panel.

Configuration nodes

Find and manage saved connection settings in the Configuration nodes tab. Use this view if a node loses a reference or if you need to update credentials.

Context data

Use the Context data tab to inspect values stored at the node, flow, or global level. Nodes such as Function and Change can read and write this context.

Select the refresh icon to reload values. You can also delete context entries from this view.

Production safety: Deploy vs Restart Flows

Choose the safest operation for live environments. In short: Deploy applies edits with minimal disruption if the flow remains valid. Restart Flows reloads all flows and interrupts active sessions. Updating or removing palettes (node modules) requires restarting the Dialogue Studio instance via OnePortal.

Differences

Use this chooser to decide which action to take.

Behavior by call phase

How each action behaves during IVR, queueing, live conversations, and after-call processing.