Crescora Flow | Enterprise AI Agent Platform

Full Node Combination Matrix

Source node to target node guidance with recommendation level, risk, and setup notes.

RecommendedConditionalAvoid

Start (start) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Message	recommended	Use this when the journey should first begins the conversation flow and defines where every user journey starts and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the Start to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require Start before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	recommended	Use this when the journey should first begins the conversation flow and defines where every user journey starts and then asks a question and splits users into two clear paths.	Main risk is missing fallback, timeout, or error coverage around the Start to Decision transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
FAQ	conditional	Use this when business rules require Start before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Start before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require Start before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Start before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Start before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Start before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	recommended	Use this when the journey should first begins the conversation flow and defines where every user journey starts and then stores or updates key values used later in the flow.	Main risk is missing fallback, timeout, or error coverage around the Start to Set Variable transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Human Handover	conditional	Use this when business rules require Start before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require Start before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	recommended	Use this when the journey should first begins the conversation flow and defines where every user journey starts and then routes users to different branches based on one variable value.	Main risk is missing fallback, timeout, or error coverage around the Start to Switch / Router transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Condition	conditional	Use this when business rules require Start before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Start before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Start before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	recommended	Use this when the journey should first begins the conversation flow and defines where every user journey starts and then classifies user intent and routes to the matching journey.	Main risk is missing fallback, timeout, or error coverage around the Start to Intent Router transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
AI Extract	conditional	Use this when business rules require Start before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Start before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Start before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Start before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Start before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Message (message) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Message.	High risk of confusing flow logic, dead-end paths, or poor user experience if Message routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Media	recommended	Use this when the journey should first sends one or more text messages to the user and then shares an image, file, video, audio, or document with optional caption.	Main risk is missing fallback, timeout, or error coverage around the Message to Media transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Decision	recommended	Use this when the journey should first sends one or more text messages to the user and then asks a question and splits users into two clear paths.	Main risk is missing fallback, timeout, or error coverage around the Message to Decision transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
FAQ	conditional	Use this when business rules require Message before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Message before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	recommended	Use this when the journey should first sends one or more text messages to the user and then collects user text and stores it in a variable for later use.	Main risk is missing fallback, timeout, or error coverage around the Message to User Input transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Delay	conditional	Use this when business rules require Message before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Message before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Message before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Message before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require Message before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require Message before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Message before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Message before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Message before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Message before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Message before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Message before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Message before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Message before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Message before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Message before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Media (media) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Media.	High risk of confusing flow logic, dead-end paths, or poor user experience if Media routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Media before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	recommended	Use this when the journey should first shares an image, file, video, audio, or document with optional caption and then asks a question and splits users into two clear paths.	Main risk is missing fallback, timeout, or error coverage around the Media to Decision transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
FAQ	conditional	Use this when business rules require Media before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Media before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	recommended	Use this when the journey should first shares an image, file, video, audio, or document with optional caption and then collects user text and stores it in a variable for later use.	Main risk is missing fallback, timeout, or error coverage around the Media to User Input transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Delay	conditional	Use this when business rules require Media before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Media before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Media before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Media before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require Media before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require Media before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Media before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Media before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Media before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Media before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Media before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Media before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Media before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Media before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Media before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Media before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Decision (decision) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Decision.	High risk of confusing flow logic, dead-end paths, or poor user experience if Decision routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Decision before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require Decision before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Decision before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	recommended	Use this when the journey should first asks a question and splits users into two clear paths and then fetches or sends data to external systems and maps results into variables.	Main risk is missing fallback, timeout, or error coverage around the Decision to API Call transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
User Input	conditional	Use this when business rules require Decision before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Decision before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Decision before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Decision before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	recommended	Use this when the journey should first asks a question and splits users into two clear paths and then stores or updates key values used later in the flow.	Main risk is missing fallback, timeout, or error coverage around the Decision to Set Variable transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Human Handover	recommended	Use this when the journey should first asks a question and splits users into two clear paths and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the Decision to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	conditional	Use this when business rules require Decision before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Decision before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Decision before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Decision before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Decision before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Decision before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Decision before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Decision before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Decision before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Decision before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Decision before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

FAQ (faq) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after FAQ.	High risk of confusing flow logic, dead-end paths, or poor user experience if FAQ routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require FAQ before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require FAQ before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require FAQ before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require FAQ before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require FAQ before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require FAQ before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require FAQ before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require FAQ before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require FAQ before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	recommended	Use this when the journey should first responds using pre-configured FAQ knowledge behavior and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the FAQ to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	recommended	Use this when the journey should first responds using pre-configured FAQ knowledge behavior and then provides a safe default response when the bot cannot understand or route properly.	Main risk is missing fallback, timeout, or error coverage around the FAQ to Fallback transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Switch / Router	conditional	Use this when business rules require FAQ before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require FAQ before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require FAQ before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require FAQ before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require FAQ before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require FAQ before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require FAQ before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require FAQ before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require FAQ before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require FAQ before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

API Call (api) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after API Call.	High risk of confusing flow logic, dead-end paths, or poor user experience if API Call routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	recommended	Use this when the journey should first fetches or sends data to external systems and maps results into variables and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the API Call to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require API Call before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require API Call before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require API Call before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require API Call before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require API Call before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require API Call before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require API Call before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	recommended	Use this when the journey should first fetches or sends data to external systems and maps results into variables and then stores or updates key values used later in the flow.	Main risk is missing fallback, timeout, or error coverage around the API Call to Set Variable transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Human Handover	conditional	Use this when business rules require API Call before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require API Call before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	recommended	Use this when the journey should first fetches or sends data to external systems and maps results into variables and then routes users to different branches based on one variable value.	Main risk is missing fallback, timeout, or error coverage around the API Call to Switch / Router transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Condition	recommended	Use this when the journey should first fetches or sends data to external systems and maps results into variables and then evaluates a rule (equals, contains, regex) to choose next behavior.	Main risk is missing fallback, timeout, or error coverage around the API Call to Condition transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Loop	conditional	Use this when business rules require API Call before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require API Call before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require API Call before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require API Call before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	recommended	Use this when the journey should first fetches or sends data to external systems and maps results into variables and then handles failures gracefully with user-safe messaging and recovery path.	Main risk is missing fallback, timeout, or error coverage around the API Call to Error Handler transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
AI Sentiment	conditional	Use this when business rules require API Call before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require API Call before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require API Call before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

