Open Dialogue Studio

Open your browser and go to the Dialogue Studio URL provided by your AnywhereNow contact or from the AnywhereNow OnePortal Formerly known as Partner Portal. A redesigned web portal for managing Dialogue Cloud deployments..

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 A Unified Contact Center, or UCC, is a queue of interactions (voice, email, IM, etc.) that are handled by Agents. Each UCC has its own settings, IVR menus and Agents. Agents can belong to one or several UCCs and can have multiple skills (competencies). A UCC can be visualized as a contact center “micro service”. Customers can utilize one UCC (e.g. a global helpdesk), a few UCC’s (e.g. for each department or regional office) or hundreds of UCC’s (e.g. for each bed at a hospital). They are interconnected and can all be managed from one central location.). Use this as the starting point for IVR Interactive Voice Response, or IVR, is a telephone application to take orders via telephone keypad or voice through a computer. By choosing menu options the caller receives information, without the intervention of a human operator, or will be forwarded to the appropriate Agent. 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 events received from the UCC event stream. Use it to react to system events outside the regular call phases.

Create your first flow

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. In Filter, select Audio.

   

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 and configure the service URL:

   1. http://<internalServiceUrl>:<configuredPortNumber>. Replace internalServiceUrl and configuredPortNumber with your internal service host and port number (provided by your AnywhereNow contact or visible in your Plugin Settings).

   2. 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 Anywhere365-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.

Operation	What it does	Impact on active calls	Use when	Key risks
Deploy	Applies flow changes without stopping unaffected flows (only changed parts reload).	Calls continue if paths stay valid; updated prompts or logic apply when reached.	Routine edits such as text updates or small logic tweaks.	Broken wires or invalid outputs can dead-end callers.
Restart Flows	Stops and restarts all flows.	Current prompt finishes; then no new nodes execute for active calls. Timers and transcripts can stop.	Only when you must fully reload running flows.	Callers can be stranded in IVR, queues, or surveys until they hang up or the call transitions.
Restart instance (OnePortal)	Restarts the Dialogue Studio runtime.	Similar to Restart Flows but with longer downtime while modules load.	Required after updating or removing palettes (node modules).	All in-flight logic, timers, and events are lost; brief event gaps are possible.

Behavior by call phase

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

Phase	Deploy (expected behavior)	Restart Flows (risk/behavior)
Incoming call (IVR)	Active calls continue; edits apply when nodes are reached. Ensure all outputs remain connected.	Current Say/Play finishes; then no further nodes run. Caller cannot progress and may need to hang up.
Enqueue	Music and prompts continue. Changes apply on the next cycle.	After the current prompt, silence until an agent answers.
InDialogue	Session stays connected. Automations apply as the flow reaches them.	No Dialogue Studio nodes run until the call ends. PostDialogue still runs on disconnect if configured.
PostDialogue	Follow-ups run normally. Edits apply on the next run.	No action and transitions may not execute. QM Question will not start.
QM Question / Answer	Survey proceeds; edits apply when reached.	Survey can stall and not advance to the next question.
Transcription	Continues as normal.	Output stops for active sessions until retriggered.
Event Bus	Continues as normal.	Some events can be missed during the brief reload window.