Routing and scheduling nodes in Default workflows

Routing and scheduling nodes connect a Default workflow to lead routing and meeting scheduling. They assign a lead to the right person, show a booking page and continue after the lead books a meeting, or cancel a meeting that was booked earlier.

​

Round-Robin

Assigns the lead to a member of a queue, using that queue’s rules. The assigned user is available to later nodes, so you can set them as the CRM owner or notify them.

​

Rules of Engagement

Runs a published Rules of Engagement ruleset to choose an owner or a queue from the lead’s data, such as region or company size. See Rules of Engagement to build a ruleset and for a full example. Default maps workflow data to the ruleset’s inputs automatically, so the node has no mapping field. The node has 2 branches:

• Resolved runs when a rule chooses a user or a queue, or when the Fallback queue applies.
• Else runs when the ruleset cannot make a routing decision, for example when no rule matches and no fallback queue is set, or when a rule routes to no one.

When a rule chooses a queue, the node already selects a member through the queue’s policy. Do not add a Round-Robin node after it for the same lead.

​

Display Scheduler

Shows a booking page to the lead and waits for them to book. The node then branches on the outcome. The settings are in 3 sections, in the order they appear on the node.

​

Booking Details

​

Redirect Settings

​

Display Options

The node has 2 branches, Booked and Not booked. After a booking, later nodes can reference:

• The meeting’s date and time, with a ready-to-use formatted date.
• The booked event.
• The primary host and any additional hosts.

The Not booked branch runs when the visitor does not book before the timeout, or explicitly does not book. On this branch, these values are empty.

​

Cancel meeting

Cancels a Default meeting that was booked earlier. Use it when a later check disqualifies the lead, or when a CRM update says the deal is closed. The node cancels the meeting the same way a host cancels it from the meetings page. It removes the calendar event and the video call, cancels reminders, and credits queue hosts. The node does not stop the workflow when it cannot cancel:

• If the meeting is already canceled, held, or marked as a no-show, the node logs a warning and the workflow continues.
• If the Meeting field is empty at run time, for example on a Not booked branch, the node logs a warning and the workflow continues.

Later nodes can reference Canceled, which is true only when this node canceled the meeting, and the meeting ID. Related: Lead routing software from Default and Sales scheduling software from Default