User Input (input) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after User Input.	High risk of confusing flow logic, dead-end paths, or poor user experience if User Input routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require User Input before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require User Input before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require User Input before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require User Input before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require User Input before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require User Input before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require User Input before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	recommended	Use this when the journey should first collects user text and stores it in a variable for later use and then repeats a step a limited number of times before failing safely.	Main risk is missing fallback, timeout, or error coverage around the User Input to Retry transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Set Variable	recommended	Use this when the journey should first collects user text and stores it in a variable for later use and then stores or updates key values used later in the flow.	Main risk is missing fallback, timeout, or error coverage around the User Input to Set Variable transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Human Handover	conditional	Use this when business rules require User Input before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require User Input before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require User Input before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	recommended	Use this when the journey should first collects user text and stores it in a variable for later use and then evaluates a rule (equals, contains, regex) to choose next behavior.	Main risk is missing fallback, timeout, or error coverage around the User Input to Condition transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Loop	conditional	Use this when business rules require User Input before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require User Input before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require User Input before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	recommended	Use this when the journey should first collects user text and stores it in a variable for later use and then extracts structured fields from user text based on a schema.	Main risk is missing fallback, timeout, or error coverage around the User Input to AI Extract transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Error Handler	conditional	Use this when business rules require User Input before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require User Input before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require User Input before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require User Input before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Delay (delay) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Delay.	High risk of confusing flow logic, dead-end paths, or poor user experience if Delay routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	recommended	Use this when the journey should first pauses the flow for a configured number of milliseconds and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the Delay to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require Delay before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Delay before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Delay before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	recommended	Use this when the journey should first pauses the flow for a configured number of milliseconds and then fetches or sends data to external systems and maps results into variables.	Main risk is missing fallback, timeout, or error coverage around the Delay to API Call transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
User Input	conditional	Use this when business rules require Delay before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Delay before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Delay before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Delay before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require Delay before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require Delay before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Delay before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Delay before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Delay before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Delay before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Delay before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Delay before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Delay before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Delay before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Delay before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Delay before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Timeout (timeout) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Timeout.	High risk of confusing flow logic, dead-end paths, or poor user experience if Timeout routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Timeout before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require Timeout before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Timeout before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Timeout before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Timeout before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require Timeout before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Timeout before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Timeout before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Timeout before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	recommended	Use this when the journey should first waits for user response and routes based on a time limit and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the Timeout to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	recommended	Use this when the journey should first waits for user response and routes based on a time limit and then provides a safe default response when the bot cannot understand or route properly.	Main risk is missing fallback, timeout, or error coverage around the Timeout to Fallback transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Switch / Router	conditional	Use this when business rules require Timeout before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Timeout before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Timeout before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Timeout before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Timeout before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Timeout before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Timeout before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Timeout before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Timeout before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Timeout before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Retry (retry) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Retry.	High risk of confusing flow logic, dead-end paths, or poor user experience if Retry routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Retry before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require Retry before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Retry before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Retry before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	recommended	Use this when the journey should first repeats a step a limited number of times before failing safely and then fetches or sends data to external systems and maps results into variables.	Main risk is missing fallback, timeout, or error coverage around the Retry to API Call transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
User Input	recommended	Use this when the journey should first repeats a step a limited number of times before failing safely and then collects user text and stores it in a variable for later use.	Main risk is missing fallback, timeout, or error coverage around the Retry to User Input transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Delay	conditional	Use this when business rules require Retry before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Retry before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Retry before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require Retry before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require Retry before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Retry before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Retry before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Retry before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Retry before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Retry before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Retry before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	recommended	Use this when the journey should first repeats a step a limited number of times before failing safely and then handles failures gracefully with user-safe messaging and recovery path.	Main risk is missing fallback, timeout, or error coverage around the Retry to Error Handler transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
AI Sentiment	conditional	Use this when business rules require Retry before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Retry before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Retry before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Set Variable (setVariable) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Set Variable.	High risk of confusing flow logic, dead-end paths, or poor user experience if Set Variable routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Set Variable before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require Set Variable before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Set Variable before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Set Variable before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	recommended	Use this when the journey should first stores or updates key values used later in the flow and then fetches or sends data to external systems and maps results into variables.	Main risk is missing fallback, timeout, or error coverage around the Set Variable to API Call transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
User Input	conditional	Use this when business rules require Set Variable before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Set Variable before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Set Variable before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Set Variable before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require Set Variable before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require Set Variable before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	recommended	Use this when the journey should first stores or updates key values used later in the flow and then routes users to different branches based on one variable value.	Main risk is missing fallback, timeout, or error coverage around the Set Variable to Switch / Router transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Condition	conditional	Use this when business rules require Set Variable before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Set Variable before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Set Variable before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Set Variable before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Set Variable before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Set Variable before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Set Variable before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Set Variable before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	recommended	Use this when the journey should first stores or updates key values used later in the flow and then generates dynamic text from a prompt template and optional variables.	Main risk is missing fallback, timeout, or error coverage around the Set Variable to AI Generate transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.

Human Handover (handover) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	avoid	Use only in exceptional cases; this handoff is usually weaker because Message is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Message.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Media	avoid	Use only in exceptional cases; this handoff is usually weaker because Media is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Media.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Decision	avoid	Use only in exceptional cases; this handoff is usually weaker because Decision is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Decision.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
FAQ	avoid	Use only in exceptional cases; this handoff is usually weaker because FAQ is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to FAQ.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
API Call	avoid	Use only in exceptional cases; this handoff is usually weaker because API Call is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to API Call.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
User Input	avoid	Use only in exceptional cases; this handoff is usually weaker because User Input is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to User Input.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Delay	avoid	Use only in exceptional cases; this handoff is usually weaker because Delay is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Delay.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Timeout	avoid	Use only in exceptional cases; this handoff is usually weaker because Timeout is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Timeout.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Retry	avoid	Use only in exceptional cases; this handoff is usually weaker because Retry is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Retry.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Set Variable	avoid	Use only in exceptional cases; this handoff is usually weaker because Set Variable is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Set Variable.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Fallback	avoid	Use only in exceptional cases; this handoff is usually weaker because Fallback is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Fallback.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Switch / Router	avoid	Use only in exceptional cases; this handoff is usually weaker because Switch / Router is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Switch / Router.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Condition	avoid	Use only in exceptional cases; this handoff is usually weaker because Condition is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Condition.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Loop	avoid	Use only in exceptional cases; this handoff is usually weaker because Loop is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Loop.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
End	recommended	Use this when the journey should first transfers the conversation to a human or external support channel and then closes the journey with a final confirmation or closing message.	Main risk is missing fallback, timeout, or error coverage around the Human Handover to End transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Intent Router	avoid	Use only in exceptional cases; this handoff is usually weaker because Intent Router is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Intent Router.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Extract	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Extract is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to AI Extract.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Error Handler	avoid	Use only in exceptional cases; this handoff is usually weaker because Error Handler is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Error Handler.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Sentiment	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Sentiment is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to AI Sentiment.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Memory	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Memory is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to AI Memory.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Generate	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Generate is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to AI Generate.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.

