AI Workflow Orchestration Guide

How to build a workflow where one bot handles general questions, order lookups, scheduling, and anything else — in any order — mid-conversation.

---

The short version

You need three things on the canvas:

1. Dedicated AI nodes — one per integration (NetSuite AI, BigCommerce AI, Calendly AI, AI Chatbot). Each node type automatically loads the right skills for that integration. No extra setup needed.

2. Section Entry nodes — one per AI node. These are just named waypoints. Zero config. They sit in front of each AI node as an addressable label.

3. Jump targets — on each AI node, you tell it which Section Entry nodes it can jump to, and when.

That is the entire system. The AI reads the jump target descriptions and calls the right jump tool when the visitor's message matches.

---

What each piece does

AI nodes

Each AI node automatically loads its own skills when execution reaches it:

• AI Chatbot — general conversation, KB answers, no integration skills
• NetSuite AI — order lookup, case status, customer account, invoices, lead creation
• BigCommerce AI — product search, pricing, availability, cart, returns
• Calendly AI — list meeting types, create scheduling links

You do not configure which skills are available. They come with the node type automatically.

MCP is not required. MCP is an optional add-on for custom external tools you build yourself. The built-in integration skills load without it.

Section Entry node

A Section Entry node is a named waypoint. When another AI node jumps here, execution passes straight through to its child (the AI node below it). You only set one thing: the name. That name becomes the jump tool — a Section Entry named "Book Appointment" creates a jump_to_book_appointment tool on every AI node that lists it as a target.

In the node picker: Flow category → Section Entry

The only field: Section name (e.g. "General Help", "Order Lookup", "Book Appointment")

Jump targets (on each AI node)

In the right panel of any AI node, scroll to Jump to Workflow Section. Check the Section Entry nodes this AI can jump to.

When you check a section, the intent field auto-fills based on the node type below that section (e.g. Calendly AI auto-suggests "wants to schedule a meeting, book a demo, set up a call, pick a time"). You can edit or keep the suggestion.

For each jump target:

Jump here when the customer… — plain English description of the intent that triggers the jump

The AI uses this text to decide when to call the jump tool. Be specific. Use real customer phrasing.

---

Working canvas: general chat + NetSuite + Calendly

This handles general questions, order lookups, and appointment booking in any order mid-conversation.

Canvas layout

[AI Chatbot]
      |
[Section Entry: "NetSuite Orders"] → [NetSuite AI]
[Section Entry: "Book Appointment"] → [Calendly AI]
[Section Entry: "General Help"] → [AI Chatbot]

The arrows above are not workflow connections — they are parent→child relationships (each Section Entry has one child). The jumps between them are configured inside each AI node's panel, not as canvas arrows.

Node 1: AI Chatbot (starting node)

This is the first node in the workflow. The visitor starts here.

Field	Value
AI Config	your main bot config
Jump to Workflow Section	check "NetSuite Orders"
→ Jump here when the customer…	asks about an order, invoice, account balance, payment status, open cases
Jump to Workflow Section	check "Book Appointment"
→ Jump here when the customer…	wants to schedule a meeting, book a demo, set up a call, pick a time

Node 2: Section Entry

Field	Value
Section name	NetSuite Orders

Child node: NetSuite AI (below it on canvas)

Node 3: NetSuite AI

Field	Value
AI Config	your main bot config (or a NetSuite-specific one)
NetSuite Config	select your NetSuite connection
Jump to Workflow Section	check "General Help"
→ Jump here when the customer…	done with orders, has a different question, wants general help
Jump to Workflow Section	check "Book Appointment"
→ Jump here when the customer…	wants to schedule a meeting, book a call, talk to someone

Node 4: Section Entry

Field	Value
Section name	Book Appointment

Child node: Calendly AI (below it on canvas)

Node 5: Calendly AI

Field	Value
AI Config	your main bot config (or a Calendly-specific one)
Jump to Workflow Section	check "General Help"
→ Jump here when the customer…	booking is confirmed, done scheduling, has other questions
Jump to Workflow Section	check "NetSuite Orders"
→ Jump here when the customer…	asks about an order, invoice, or account while booking

