ContributionsMost RecentMost LikesSolutionsDisplaying in line images in GoToAssist emails Hi, Our users all use a standard signature which contains images, and when they create or update tickets via email the update emails we receive change those images into attachments. Is there a way that GoToAssist can retain these images in the message body to keep the fomatting of the email thread tidy? Thanks! Re: Email repsonses are being truncated after smiley :-) Hi, I've just tested this and it seems the issue is now fixed:smileyhappy: the emoticon in the message body appears as a "??" though, is this how it should be appearing? Thanks Re: Email repsonses are being truncated after smiley :-)Hi, has there been an update on the fix for this issue? I just tested it and it is still occurring. Thanks :)Re: Email repsonses are being truncated after smiley :-) Hi, have you had any more updates on this issue? Thanks Re: Email repsonses are being truncated after smiley :-) Hi, has there been any update on this? Re: Email repsonses are being truncated after smiley :-) Awesome thank you very much! Re: Email repsonses are being truncated after smiley :-) Hi, We are designing our service desk so for customers its fully email based. If a customer sends an email in which contains a ":)", any text following the smiley is not logged in the ticket details. The smiley is converted to a graphic automatically in Outlook, which I assume is causing the issue. I can't find a way to easily change this behaviour in Outlook, as it's built into the autocomplete settings. We will have 50 or so staff using the service desk so its also not something we can go to each PC and manually change, and GoToAssist should be able to input the entire email message text whether there is a smiley in it or not. I also found an article from mid-2017 detailing the same issue, so its been brought to attention before: https://community.logmein.com/t5/GoToAssist-Service-Desk/Email-repsonses-are-being-truncated-after-smiley/m-p/182693/thread-id/1551 Can this bug be fixed? Thanks, Mark