Fallback (fallback) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Fallback.	High risk of confusing flow logic, dead-end paths, or poor user experience if Fallback routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Fallback before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require Fallback before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Fallback before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Fallback before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Fallback before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	recommended	Use this when the journey should first provides a safe default response when the bot cannot understand or route properly and then collects user text and stores it in a variable for later use.	Main risk is missing fallback, timeout, or error coverage around the Fallback to User Input transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Delay	conditional	Use this when business rules require Fallback before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Fallback before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Fallback before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Fallback before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	recommended	Use this when the journey should first provides a safe default response when the bot cannot understand or route properly and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the Fallback to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Switch / Router	conditional	Use this when business rules require Fallback before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Fallback before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Fallback before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Fallback before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	recommended	Use this when the journey should first provides a safe default response when the bot cannot understand or route properly and then classifies user intent and routes to the matching journey.	Main risk is missing fallback, timeout, or error coverage around the Fallback to Intent Router transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
AI Extract	conditional	Use this when business rules require Fallback before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Fallback before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Fallback before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Fallback before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Fallback before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Switch / Router (switch) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Switch / Router.	High risk of confusing flow logic, dead-end paths, or poor user experience if Switch / Router routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	recommended	Use this when the journey should first routes users to different branches based on one variable value and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the Switch / Router to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require Switch / Router before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Switch / Router before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Switch / Router before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	recommended	Use this when the journey should first routes users to different branches based on one variable value and then fetches or sends data to external systems and maps results into variables.	Main risk is missing fallback, timeout, or error coverage around the Switch / Router to API Call transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
User Input	conditional	Use this when business rules require Switch / Router before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Switch / Router before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Switch / Router before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Switch / Router before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Switch / Router before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require Switch / Router before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require Switch / Router before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Switch / Router before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Switch / Router before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	recommended	Use this when the journey should first routes users to different branches based on one variable value and then closes the journey with a final confirmation or closing message.	Main risk is missing fallback, timeout, or error coverage around the Switch / Router to End transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Intent Router	conditional	Use this when business rules require Switch / Router before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Switch / Router before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Switch / Router before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Switch / Router before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Switch / Router before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Switch / Router before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Condition (condition) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Condition.	High risk of confusing flow logic, dead-end paths, or poor user experience if Condition routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	recommended	Use this when the journey should first evaluates a rule (equals, contains, regex) to choose next behavior and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the Condition to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require Condition before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Condition before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Condition before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Condition before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require Condition before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Condition before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Condition before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	recommended	Use this when the journey should first evaluates a rule (equals, contains, regex) to choose next behavior and then repeats a step a limited number of times before failing safely.	Main risk is missing fallback, timeout, or error coverage around the Condition to Retry transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Set Variable	conditional	Use this when business rules require Condition before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	recommended	Use this when the journey should first evaluates a rule (equals, contains, regex) to choose next behavior and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the Condition to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	conditional	Use this when business rules require Condition before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Condition before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Condition before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Condition before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Condition before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Condition before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Condition before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Condition before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Condition before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Condition before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Loop (loop) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Loop.	High risk of confusing flow logic, dead-end paths, or poor user experience if Loop routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Loop before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require Loop before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Loop before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Loop before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Loop before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	recommended	Use this when the journey should first repeats a sequence for a fixed number of times and then collects user text and stores it in a variable for later use.	Main risk is missing fallback, timeout, or error coverage around the Loop to User Input transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Delay	conditional	Use this when business rules require Loop before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Loop before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Loop before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Loop before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	recommended	Use this when the journey should first repeats a sequence for a fixed number of times and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the Loop to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	conditional	Use this when business rules require Loop before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Loop before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	recommended	Use this when the journey should first repeats a sequence for a fixed number of times and then evaluates a rule (equals, contains, regex) to choose next behavior.	Main risk is missing fallback, timeout, or error coverage around the Loop to Condition transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
End	conditional	Use this when business rules require Loop before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Loop before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Loop before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Loop before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Loop before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Loop before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Loop before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

End (end) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	avoid	Use only in exceptional cases; this handoff is usually weaker because Message is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Message.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Media	avoid	Use only in exceptional cases; this handoff is usually weaker because Media is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Media.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Decision	avoid	Use only in exceptional cases; this handoff is usually weaker because Decision is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Decision.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
FAQ	avoid	Use only in exceptional cases; this handoff is usually weaker because FAQ is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to FAQ.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
API Call	avoid	Use only in exceptional cases; this handoff is usually weaker because API Call is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to API Call.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
User Input	avoid	Use only in exceptional cases; this handoff is usually weaker because User Input is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to User Input.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Delay	avoid	Use only in exceptional cases; this handoff is usually weaker because Delay is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Delay.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Timeout	avoid	Use only in exceptional cases; this handoff is usually weaker because Timeout is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Timeout.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Retry	avoid	Use only in exceptional cases; this handoff is usually weaker because Retry is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Retry.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Set Variable	avoid	Use only in exceptional cases; this handoff is usually weaker because Set Variable is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Set Variable.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Human Handover	avoid	Use only in exceptional cases; this handoff is usually weaker because Human Handover is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Human Handover.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Fallback	avoid	Use only in exceptional cases; this handoff is usually weaker because Fallback is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Fallback.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Switch / Router	avoid	Use only in exceptional cases; this handoff is usually weaker because Switch / Router is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Switch / Router.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Condition	avoid	Use only in exceptional cases; this handoff is usually weaker because Condition is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Condition.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Loop	avoid	Use only in exceptional cases; this handoff is usually weaker because Loop is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Loop.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Intent Router	avoid	Use only in exceptional cases; this handoff is usually weaker because Intent Router is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Intent Router.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Extract	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Extract is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to AI Extract.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Error Handler	avoid	Use only in exceptional cases; this handoff is usually weaker because Error Handler is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Error Handler.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Sentiment	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Sentiment is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to AI Sentiment.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Memory	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Memory is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to AI Memory.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Generate	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Generate is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to AI Generate.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.

Intent Router (intent-router) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Intent Router.	High risk of confusing flow logic, dead-end paths, or poor user experience if Intent Router routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Intent Router before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require Intent Router before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Intent Router before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	recommended	Use this when the journey should first classifies user intent and routes to the matching journey and then responds using pre-configured FAQ knowledge behavior.	Main risk is missing fallback, timeout, or error coverage around the Intent Router to FAQ transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
API Call	recommended	Use this when the journey should first classifies user intent and routes to the matching journey and then fetches or sends data to external systems and maps results into variables.	Main risk is missing fallback, timeout, or error coverage around the Intent Router to API Call transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
User Input	conditional	Use this when business rules require Intent Router before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Intent Router before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Intent Router before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Intent Router before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Intent Router before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require Intent Router before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	recommended	Use this when the journey should first classifies user intent and routes to the matching journey and then provides a safe default response when the bot cannot understand or route properly.	Main risk is missing fallback, timeout, or error coverage around the Intent Router to Fallback transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Switch / Router	conditional	Use this when business rules require Intent Router before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Intent Router before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Intent Router before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Intent Router before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Intent Router before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Intent Router before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Intent Router before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Intent Router before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Intent Router before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

