Dial (CX Voice) | Expertflow CX

Node	Dial
Description	This node places an outbound call to a contact through your contact center, then reports back on that call's progress and final result through its two outputs.

Overview

Takes a single contact (sent in by an upstream node) and schedules a voice call for them through the configured channel.
Doesn't wait around for the call to happen — it hands the request off to a scheduling service and moves on.
Later, that same node reports back what happened: live progress on one output, and the final delivery result on the other.
If the contact is missing, or doesn't have a usable phone number on file, the contact is skipped quietly — no call is scheduled and nothing is treated as an error.

Category	Inputs	Outputs	Default Label
Channel Action	1	2	Node name, or "Dial" if left blank

Output	Label	Carries
1	Live Call Event	Real-time updates about a call's progress as it happens (e.g. ringing, connected).
2	Delivery Notification	The final result of a previously placed call (e.g. delivered, failed), once the scheduling service reports it.

Setting	Default	What it does
Name	(blank)	Optional label for the node.
Channel	First available CX Voice channel	Which configured Voice channel/service to place the call from. Loaded automatically — only Voice channels are shown.
Customer Identifier	(from contact schema)	Which field on the contact record holds the number to dial. Loaded from your org's contact schema fields marked as channel identifiers (e.g. phone number).
Identifier Index	1st	If that field can hold more than one value (e.g. several phone numbers), which one to use — 1st through 10th.
Gateway ID	System default	Which telephony gateway to route the call through. Defaults to a system-wide setting unless overridden here.
Campaign Type	Agent (fixed)	Calls are connected to a live agent. Currently the only option available, and can't be changed from the editor.

For a normal incoming contact, the node checks that a contact is attached to the message and that it has a usable value in the configured identifier field.
If either check fails, the contact is skipped — no call is scheduled, and nothing is shown as an error.
Otherwise, it builds a single call request for that contact and hands it to the scheduling service, then moves on without waiting for the call itself to happen.
If the contact had previously been flagged for a retry, that's marked as resolved once it's handed off again.
Sometime later, the scheduling service reports back on what happened to that call — this is sent out the Delivery Notification output.
Separately, live progress updates for a call this node placed are sent out the Live Call Event output as they happen.