CSAT For Talk

25 Comments

  • Louise Dissing

    Hi Brandon,

    I've actually really been thinking about how to do this - and we at helphouse came up with an idea on how to do this with texts instead!

    Let me know if you could be interested in hearing any further about this, and then we could set up a meeting regarding this?

    #helpsome regards,
    Louise Dissing
    Team Lead @ helphouse.io

    1
  • Brandon Tidd
    Community Moderator
    The Humblident Award - 2021

    Hi Louise,

     

    Thanks for reaching out.  While that idea sounds good in theory - most of our end-users are contacting us through office lines, so a text doesn't make sense in this use-case.  Maybe someone else will benefit from this project though, so keep up the good work!

     

    Brandon

    0
  • Jen Juang

    Louise - I'd love to hear what you came up with. Can you please share? Or what's the best way to get in touch with you?

    0
  • Thomas de Silva

    Hi Jen.

     

    Please click the link in my signature.

     

    #helpsome regards,
    Thomas de Silva

    Zendesk Consultant @ helphouse.io

    0
  • Louise Dissing

    Thomas - thank you for being on top! :-)

    Jen, My apologies - you can contact us on support@helphouse.io and then I'll get you in touch with someone who can show you this! :-)

    #helpsome regards,
    Louise Dissing
    Team Lead @ helphouse.io

    0
  • Michael Rieder

    Hi there,

    You can configure an automation in this case if you know the customers e-mail-adress from another conversation or from another source such as your CRM.

    Please make sure that your privacy policies are compliant with such an approach. But from a technical point of view it works fine.

    1
  • Brandon Tidd
    Community Moderator
    The Humblident Award - 2021

    Hi @...,

    We actually use this for accounts where the email address is known, but it would be a nice tie-in for phone call only operations.

    Brandon

    0
  • Michael Rieder

    Hi @...

    There is a way by combining a new ticket field (send SMS for ex.), an automation and a trigger:

    Automation

     

    Trigger

    Unfortunately, the {{satisfaction.rating_url}} is very long. This drives the cost per SMS.

    https://support.zendesk.com/hc/en-us/community/posts/1260800892230-CSAT-via-SMS-How-do-we-short-the-satisfaction-url-

     

    By the way: I think it's better to just use a tag instead of a ticket field ;-)
     
    0
  • Brandon Tidd
    Community Moderator
    The Humblident Award - 2021

    Thanks for this @....  The call center actually takes calls from mostly landlines, eliminating the text back opportunity.  While we were able to tie this back into c-sat using the user's profile and subsequent ticket - the feedback we received was that the email came through too far removed from the call and caused customer confusion.

    0
  • Michael Rieder

    Hi @...

    Good point. I've been thinking about that, too. You can define two rules in the automation for the CSAT by adding the channel as a condition. Then there is one automation per channel. For example, for telephone support you send the survey after one hour, for e-mail after 24 hours. I think we will solve it this way.

    0
  • Brandon Tidd
    Community Moderator
    The Humblident Award - 2021

    Hey @... - good tip!

    0
  • Lauren Benkov

    Hey @...! Thank you for this tip. For triggers I can't seem to get the satisfaction url placeholder to work. Do you have a workaround for this? I thought I could do a second automation instead of a trigger, but you can't send a text via automation.

    Thanks!

    0
  • Michael Rieder

    Hi @...

    Correct. Automations can't send SMS, so we had to combine it with a trigger.
    However, I didn't understand your problem exactly. We simply use the placeholder {{satisfaction.rating.url}} in the SMS text.

    It's best to adopt the solution as described above: https://support.zendesk.com/hc/de/community/posts/360031484573/comments/1260801990290

     
     
    0
  • Lauren Benkov

    @... - got it to work! I had it typed as {{satisfaction.rating_url}} instead of satisfaction.rating.url}}.

    Really appreciate this tip!

    1
  • Michael Rieder

    @... good job :-)

    By the way, you can just paste placeholders into a comment in a ticket to see how it works in your environment.

     
    0
  • Nicole Saunders
    Zendesk Community Manager

    Hey @... - would you consider publishing the handy info you've shared here to our User Tips & Tricks topic? That would help make it easier for other users to find. 

    0
  • Syd

    We too have a gap in CSAT reporting. It would be nice to have the ability to have a CSAT option at the end of the call as we do not always collect an email address during the call

    1
  • Carmen Paolucci

    Definitely interested in this.  Something immediately after the call where the customers stays on the line for a quick CSAT survey.  I know that it can be accomplished via email or SMS but preference would be to offer the CSAT in the channel the customer chose and not all call from an SMS enabled line.  

    1
  • Dave Dyson
    Zendesk Community Manager
    Hi everyone, keep the feedback coming, and don't forget to upvote threads you're interested in – thanks!
    0
  • AH

    {{satisfaction.rating.url}} does not work for me in text message.

    When I use this short code I get an error message saying zendesk could not deliver the message.

    Does anyone use this shortcode? And does it work for you?

    0
  • Brandon Tidd
    Community Moderator
    The Humblident Award - 2021

    Hi AH,

    I think in this case you would need to use the following:

    The default {{satisfaction.rating_section}}​ placeholder will return the following section:

    If you want to offer just the links, you would need to offer both {{satisfaction.positive_rating_url}} and {{satisfaction.negative_rating_url}}  since the links themselves immediately collect the feedback and associate it with the ticket.

    Brandon 

    0
  • AH

    Thank you for your answer Brandon Tidd. However both of those also fail.

    They work perfectly when I use "Email user" in trigger action. But when I chose the action "Text user", they fail and Zendesk says that the text/SMS can not be sent.

    The same happens when I use: {{ticket.url}} - the text can not be sent.

    I tried to enter a plain webadress like: https://www.zendesk.com/ or google.com. They fail. No matter how I format the link/url the text/SMS will not send. 

    It I remove these shortcodes, so it is just plain text, then text/SMS goes through fine.

    ps. the shortcodes below work fine:

    • {{ticket.requester.name}}
    • {{ticket.via}}
    • {{ticket.title}}
    • {{ticket.id}}

    But they all also only render plain text.

    0
  • Brandon Tidd
    Community Moderator
    The Humblident Award - 2021

    Sorry to hear that - I would expect that the other short codes work as they are substitutes for just plain text - a bit surprised that even the plain web addresses like google.com also fail (assuming here you are way under the 160 character limitation).  Let me kick this around with the other moderators and see if anyone has a work around here.  You might also consider opening a support ticket to have the Zendesk advocacy team review your setup specifically.

    0
  • AH

    It has suddenly started working without me doing anything.

    Very strange, but nice that it is working :-)

    Thank you for your help

     

    0

Please sign in to leave a comment.

Powered by Zendesk