AI Extract (ai-extract) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after AI Extract.	High risk of confusing flow logic, dead-end paths, or poor user experience if AI Extract routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require AI Extract before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require AI Extract before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require AI Extract before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require AI Extract before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	recommended	Use this when the journey should first extracts structured fields from user text based on a schema and then fetches or sends data to external systems and maps results into variables.	Main risk is missing fallback, timeout, or error coverage around the AI Extract to API Call transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
User Input	conditional	Use this when business rules require AI Extract before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require AI Extract before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require AI Extract before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require AI Extract before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	recommended	Use this when the journey should first extracts structured fields from user text based on a schema and then stores or updates key values used later in the flow.	Main risk is missing fallback, timeout, or error coverage around the AI Extract to Set Variable transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Human Handover	conditional	Use this when business rules require AI Extract before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require AI Extract before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require AI Extract before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	recommended	Use this when the journey should first extracts structured fields from user text based on a schema and then evaluates a rule (equals, contains, regex) to choose next behavior.	Main risk is missing fallback, timeout, or error coverage around the AI Extract to Condition transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Loop	conditional	Use this when business rules require AI Extract before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require AI Extract before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require AI Extract before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require AI Extract before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require AI Extract before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require AI Extract before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require AI Extract before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Error Handler (error) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Error Handler.	High risk of confusing flow logic, dead-end paths, or poor user experience if Error Handler routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	recommended	Use this when the journey should first handles failures gracefully with user-safe messaging and recovery path and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the Error Handler to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require Error Handler before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Error Handler before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Error Handler before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Error Handler before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require Error Handler before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Error Handler before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Error Handler before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Error Handler before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Error Handler before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	recommended	Use this when the journey should first handles failures gracefully with user-safe messaging and recovery path and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the Error Handler to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	conditional	Use this when business rules require Error Handler before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Error Handler before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Error Handler before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Error Handler before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	recommended	Use this when the journey should first handles failures gracefully with user-safe messaging and recovery path and then closes the journey with a final confirmation or closing message.	Main risk is missing fallback, timeout, or error coverage around the Error Handler to End transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Intent Router	conditional	Use this when business rules require Error Handler before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Error Handler before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Error Handler before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Error Handler before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Error Handler before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

AI Sentiment (ai-sentiment) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after AI Sentiment.	High risk of confusing flow logic, dead-end paths, or poor user experience if AI Sentiment routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	recommended	Use this when the journey should first detects conversation sentiment to adapt tone and escalation decisions and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the AI Sentiment to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require AI Sentiment before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require AI Sentiment before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require AI Sentiment before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require AI Sentiment before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require AI Sentiment before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require AI Sentiment before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require AI Sentiment before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require AI Sentiment before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	recommended	Use this when the journey should first detects conversation sentiment to adapt tone and escalation decisions and then stores or updates key values used later in the flow.	Main risk is missing fallback, timeout, or error coverage around the AI Sentiment to Set Variable transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Human Handover	recommended	Use this when the journey should first detects conversation sentiment to adapt tone and escalation decisions and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the AI Sentiment to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	conditional	Use this when business rules require AI Sentiment before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require AI Sentiment before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require AI Sentiment before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require AI Sentiment before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require AI Sentiment before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require AI Sentiment before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require AI Sentiment before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require AI Sentiment before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require AI Sentiment before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require AI Sentiment before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

AI Memory (ai-memory) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after AI Memory.	High risk of confusing flow logic, dead-end paths, or poor user experience if AI Memory routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require AI Memory before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require AI Memory before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require AI Memory before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require AI Memory before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require AI Memory before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require AI Memory before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require AI Memory before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require AI Memory before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require AI Memory before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require AI Memory before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	recommended	Use this when the journey should first stores selected user context so future responses can stay personalized and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the AI Memory to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	conditional	Use this when business rules require AI Memory before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	recommended	Use this when the journey should first stores selected user context so future responses can stay personalized and then routes users to different branches based on one variable value.	Main risk is missing fallback, timeout, or error coverage around the AI Memory to Switch / Router transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Condition	conditional	Use this when business rules require AI Memory before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require AI Memory before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require AI Memory before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require AI Memory before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require AI Memory before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require AI Memory before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require AI Memory before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	recommended	Use this when the journey should first stores selected user context so future responses can stay personalized and then generates dynamic text from a prompt template and optional variables.	Main risk is missing fallback, timeout, or error coverage around the AI Memory to AI Generate transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.

AI Generate (ai-generate) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after AI Generate.	High risk of confusing flow logic, dead-end paths, or poor user experience if AI Generate routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	recommended	Use this when the journey should first generates dynamic text from a prompt template and optional variables and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the AI Generate to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require AI Generate before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require AI Generate before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require AI Generate before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require AI Generate before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require AI Generate before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require AI Generate before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require AI Generate before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require AI Generate before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require AI Generate before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require AI Generate before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require AI Generate before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require AI Generate before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	recommended	Use this when the journey should first generates dynamic text from a prompt template and optional variables and then evaluates a rule (equals, contains, regex) to choose next behavior.	Main risk is missing fallback, timeout, or error coverage around the AI Generate to Condition transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Loop	conditional	Use this when business rules require AI Generate before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require AI Generate before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require AI Generate before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require AI Generate before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require AI Generate before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require AI Generate before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	recommended	Use this when the journey should first generates dynamic text from a prompt template and optional variables and then stores selected user context so future responses can stay personalized.	Main risk is missing fallback, timeout, or error coverage around the AI Generate to AI Memory transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.

Full Node Combination Matrix

Source node to target node guidance with recommendation level, risk, and setup notes.

RecommendedConditionalAvoid

