Home / Integrations / Zendesk / Make Zendesk tickets look like real emails

About The Moo Master

As today's world moves towards more cloud based solutions, it's not always easy to find an all-in-one solution to a business problem. We focus on business development. finding new, creative and innovative ways to use different IT systems to enhance and automate business processes. We're happy to share our knowledge and solutions we've come up with over the years to some of those unique IT/Business problems.

16 comments

  1. This would be the perfect solution if this wasn’t an issue: Any HTML/Markdown formatting is not displayed (bold, italics, underline, ahref text links, etc etc). Any other inline elements such as images will also be reduced to nothing more than a link to the image.

    If we could retain html and inline images we would have perfection. I would love to know if anyone comes up with a solution for that.

    Tip: to make it further look like outlook edit to the following:
    From: {{comment.author.name}} Sent:{{comment.created_at_with_time}} To: {{ticket.requester.name}}Cc: {{ticket.cc_names}} {{comment.value}}

    • Hi Alex – Thanks for your input and the tip. The first email should be displayed in HTML so there are no issues with formatting or markdown. The trailing emails i’ve simply done using the unformatted comments placeholder. That way any emails sent using the web interface by the agent will include all the formatting that they provided.

      RE your tip: Good for anyone who is looking to make it look almost identical to an email, thanks for that. For us it was close enough that it still looked nice and neat 🙂

      Agree that this whole solution isn’t perfect – be great if Zendesk could just create a formatted HTML comments placeholder… sigh.

  2. Hello Moo Master,

    I’ve been asked by my company to make Zendesk emails look like regular emails. We get two complaints from our customers about Zendesk quite often. 1. The email I get from Zendesk does not look like an email. 2. The attachment link at the bottom of the reply. Looking at your code it appears that you have some control over where the attachment link is placed. Is that correct?

    Do you offer any Zendesk customization services?

    Thank you.

    • Hi Scott,

      I haven’t tested, but i believe it is possible to shift the attachment to the top of the reply email. It’s for sure not as neat, but there are limitations as you know with how Zendesk handles attachments. Please comment and let me know what other customizations you’re looking for, or send me an email direct – [email protected]

  3. Hello Moo Master,

    I’ve followed the steps outlined but for some reason, any attachments are being stripped from the resulting emails. Any thoughts as to why this might be happening?

  4. Me again Mr. Moo Master! I’m having another problem implementing this code; can’t recall if this was introduced with the fix made recently. Regardless, the code seems to be ignoring the {{delimiter}}. All replies made via email are including all other previous comments, making a mess of the thread. Would you mind looking into this? Thanks in advance!

    • Hi Matthew,
      Is it Agent replying via email or Customer replying via email which are copying the entire thread upon each reply (or both ways)?
      Is it also for every ticket reply, or just a select few replies which is making a mess ?

      • Tested and it appears to be both ways on every ticket. Essentially every time either an end-user or Agent replies via email, it’s taking the new comment, but also including all other previous comments.

        • I was looking to implement this, but have found same thing. If agent responds via email, it creates a private note in the ticket, but then if agent sends customer update from Zendesk, the notification to customer includes the private note.

          Is there any solution?

  5. Hey The Moo Master,

    Thanks for putting this together!

    I am having one problem when implementing this though. It seems like it’s cutting off the last few lines when I receive the email in Gmail. There must be some placeholder still there because there is a rather large gap between the end of the email and the start of the next message in the chain. I’ve copied and pasted exactly what you put in for the email and macro. Any idea what might be causing this?

    Thanks again. You rock!

  6. Hey The Moo Master,

    Please disregard my last comment. Through some brute force commenting I’ve found that line:

    display:none !important; /* Generic*/

    seems to be the pulling my signature (the end of the comment) out of my emails. I understand now that the signature is considered a part of the native zendesk formatting that would be taken out with the name/date/etc at the top. My problem was that with the 20 or so people working through my zendesk account I thought it would be easier just to tack a signature onto the end of each comment rather than make a dynamic HTML sig that would work for everyone… at least while we are still trying out the email features. For the time being I just replaced the signature div in the trigger with a user_signature placeholder and that seemed to do the trick.

    Thanks again for the great template. I really appreciate it!

  7. This is great! Thank you for taking the time to share this. I noticed that the template overrides the default delimiter and injects random text instead. Here’s the in the final email delivered to Gmail inbox.

    [YMMML5-6V7V]

    Do you know why this happens? If possible, I’d like to customize this text and use the delimiter setup on Zendesk.

    This is currently a problem in GMail previews when there’s short text or on mobile. Otherwise, it’s all great!

  8. This mostly works but the gmail client still doesnt collapse down the previous emails automatically. So when you open a new zendesk reply email, it fills your whole screen. Anyone have a workaround?

  9. It doesn’t work with the zendesk support app. The comment isn’t shown.

    Any ideas?

Leave a Reply

Your email address will not be published. Required fields are marked *