Route by Profile
The Route by Profile node allows your virtual being to deliver different conversation experiences depending on where it's deployed. When a user interacts with your virtual being, this node checks which profile the interaction is taking place on (e.g. specific web widget or kiosk) and routes the conversation along the appropriate path.
Setting up profile routing:
Select target profiles from your configured deployments
Create specific cases for each profile that needs unique handling
Define the conversation path for each case
Set a default path for any unmatched profiles to prevent dead ends
Example:
The virtual being will deliver a different greeting when the conversation starts depending on the touchpoint, in this case there are two profiles deployed: a web widget and a kiosk.
Other example use cases:
Different responses for web vs kiosk
Different data collection based on the profile
Different Datat tables searched for answers
Custom behavior per deployment
Important considerations:
Always set a default case to handle unexpected situations
Test behavior thoroughly across all profiles
Consider flow complexity depending on the touchpoint and environment (public access vs personal device)
Maintain consistent core functionality across all profiles
Last updated