I suggest you ...

Put Trigger customization under Assets (Widgets)

Since a separate asset could be created to handle localization (multi-language support) shouldn’t the triggers be under the assets instead of global settings?

8 votes
Vote
Sign in
(thinking…)
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Admintawk.to (top bird!, tawk.to) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

4 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • Anonymous commented  ·   ·  Flag as inappropriate

    Presently it appears that triggers work across all account widgets, we have 2 widgets for our multilingual site and we need to be able to set different triggers for the different widgets

  • Charalampos Tsimpouris commented  ·   ·  Flag as inappropriate

    It would be nice to have an extra condition in triggers only for specific assets. The problem begins from the fact that having a multilingual site, I show two different assets under the same property, one per language. However, I cannot use the triggers with custom texts, as it will be in a different language than the users. I know, that I could have two different properties.. but still, an extra condition could be really nice.

  • Luca commented  ·   ·  Flag as inappropriate

    In cases of a website (property) translated in different languages (assets) would be useful the option to have different trigger messages, translated in the different languages of the widget assets instead of one trigger at the property level for all of them.

  • Walter Barlet commented  ·   ·  Flag as inappropriate

    Since a separate asset could be created to handle localization (multi-language support) shouldn't the triggers and departments be under the assets instead of global settings?

Feedback and Knowledge Base