Since Syncro seems to have no plans to support “in-reply-to” headers so ticket emails will actually thread for our customers, I’ve been using {{ticket_public_comments_for_email}} for the body of my “Ticket Comment Email” template. This has been an passible solution for the lack of threading support. However, it was brought to my attention that while the {{ticket_public_comments_for_email}} includes the current “comment_body”, it only includes the first ~2500 characters. The {{comment_body}} variable, emails the entire comment.
The solution would seem to be have {{comment_body}} followed by {{ticket_public_comments_for_email}}. But duplicates the first ~2500 characters of {{comment_body}} directly after the {{comment_body}}. It’s a mess that does not help to alleviate the basic issue of a total lack of threading.
Is there any way that I can include previous comments on a ticket while ensuring that my current comment isn’t truncated while not confusingly repeating the first ~2500 characters?
I just looked at my Support sent items and found an email that has 12,467 characters that was sent to the contact. I’ve never see anything truncated in the sent emails.
I hate the delimiter text line. I’m glad it’s near invisible because we have had several clients that would take it literally when we used CWM and they would reply below our header, right above the line, then their reply wouldn’t make it into CWM.
So literally the only thing different in my wrapper is the color for the “----- REPLY ABOVE THIS LINE TO SEND A RESPONSE -----”. #333333 instead of #E8E8E8. I’m not going to feed my OCD by trying tickets with the default.
On the delimiter text, I had so many attempt to reply in-line only to have their answers blown away!
Don’t know what to say then. It sounds like your token is taking more of a snapshot of the web rather than what it’s meant to, so I’m guessing a support ticket is in order .
I recon it’s that his account perhaps was updated to the new markup messaging system early? I just landed here to try and figure out why we have a character limit now on email. My canned email with full report details of work completed, upgrade recommendations, and other service upsells is now too long… Grrrrr character limits! haha.