Start (start) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Message	recommended	Use this when the journey should first begins the conversation flow and defines where every user journey starts and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the Start to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require Start before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	recommended	Use this when the journey should first begins the conversation flow and defines where every user journey starts and then asks a question and splits users into two clear paths.	Main risk is missing fallback, timeout, or error coverage around the Start to Decision transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
FAQ	conditional	Use this when business rules require Start before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Start before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require Start before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Start before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Start before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Start before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	recommended	Use this when the journey should first begins the conversation flow and defines where every user journey starts and then stores or updates key values used later in the flow.	Main risk is missing fallback, timeout, or error coverage around the Start to Set Variable transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Human Handover	conditional	Use this when business rules require Start before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require Start before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	recommended	Use this when the journey should first begins the conversation flow and defines where every user journey starts and then routes users to different branches based on one variable value.	Main risk is missing fallback, timeout, or error coverage around the Start to Switch / Router transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Condition	conditional	Use this when business rules require Start before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Start before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Start before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	recommended	Use this when the journey should first begins the conversation flow and defines where every user journey starts and then classifies user intent and routes to the matching journey.	Main risk is missing fallback, timeout, or error coverage around the Start to Intent Router transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
AI Extract	conditional	Use this when business rules require Start before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Start before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Start before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Start before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Start before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Message (message) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Message.	High risk of confusing flow logic, dead-end paths, or poor user experience if Message routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Media	recommended	Use this when the journey should first sends one or more text messages to the user and then shares an image, file, video, audio, or document with optional caption.	Main risk is missing fallback, timeout, or error coverage around the Message to Media transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Decision	recommended	Use this when the journey should first sends one or more text messages to the user and then asks a question and splits users into two clear paths.	Main risk is missing fallback, timeout, or error coverage around the Message to Decision transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
FAQ	conditional	Use this when business rules require Message before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Message before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	recommended	Use this when the journey should first sends one or more text messages to the user and then collects user text and stores it in a variable for later use.	Main risk is missing fallback, timeout, or error coverage around the Message to User Input transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Delay	conditional	Use this when business rules require Message before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Message before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Message before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Message before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require Message before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require Message before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Message before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Message before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Message before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Message before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Message before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Message before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Message before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Message before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Message before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Message before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Media (media) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Media.	High risk of confusing flow logic, dead-end paths, or poor user experience if Media routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Media before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	recommended	Use this when the journey should first shares an image, file, video, audio, or document with optional caption and then asks a question and splits users into two clear paths.	Main risk is missing fallback, timeout, or error coverage around the Media to Decision transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
FAQ	conditional	Use this when business rules require Media before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Media before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	recommended	Use this when the journey should first shares an image, file, video, audio, or document with optional caption and then collects user text and stores it in a variable for later use.	Main risk is missing fallback, timeout, or error coverage around the Media to User Input transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Delay	conditional	Use this when business rules require Media before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Media before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Media before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Media before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require Media before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require Media before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Media before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Media before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Media before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Media before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Media before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Media before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Media before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Media before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Media before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Media before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Decision (decision) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Decision.	High risk of confusing flow logic, dead-end paths, or poor user experience if Decision routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Decision before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require Decision before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Decision before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	recommended	Use this when the journey should first asks a question and splits users into two clear paths and then fetches or sends data to external systems and maps results into variables.	Main risk is missing fallback, timeout, or error coverage around the Decision to API Call transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
User Input	conditional	Use this when business rules require Decision before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Decision before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Decision before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Decision before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	recommended	Use this when the journey should first asks a question and splits users into two clear paths and then stores or updates key values used later in the flow.	Main risk is missing fallback, timeout, or error coverage around the Decision to Set Variable transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Human Handover	recommended	Use this when the journey should first asks a question and splits users into two clear paths and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the Decision to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	conditional	Use this when business rules require Decision before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Decision before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Decision before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Decision before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Decision before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Decision before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Decision before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Decision before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Decision before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Decision before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Decision before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

FAQ (faq) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after FAQ.	High risk of confusing flow logic, dead-end paths, or poor user experience if FAQ routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require FAQ before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require FAQ before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require FAQ before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require FAQ before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require FAQ before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require FAQ before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require FAQ before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require FAQ before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require FAQ before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	recommended	Use this when the journey should first responds using pre-configured FAQ knowledge behavior and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the FAQ to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	recommended	Use this when the journey should first responds using pre-configured FAQ knowledge behavior and then provides a safe default response when the bot cannot understand or route properly.	Main risk is missing fallback, timeout, or error coverage around the FAQ to Fallback transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Switch / Router	conditional	Use this when business rules require FAQ before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require FAQ before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require FAQ before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require FAQ before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require FAQ before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require FAQ before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require FAQ before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require FAQ before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require FAQ before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require FAQ before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

API Call (api) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after API Call.	High risk of confusing flow logic, dead-end paths, or poor user experience if API Call routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	recommended	Use this when the journey should first fetches or sends data to external systems and maps results into variables and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the API Call to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require API Call before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require API Call before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require API Call before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require API Call before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require API Call before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require API Call before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require API Call before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	recommended	Use this when the journey should first fetches or sends data to external systems and maps results into variables and then stores or updates key values used later in the flow.	Main risk is missing fallback, timeout, or error coverage around the API Call to Set Variable transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Human Handover	conditional	Use this when business rules require API Call before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require API Call before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	recommended	Use this when the journey should first fetches or sends data to external systems and maps results into variables and then routes users to different branches based on one variable value.	Main risk is missing fallback, timeout, or error coverage around the API Call to Switch / Router transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Condition	recommended	Use this when the journey should first fetches or sends data to external systems and maps results into variables and then evaluates a rule (equals, contains, regex) to choose next behavior.	Main risk is missing fallback, timeout, or error coverage around the API Call to Condition transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Loop	conditional	Use this when business rules require API Call before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require API Call before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require API Call before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require API Call before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	recommended	Use this when the journey should first fetches or sends data to external systems and maps results into variables and then handles failures gracefully with user-safe messaging and recovery path.	Main risk is missing fallback, timeout, or error coverage around the API Call to Error Handler transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
AI Sentiment	conditional	Use this when business rules require API Call before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require API Call before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require API Call before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

