Recherches récentes
Pas de recherche récente

Vitor Leepkaln
Adhésion le 09 févr. 2022
·
Dernière activité le 15 mai 2024
Suivis
0
Abonnés
0
Activité totale
3
Votes
0
Abonnement
1
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Vitor Leepkaln
Vitor Leepkaln a créé une publication,
We have a use-case that requires dynamically changing trigger conditions to match our business logic. This means that the values used in the trigger condition change week to week, and it's currently unsustainable to update these values manually.
I've come to realize that we are unable to update said conditions using the trigger endpoints.
As a developer, it would be useful to be able to make changes to Chat trigger conditions using the API, so that the values can be changed dynamically, especially when dealing with hundreds of conditions.
Publication le 14 mai 2024 · Vitor Leepkaln
0
Abonnés
3
Votes
2
Commentaires
Vitor Leepkaln a ajouté un commentaire,
Hi @...,
I have the same question as Maria, and would love to get your input.
We're also looking to automate the user creation process and currently chat comes disabled for all new Support users and we'd like to change that. Is my understanding that needs to be setup from the Chat custom roles side rather than the Support side? Similarly to Maria's, our users are coming with Explore and Guide enabled by default, but Chat doesn't.
Thank you!
Afficher le commentaire · Publication le 09 févr. 2022 · Vitor Leepkaln
0
Abonnés
0
Votes
0
Commentaire