Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Vitor Leepkaln
Beigetreten 09. Feb. 2022
·
Letzte Aktivität 15. Mai 2024
Folge ich
0
Follower
0
Gesamtaktivitäten
3
Stimmen
0
Abonnement
1
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Vitor Leepkaln
Vitor Leepkaln hat einen Post erstellt
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.
Gepostet 14. Mai 2024 · Vitor Leepkaln
0
Follower
3
Stimmen
2
Kommentare
Vitor Leepkaln hat einen Kommentar hinterlassen
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!
Kommentar anzeigen · Gepostet 09. Feb. 2022 · Vitor Leepkaln
0
Follower
0
Stimmen
0
Kommentare