User Input (input) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after User Input.	High risk of confusing flow logic, dead-end paths, or poor user experience if User Input routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require User Input before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require User Input before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require User Input before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require User Input before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require User Input before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require User Input before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require User Input before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	recommended	Use this when the journey should first collects user text and stores it in a variable for later use and then repeats a step a limited number of times before failing safely.	Main risk is missing fallback, timeout, or error coverage around the User Input to Retry transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Set Variable	recommended	Use this when the journey should first collects user text and stores it in a variable for later use and then stores or updates key values used later in the flow.	Main risk is missing fallback, timeout, or error coverage around the User Input to Set Variable transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Human Handover	conditional	Use this when business rules require User Input before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require User Input before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require User Input before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	recommended	Use this when the journey should first collects user text and stores it in a variable for later use and then evaluates a rule (equals, contains, regex) to choose next behavior.	Main risk is missing fallback, timeout, or error coverage around the User Input to Condition transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Loop	conditional	Use this when business rules require User Input before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require User Input before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require User Input before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	recommended	Use this when the journey should first collects user text and stores it in a variable for later use and then extracts structured fields from user text based on a schema.	Main risk is missing fallback, timeout, or error coverage around the User Input to AI Extract transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Error Handler	conditional	Use this when business rules require User Input before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require User Input before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require User Input before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require User Input before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Delay (delay) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Delay.	High risk of confusing flow logic, dead-end paths, or poor user experience if Delay routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	recommended	Use this when the journey should first pauses the flow for a configured number of milliseconds and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the Delay to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require Delay before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Delay before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Delay before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	recommended	Use this when the journey should first pauses the flow for a configured number of milliseconds and then fetches or sends data to external systems and maps results into variables.	Main risk is missing fallback, timeout, or error coverage around the Delay to API Call transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
User Input	conditional	Use this when business rules require Delay before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Delay before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Delay before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Delay before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require Delay before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require Delay before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Delay before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Delay before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Delay before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Delay before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Delay before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Delay before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Delay before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Delay before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Delay before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Delay before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Timeout (timeout) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Timeout.	High risk of confusing flow logic, dead-end paths, or poor user experience if Timeout routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Timeout before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require Timeout before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Timeout before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Timeout before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Timeout before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require Timeout before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Timeout before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Timeout before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Timeout before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	recommended	Use this when the journey should first waits for user response and routes based on a time limit and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the Timeout to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	recommended	Use this when the journey should first waits for user response and routes based on a time limit and then provides a safe default response when the bot cannot understand or route properly.	Main risk is missing fallback, timeout, or error coverage around the Timeout to Fallback transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Switch / Router	conditional	Use this when business rules require Timeout before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Timeout before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Timeout before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Timeout before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Timeout before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Timeout before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Timeout before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Timeout before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Timeout before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Timeout before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Retry (retry) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Retry.	High risk of confusing flow logic, dead-end paths, or poor user experience if Retry routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Retry before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require Retry before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Retry before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Retry before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	recommended	Use this when the journey should first repeats a step a limited number of times before failing safely and then fetches or sends data to external systems and maps results into variables.	Main risk is missing fallback, timeout, or error coverage around the Retry to API Call transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
User Input	recommended	Use this when the journey should first repeats a step a limited number of times before failing safely and then collects user text and stores it in a variable for later use.	Main risk is missing fallback, timeout, or error coverage around the Retry to User Input transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Delay	conditional	Use this when business rules require Retry before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Retry before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Retry before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require Retry before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require Retry before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Retry before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Retry before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Retry before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Retry before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Retry before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Retry before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	recommended	Use this when the journey should first repeats a step a limited number of times before failing safely and then handles failures gracefully with user-safe messaging and recovery path.	Main risk is missing fallback, timeout, or error coverage around the Retry to Error Handler transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
AI Sentiment	conditional	Use this when business rules require Retry before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Retry before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Retry before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Set Variable (setVariable) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Set Variable.	High risk of confusing flow logic, dead-end paths, or poor user experience if Set Variable routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Set Variable before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require Set Variable before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Set Variable before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Set Variable before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	recommended	Use this when the journey should first stores or updates key values used later in the flow and then fetches or sends data to external systems and maps results into variables.	Main risk is missing fallback, timeout, or error coverage around the Set Variable to API Call transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
User Input	conditional	Use this when business rules require Set Variable before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Set Variable before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Set Variable before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Set Variable before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require Set Variable before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require Set Variable before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	recommended	Use this when the journey should first stores or updates key values used later in the flow and then routes users to different branches based on one variable value.	Main risk is missing fallback, timeout, or error coverage around the Set Variable to Switch / Router transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Condition	conditional	Use this when business rules require Set Variable before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Set Variable before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Set Variable before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Set Variable before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Set Variable before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Set Variable before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Set Variable before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Set Variable before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	recommended	Use this when the journey should first stores or updates key values used later in the flow and then generates dynamic text from a prompt template and optional variables.	Main risk is missing fallback, timeout, or error coverage around the Set Variable to AI Generate transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.

Human Handover (handover) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	avoid	Use only in exceptional cases; this handoff is usually weaker because Message is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Message.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Media	avoid	Use only in exceptional cases; this handoff is usually weaker because Media is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Media.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Decision	avoid	Use only in exceptional cases; this handoff is usually weaker because Decision is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Decision.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
FAQ	avoid	Use only in exceptional cases; this handoff is usually weaker because FAQ is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to FAQ.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
API Call	avoid	Use only in exceptional cases; this handoff is usually weaker because API Call is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to API Call.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
User Input	avoid	Use only in exceptional cases; this handoff is usually weaker because User Input is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to User Input.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Delay	avoid	Use only in exceptional cases; this handoff is usually weaker because Delay is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Delay.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Timeout	avoid	Use only in exceptional cases; this handoff is usually weaker because Timeout is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Timeout.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Retry	avoid	Use only in exceptional cases; this handoff is usually weaker because Retry is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Retry.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Set Variable	avoid	Use only in exceptional cases; this handoff is usually weaker because Set Variable is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Set Variable.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Fallback	avoid	Use only in exceptional cases; this handoff is usually weaker because Fallback is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Fallback.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Switch / Router	avoid	Use only in exceptional cases; this handoff is usually weaker because Switch / Router is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Switch / Router.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Condition	avoid	Use only in exceptional cases; this handoff is usually weaker because Condition is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Condition.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Loop	avoid	Use only in exceptional cases; this handoff is usually weaker because Loop is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Loop.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
End	recommended	Use this when the journey should first transfers the conversation to a human or external support channel and then closes the journey with a final confirmation or closing message.	Main risk is missing fallback, timeout, or error coverage around the Human Handover to End transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Intent Router	avoid	Use only in exceptional cases; this handoff is usually weaker because Intent Router is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Intent Router.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Extract	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Extract is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to AI Extract.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Error Handler	avoid	Use only in exceptional cases; this handoff is usually weaker because Error Handler is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to Error Handler.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Sentiment	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Sentiment is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to AI Sentiment.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Memory	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Memory is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to AI Memory.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Generate	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Generate is not a natural next step after Human Handover.	High risk of confusing flow logic, dead-end paths, or poor user experience if Human Handover routes directly to AI Generate.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.

