Your support needs to grow with the size of your website. People browsing your shop have different questions than those checking your documentation, international visitors prefer support in their own language, and you might want to use a different approach mode depending on whether your contacts are using a desktop or a mobile device.
Our **Widget routers** make the handling of all these scenarios a breeze. You can easily configure rules that select different Widgets depending on the information we have about your contacts: the section of the website they are on when starting a conversation, which country they are from, which language they prefer in their browsers, etc. Managing individual chat setups has never been easier.
|Configuration||How to create and configure Widget routers.|
|Integration||How to add configured Widget routers to your website.|
|Sample Widget routers||Typical examples for when Widget routers are useful - and how to set them up accordingly.|
In your Dashboard, go to **Config** > **Widget routers**:
Click **Add Widget router** to create a new Widget router:
A new Widget router requires at least a name. It’s enabled by default and has the default Widget selected. Since using a Widget router without a rule set is just like using a regular Widget, let’s add a rule set:
We created a new rule set and edited its first rule. This rule matches if the URL the contact is visiting when starting the chat contains the string “shop”, between slashes. When the rule set matches, it selects a different Widget than the default Widget, in this case the “Active Sales” Widget. Through the fields below you can even override some of the “Active Sales” Widget’s settings.
Once you click **Create Widget router**, you are back to the Widget router overview. Here your newly created Router now appears along with its numbers of rule sets and its current status:
This simple Widget router already allows you to use a dedicated Widget for contacts that start a chat from your webshop, with dedicated support staff that’s best-suited to answer their questions. Now you can create more rule sets for this Widget router, or create more Routers.
Multiple simple Routers vs. few complex Routers
Whether you want to create multiple simple Widget routers with simple rule sets or a few complex Widget routers with many elaborate rule sets is mostly a matter of taste.
Using few complex Widget routers allows you to manage your Widgets from few configuration items and they’re faster to integrate. But overly complex Routers can be hard to understand, which may lead to unwanted behavior.
Multiple simple Widget routers require more integration work up front since each Router has to be manually integrated into your website (see **Integration** section below). Once integrated, however, they can be easier to understand and maintain.
**Please note:** You can only implement one Widget router per HTML page, so if you use multiple Widget routers you have to ensure that each is loaded at the correct location.
More on rule sets
For each rule set you define a Widget that is used if **all** rules match - or choose to display no Widget in this case.
If a Widget router has multiple rule sets, these will be evaluated in a “short-circuit” logic: the rule sets (i.e. its rules) are tested sequentially and the first one with **all** rules matching “wins” – its Widget gets selected.
In addition to picking a Widget, a rule set can also override the following configuration settings of that Widget:
|Approach mode||Changes the Widget’s default approach mode, e.g. make contact registration mandatory when this rule set matches|
|Button position||Changes the Widget’s default button position, e.g. show it on the left side when this rule set matches|
|Button profile desktop||Changes how prominently the Widget’s button is displayed for desktop visitors when this rule set matches|
|Button profile mobile||Changes how prominently the Widget’s button is displayed for mobile visitors when this rule set matches|
More on single rules
Each rule set can consist of multiple rules but must contain at least one. If you create more than one rule for a rule set, all of them have to match in order for the rule set to match. Currently you can create the following rules:
|Matches if the contact’s URL is exactly the string you provided|
|Matches if the contact’s URL contains the regular expression you provided|
|Matches if the contact’s user agent string contains the regular expression you provided|
|Matches if the contact’s IP address resolves to the selected country (or continent)|
|Matches if the contact’s derived language preference equals the selected language|
|Matches if the contact’s browser falls into the selected category (desktop vs. mobile)|
**Please note:** While we do basic syntactic validation for each rule (e.g. whether the provided string is a valid regular expression), you are responsible for building semantically valid rule sets where individual rules do not exclude each other.
For example, if you create a rule set with two rules where the first one requires the contact’s country to be “Germany” while the second rule only matches if the country is “Austria”, the rule set as a whole can never match. The Widget router then falls back to the configured default Widget.
We will show more prototypical Widget router rule set configurations in the example section below.
For each of your Widget routers we provide the respective HTML snippet, ready for you to copy and integrate it yourself or to send it to your technical staff. In the Widget router overview, edit the Widget router you want to integrate:
Go to the **Integration** tab, there you’ll find the HTML code snippet:
Integrating the code yourself
Paste the code into the bottom of your website, just before the closing </body> tag. Save your modified website and upload it to your web server. Congratulations, you are done!
Sending the code to your technical staff
Instead of copying the code, click the **Let my programmer do it** button:
You now see a pre-written message containing all the necessary information for your technical staff to integrate the Widget router. Just provide the email address to send this message to:
Your technical staff will receive this email:
Sample Widget routers
Here are some sample Widget routers to show you possible use cases and configurations that fit them.
Load Widgets based on contact language
You have a website with an international target audience, and your staff is able to offer customer support in three different languages: German, Spanish and English.
First create a localized Widget for each language like the one below:
Then create a Widget router with the following configuration:
First, this Widget router checks if the contact’s browser language settings indicate support for any German locale. If yes, it loads the Widget “Kundenservice auf Deutsch”.
Then it checks if the contact’s browser language settings indicate support for any Spanish locale. If yes, it loads the Widget “Asistencia en español”. In all other cases it falls back to the default Widget “Support in English”.
Things to consider when matching for languages
Most web browsers let you configure more than one language. Our language-based rules only try to match the primary language. Also regional variations are currently ignored, so a rule for Portuguese matches Brazilian and European Portuguese.
Also, it’s good practise to set your default Widget to a language the majority of your contacts likely understands. This way, if none of the more specific language rules match, you will safely fall back to your “main” language version.
Override Widget configurations based on website URL
You want to use a different approach mode depending on which section of your webshop your contacts are browsing. In general, you want to proactively initiate a chat after a certain time and offer support to potential customers. Only on your FAQ page, you want contacts to initiate the chat.
You configure your default Widget to use a proactive approach mode:
Then, to use the same Widget with a different approach mode when the contact browses your FAQs, create a Widget router with the following configuration:
This Widget router checks if the contact is currently visiting your FAQ section. If yes, it loads the “My Webshop” Widget but sets it to **Normal Mode**.
In all other cases and all non-FAQ pages, it also loads the “My Webshop” Widget but uses its default approach mode - proactively starting a chat after 10 seconds.
Load different Widgets depending on geolocation
Due to different legal requirements, you want to use Widgets with different privacy settings depending on your contact’s geolocation.
In a Widget’s settings, you configure it to have a more restrictive Privacy Mode:
Then create a Widget router with the following configuration:
This Widget router checks if your current contact is based in Europe. If yes, it will load the “EU privacy Widget”, with its more restrictive settings. In all other cases it will load the default Widget.