
Vladimir Petrushenka
-
Activité totale211
-
Dernière activité
-
Membre depuis
-
Abonné à1 utilisateur
-
Abonnés0 utilisateur
-
Votes91
-
Abonnements65
Aperçu des activités
Dernière activité effectuée par Vladimir Petrushenka-
Vladimir Petrushenka a ajouté un commentaire,
Hi Shawna James, that would be great if you could share the recording. Thanks a lot.
-
Vladimir Petrushenka a ajouté un commentaire,
Hi Walter Bellante and Shawna James, I've signed up for the Explore feedback round table event, but I can't seem to join the call. The link that was sent to me in the confirmation email takes me ba...
-
Vladimir Petrushenka a ajouté un commentaire,
Thanks for clarifying these, Walter, and hope you are well.
-
Vladimir Petrushenka a ajouté un commentaire,
Hi there, thanks for the update. There are two things that concern us a little, I'm hoping you can please comment on them. 1. Bookmarks related. We have the same use case as one of the posters abo...
-
Vladimir Petrushenka a ajouté un commentaire,
This is just awful, and forgive me for being direct here. We've spent months(!) putting together the existing dashboards, scheduling them to our partners, internally etc which now needs to be re-d...
-
Vladimir Petrushenka a ajouté un commentaire,
it does, thanks Gabriel
-
Vladimir Petrushenka a ajouté un commentaire,
also, would someone be able to share the HTML code for this CSAT survey:
-
Vladimir Petrushenka a ajouté un commentaire,
Hi folks, Was hhoping someone could advise on the following. When I add {{satisfaction.rating_section}} to the macro and apply it, it comes in the response in a shape of a link that takes to the...
-
Vladimir Petrushenka a ajouté un commentaire,
Big +1 to the CJ Johnson point. You have to be able to report on 'Next SLA Breach', even if it's not live but a snapshot of how it looked a couple of hours ago!
-
Vladimir Petrushenka a ajouté un commentaire,
Big +1 to this feature. The feature would allow us to share customer comments with partners in automated way via dashboard scheduling. Unfortunately, currently we have to do that manually