Fallback (fallback) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Fallback.	High risk of confusing flow logic, dead-end paths, or poor user experience if Fallback routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Fallback before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require Fallback before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Fallback before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Fallback before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Fallback before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	recommended	Use this when the journey should first provides a safe default response when the bot cannot understand or route properly and then collects user text and stores it in a variable for later use.	Main risk is missing fallback, timeout, or error coverage around the Fallback to User Input transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Delay	conditional	Use this when business rules require Fallback before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Fallback before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Fallback before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Fallback before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	recommended	Use this when the journey should first provides a safe default response when the bot cannot understand or route properly and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the Fallback to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Switch / Router	conditional	Use this when business rules require Fallback before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Fallback before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Fallback before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Fallback before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	recommended	Use this when the journey should first provides a safe default response when the bot cannot understand or route properly and then classifies user intent and routes to the matching journey.	Main risk is missing fallback, timeout, or error coverage around the Fallback to Intent Router transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
AI Extract	conditional	Use this when business rules require Fallback before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Fallback before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Fallback before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Fallback before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Fallback before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Switch / Router (switch) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Switch / Router.	High risk of confusing flow logic, dead-end paths, or poor user experience if Switch / Router routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	recommended	Use this when the journey should first routes users to different branches based on one variable value and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the Switch / Router to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require Switch / Router before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Switch / Router before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Switch / Router before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	recommended	Use this when the journey should first routes users to different branches based on one variable value and then fetches or sends data to external systems and maps results into variables.	Main risk is missing fallback, timeout, or error coverage around the Switch / Router to API Call transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
User Input	conditional	Use this when business rules require Switch / Router before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Switch / Router before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Switch / Router before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Switch / Router before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Switch / Router before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require Switch / Router before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require Switch / Router before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Switch / Router before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Switch / Router before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	recommended	Use this when the journey should first routes users to different branches based on one variable value and then closes the journey with a final confirmation or closing message.	Main risk is missing fallback, timeout, or error coverage around the Switch / Router to End transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Intent Router	conditional	Use this when business rules require Switch / Router before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Switch / Router before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Switch / Router before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Switch / Router before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Switch / Router before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Switch / Router before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Condition (condition) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Condition.	High risk of confusing flow logic, dead-end paths, or poor user experience if Condition routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	recommended	Use this when the journey should first evaluates a rule (equals, contains, regex) to choose next behavior and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the Condition to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require Condition before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Condition before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Condition before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Condition before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require Condition before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Condition before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Condition before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	recommended	Use this when the journey should first evaluates a rule (equals, contains, regex) to choose next behavior and then repeats a step a limited number of times before failing safely.	Main risk is missing fallback, timeout, or error coverage around the Condition to Retry transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Set Variable	conditional	Use this when business rules require Condition before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	recommended	Use this when the journey should first evaluates a rule (equals, contains, regex) to choose next behavior and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the Condition to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	conditional	Use this when business rules require Condition before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Condition before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Condition before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Condition before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Condition before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Condition before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Condition before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Condition before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Condition before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Condition before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Loop (loop) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Loop.	High risk of confusing flow logic, dead-end paths, or poor user experience if Loop routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Loop before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require Loop before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Loop before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Loop before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Loop before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	recommended	Use this when the journey should first repeats a sequence for a fixed number of times and then collects user text and stores it in a variable for later use.	Main risk is missing fallback, timeout, or error coverage around the Loop to User Input transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Delay	conditional	Use this when business rules require Loop before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Loop before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Loop before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Loop before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	recommended	Use this when the journey should first repeats a sequence for a fixed number of times and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the Loop to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	conditional	Use this when business rules require Loop before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Loop before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	recommended	Use this when the journey should first repeats a sequence for a fixed number of times and then evaluates a rule (equals, contains, regex) to choose next behavior.	Main risk is missing fallback, timeout, or error coverage around the Loop to Condition transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
End	conditional	Use this when business rules require Loop before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require Loop before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Loop before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Loop before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Loop before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Loop before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Loop before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

End (end) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	avoid	Use only in exceptional cases; this handoff is usually weaker because Message is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Message.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Media	avoid	Use only in exceptional cases; this handoff is usually weaker because Media is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Media.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Decision	avoid	Use only in exceptional cases; this handoff is usually weaker because Decision is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Decision.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
FAQ	avoid	Use only in exceptional cases; this handoff is usually weaker because FAQ is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to FAQ.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
API Call	avoid	Use only in exceptional cases; this handoff is usually weaker because API Call is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to API Call.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
User Input	avoid	Use only in exceptional cases; this handoff is usually weaker because User Input is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to User Input.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Delay	avoid	Use only in exceptional cases; this handoff is usually weaker because Delay is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Delay.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Timeout	avoid	Use only in exceptional cases; this handoff is usually weaker because Timeout is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Timeout.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Retry	avoid	Use only in exceptional cases; this handoff is usually weaker because Retry is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Retry.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Set Variable	avoid	Use only in exceptional cases; this handoff is usually weaker because Set Variable is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Set Variable.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Human Handover	avoid	Use only in exceptional cases; this handoff is usually weaker because Human Handover is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Human Handover.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Fallback	avoid	Use only in exceptional cases; this handoff is usually weaker because Fallback is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Fallback.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Switch / Router	avoid	Use only in exceptional cases; this handoff is usually weaker because Switch / Router is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Switch / Router.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Condition	avoid	Use only in exceptional cases; this handoff is usually weaker because Condition is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Condition.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Loop	avoid	Use only in exceptional cases; this handoff is usually weaker because Loop is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Loop.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Intent Router	avoid	Use only in exceptional cases; this handoff is usually weaker because Intent Router is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Intent Router.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Extract	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Extract is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to AI Extract.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Error Handler	avoid	Use only in exceptional cases; this handoff is usually weaker because Error Handler is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to Error Handler.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Sentiment	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Sentiment is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to AI Sentiment.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Memory	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Memory is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to AI Memory.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
AI Generate	avoid	Use only in exceptional cases; this handoff is usually weaker because AI Generate is not a natural next step after End.	High risk of confusing flow logic, dead-end paths, or poor user experience if End routes directly to AI Generate.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.

Intent Router (intent-router) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Intent Router.	High risk of confusing flow logic, dead-end paths, or poor user experience if Intent Router routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require Intent Router before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require Intent Router before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Intent Router before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	recommended	Use this when the journey should first classifies user intent and routes to the matching journey and then responds using pre-configured FAQ knowledge behavior.	Main risk is missing fallback, timeout, or error coverage around the Intent Router to FAQ transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
API Call	recommended	Use this when the journey should first classifies user intent and routes to the matching journey and then fetches or sends data to external systems and maps results into variables.	Main risk is missing fallback, timeout, or error coverage around the Intent Router to API Call transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
User Input	conditional	Use this when business rules require Intent Router before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Intent Router before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Intent Router before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Intent Router before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Intent Router before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require Intent Router before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	recommended	Use this when the journey should first classifies user intent and routes to the matching journey and then provides a safe default response when the bot cannot understand or route properly.	Main risk is missing fallback, timeout, or error coverage around the Intent Router to Fallback transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Switch / Router	conditional	Use this when business rules require Intent Router before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Intent Router before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Intent Router before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require Intent Router before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Intent Router before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require Intent Router before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Intent Router before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Intent Router before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Intent Router before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

AI Extract (ai-extract) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after AI Extract.	High risk of confusing flow logic, dead-end paths, or poor user experience if AI Extract routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require AI Extract before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require AI Extract before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require AI Extract before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require AI Extract before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	recommended	Use this when the journey should first extracts structured fields from user text based on a schema and then fetches or sends data to external systems and maps results into variables.	Main risk is missing fallback, timeout, or error coverage around the AI Extract to API Call transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
User Input	conditional	Use this when business rules require AI Extract before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require AI Extract before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require AI Extract before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require AI Extract before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	recommended	Use this when the journey should first extracts structured fields from user text based on a schema and then stores or updates key values used later in the flow.	Main risk is missing fallback, timeout, or error coverage around the AI Extract to Set Variable transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Human Handover	conditional	Use this when business rules require AI Extract before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require AI Extract before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require AI Extract before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	recommended	Use this when the journey should first extracts structured fields from user text based on a schema and then evaluates a rule (equals, contains, regex) to choose next behavior.	Main risk is missing fallback, timeout, or error coverage around the AI Extract to Condition transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Loop	conditional	Use this when business rules require AI Extract before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require AI Extract before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require AI Extract before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require AI Extract before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require AI Extract before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require AI Extract before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require AI Extract before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