Node 6: Section Entry

Field	Value
Section name	General Help

Child node: AI Chatbot (below it on canvas) — same config as Node 1, same jump targets

---

How it flows at runtime

1. Visitor starts → hits AI Chatbot → general conversation + KB answers

2. Visitor says "what's the status of my order?" → AI calls jump_to_netsuite_orders

3. New session starts at Section Entry: NetSuite Orders → drops into NetSuite AI → order lookup skills active

4. NetSuite AI answers, visitor says "great, can I book a call?" → AI calls jump_to_book_appointment

5. New session starts at Section Entry: Book Appointment → drops into Calendly AI → scheduling skills active

6. Calendly AI books the meeting, visitor says "thanks, one more question" → AI calls jump_to_general_help

7. Back to AI Chatbot → general conversation continues

No fixed sequence. Visitor can go in any order. The full conversation history is always preserved — each new AI can see everything said before.

---

KB answers work everywhere

All three AI nodes can be pointed at the same AI Config. That AI Config has your knowledge base (Azure AI Search) attached. So whether the visitor is talking to the general AI, the NetSuite AI, or the Calendly AI — they all answer KB questions from the same source. You only set it up once.

---

Does it work on SMS and IVR?

Yes. The section jump mechanism works on all channels:

• Web chat — full experience
• SMS — the AI sends scheduling links as plain text URLs; Calendly works over SMS
• IVR (voice) — the AI reads out options and collects responses; scheduling links are sent via SMS follow-up. IVR-specific skills add a send_sms_followup tool that fires a link to the caller's phone.

Channel-aware skills automatically adapt their responses to the channel. No extra configuration needed.

---

Adding BigCommerce to the mix

Add two more nodes:

Section Entry: "Product Help" → child: BigCommerce AI

On the BigCommerce AI node set jump targets to "General Help", "NetSuite Orders", "Book Appointment" with appropriate when-descriptions.

Then add "Product Help" as a jump target on the AI Chatbot, NetSuite AI, and Calendly AI nodes with:

asks about a product, price, availability, shipping, returns, cart

---

What the Specialist Agents panel does (and does not do)

Every AI node has a Specialist Agents panel. This swaps the AI's personality (system prompt) mid-conversation without changing which node is running. It does NOT load integration skills. A Specialist Agent running inside an AI Chatbot node does not gain NetSuite or Calendly skills — it only gets the system prompt of the specialist AI config.

Use Specialist Agents for: swapping tone or expertise within the same integration context.

Use Section Jumps for: switching between integrations (NetSuite → Calendly → BigCommerce).

---

Prerequisites

Before the workflow runs, each integration must be connected:

• NetSuite AI: Integrations → NetSuite → add credentials. Select the config in the NetSuite AI node.
• BigCommerce AI: Integrations → BigCommerce → connect store. Select config in node.
• Calendly AI: Integrations → Calendly → add Personal Access Token, select default event type. No config picker on node — it uses the site's connected Calendly account automatically.

---

Troubleshooting

AI never jumps to another section

The "Jump here when the customer…" text is too vague or doesn't match what visitors say. Use specific natural language matching real visitor phrasing. The auto-suggest fills in a good default — start from that.

NetSuite AI has no order lookup tools

The NetSuite Config is not selected on the node, or the NetSuite integration is not connected in Integrations → NetSuite.

Calendly AI can't create links

Calendly integration is not connected in Integrations → Calendly, or EnableCalendlySkills is not enabled on the site subscription.

After a jump the conversation history is lost

It is not lost. Each jump starts a fresh AI session but the full conversation history on the chat thread is preserved. The new AI can see all prior messages.

AI keeps jumping in circles

Each AI node is jumping before resolving the visitor's question. Make the "Jump here when the customer…" text more specific — add "after resolving their current question" or "only if the topic completely changes."