Need a placeholder for satisfaction reason

12 Commentaires

  • Greg Pope
    Actions pour les commentaires Permalien

    +1

    We need the reason placeholder for the exact same use case (a bad rating triggered email).

    0
  • Mauro Recanatesi
    Actions pour les commentaires Permalien

    We also need the reason placeholder for the exact same use case.

    Thanks

    Bye

    0
  • Sharon Grey
    Actions pour les commentaires Permalien

    We have the same use case.  It seems like just an oversight that -- when the functionality was added -- a placeholder wasn't also added to allow the inclusion of reason in a triggered Notification email.

    0
  • Jeff Callahan
    Actions pour les commentaires Permalien

    +1 for this

    0
  • Martin
    Actions pour les commentaires Permalien

    +1 from me

    0
  • Mike Barnette
    Actions pour les commentaires Permalien

    +1 here as well, please!

    0
  • Actions pour les commentaires Permalien

    Hi all, 

    to register your "+1" please use the voting buttons on the original post, and in the comments share details about your use case, or the scope and impact it would have on your workflows/business. 

    Thanks for your participation! 

    0
  • Tobias Hermanns
    Actions pour les commentaires Permalien

    Yes, please!

    0
  • Neus
    Actions pour les commentaires Permalien

    Yes please! We need to inform our Agents about which reason the user chosed, not only the coment.

    0
  • Maggie St. Clair
    Actions pour les commentaires Permalien

    Please consider adding this placeholder. We need it for the same reasons mentioned by everyone else. Thanks! 

    0
  • Thomas Joussot
    Actions pour les commentaires Permalien

    +1 on this feature request.

    This placeholder is absolutely required to notify team leaders here as well.

    This is crucial for us to know why a ticket has been bad rated. Please consider adding this asap, thanks!

    0
  • Predintha Jayasinghe
    Actions pour les commentaires Permalien

    +1 - We have the exact same use case as the original post.

    0

Vous devez vous connecter pour laisser un commentaire.

Réalisé par Zendesk