Error Handler (error) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after Error Handler.	High risk of confusing flow logic, dead-end paths, or poor user experience if Error Handler routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	recommended	Use this when the journey should first handles failures gracefully with user-safe messaging and recovery path and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the Error Handler to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require Error Handler before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require Error Handler before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require Error Handler before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require Error Handler before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require Error Handler before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require Error Handler before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require Error Handler before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require Error Handler before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require Error Handler before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	recommended	Use this when the journey should first handles failures gracefully with user-safe messaging and recovery path and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the Error Handler to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	conditional	Use this when business rules require Error Handler before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require Error Handler before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require Error Handler before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require Error Handler before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	recommended	Use this when the journey should first handles failures gracefully with user-safe messaging and recovery path and then closes the journey with a final confirmation or closing message.	Main risk is missing fallback, timeout, or error coverage around the Error Handler to End transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Intent Router	conditional	Use this when business rules require Error Handler before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require Error Handler before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require Error Handler before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require Error Handler before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require Error Handler before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

AI Sentiment (ai-sentiment) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after AI Sentiment.	High risk of confusing flow logic, dead-end paths, or poor user experience if AI Sentiment routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	recommended	Use this when the journey should first detects conversation sentiment to adapt tone and escalation decisions and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the AI Sentiment to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require AI Sentiment before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require AI Sentiment before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require AI Sentiment before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require AI Sentiment before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require AI Sentiment before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require AI Sentiment before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require AI Sentiment before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require AI Sentiment before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	recommended	Use this when the journey should first detects conversation sentiment to adapt tone and escalation decisions and then stores or updates key values used later in the flow.	Main risk is missing fallback, timeout, or error coverage around the AI Sentiment to Set Variable transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Human Handover	recommended	Use this when the journey should first detects conversation sentiment to adapt tone and escalation decisions and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the AI Sentiment to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	conditional	Use this when business rules require AI Sentiment before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require AI Sentiment before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	conditional	Use this when business rules require AI Sentiment before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require AI Sentiment before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require AI Sentiment before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require AI Sentiment before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require AI Sentiment before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require AI Sentiment before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	conditional	Use this when business rules require AI Sentiment before AI Memory, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	conditional	Use this when business rules require AI Sentiment before AI Generate, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.

AI Memory (ai-memory) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after AI Memory.	High risk of confusing flow logic, dead-end paths, or poor user experience if AI Memory routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	conditional	Use this when business rules require AI Memory before Message, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Media	conditional	Use this when business rules require AI Memory before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require AI Memory before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require AI Memory before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require AI Memory before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require AI Memory before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require AI Memory before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require AI Memory before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require AI Memory before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require AI Memory before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	recommended	Use this when the journey should first stores selected user context so future responses can stay personalized and then transfers the conversation to a human or external support channel.	Main risk is missing fallback, timeout, or error coverage around the AI Memory to Human Handover transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Fallback	conditional	Use this when business rules require AI Memory before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	recommended	Use this when the journey should first stores selected user context so future responses can stay personalized and then routes users to different branches based on one variable value.	Main risk is missing fallback, timeout, or error coverage around the AI Memory to Switch / Router transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Condition	conditional	Use this when business rules require AI Memory before Condition, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Loop	conditional	Use this when business rules require AI Memory before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require AI Memory before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require AI Memory before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require AI Memory before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require AI Memory before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require AI Memory before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Generate	recommended	Use this when the journey should first stores selected user context so future responses can stay personalized and then generates dynamic text from a prompt template and optional variables.	Main risk is missing fallback, timeout, or error coverage around the AI Memory to AI Generate transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.

AI Generate (ai-generate) -> 22 pairings

Target	Status	Use Case	Risk	Setup Tip
Start	avoid	Use only in exceptional cases; this handoff is usually weaker because Start is not a natural next step after AI Generate.	High risk of confusing flow logic, dead-end paths, or poor user experience if AI Generate routes directly to Start.	Prefer another target node; if unavoidable, isolate this path, document ownership, and monitor it with alerts.
Message	recommended	Use this when the journey should first generates dynamic text from a prompt template and optional variables and then sends one or more text messages to the user.	Main risk is missing fallback, timeout, or error coverage around the AI Generate to Message transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Media	conditional	Use this when business rules require AI Generate before Media, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Decision	conditional	Use this when business rules require AI Generate before Decision, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
FAQ	conditional	Use this when business rules require AI Generate before FAQ, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
API Call	conditional	Use this when business rules require AI Generate before API Call, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
User Input	conditional	Use this when business rules require AI Generate before User Input, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Delay	conditional	Use this when business rules require AI Generate before Delay, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Timeout	conditional	Use this when business rules require AI Generate before Timeout, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Retry	conditional	Use this when business rules require AI Generate before Retry, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Set Variable	conditional	Use this when business rules require AI Generate before Set Variable, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Human Handover	conditional	Use this when business rules require AI Generate before Human Handover, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Fallback	conditional	Use this when business rules require AI Generate before Fallback, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Switch / Router	conditional	Use this when business rules require AI Generate before Switch / Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Condition	recommended	Use this when the journey should first generates dynamic text from a prompt template and optional variables and then evaluates a rule (equals, contains, regex) to choose next behavior.	Main risk is missing fallback, timeout, or error coverage around the AI Generate to Condition transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.
Loop	conditional	Use this when business rules require AI Generate before Loop, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
End	conditional	Use this when business rules require AI Generate before End, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Intent Router	conditional	Use this when business rules require AI Generate before Intent Router, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Extract	conditional	Use this when business rules require AI Generate before AI Extract, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
Error Handler	conditional	Use this when business rules require AI Generate before Error Handler, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Sentiment	conditional	Use this when business rules require AI Generate before AI Sentiment, but only with explicit branch and validation controls.	Without clear routing criteria, this pairing can create branch sprawl, unexpected transitions, or difficult troubleshooting.	Document the business condition for this handoff and add validation with fallback before go-live.
AI Memory	recommended	Use this when the journey should first generates dynamic text from a prompt template and optional variables and then stores selected user context so future responses can stay personalized.	Main risk is missing fallback, timeout, or error coverage around the AI Generate to AI Memory transition.	Define one clear transition rule, map required variables, and test happy path plus one failure scenario before launch.

Flow Node Combination Matrix

How to read the matrix

What this covers

Full Node Combination Matrix

Operational Checklist

Related Guides

Next Action

Flow Node Combination Matrix

How to read the matrix

What this covers

Full Node Combination Matrix

Operational Checklist

Related Guides

Next Action