# 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:

1. Select target profiles from your configured deployments
2. Create specific cases for each profile that needs unique handling
3. Define the conversation path for each case
4. 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.

<figure><img src="https://1213579860-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MaU7JJyoXT5PfhTD9dJ%2Fuploads%2FDJHWhYHpiDcFFhJWE1hF%2Fhub-assistant-virbe.virbe.app_dashboard_conversation-flows_ca98acce-9cff-4d65-ad55-7ca28f98965e_node_07db13a7-d615-43bd-8db8-7709c8e5bd9d.png?alt=media&#x26;token=0f78a0e1-91e5-48e7-b0b3-a722509e5dec" alt=""><figcaption><p>Route by Profile example use case</p></figcaption></figure>

#### 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

{% hint style="info" %}
I**mportant 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
  {% endhint %}