This object is in archive! 

Improve Email Subject Matching with Multiple Forwards

Archived Mike M. 9 years ago

Currently, the system handles email replies where RE: is added, but some email systems add it every time the user replies. This results in RE: RE: and so on, which opens a new ticket each time.


Can the subject matching be improved to allow multiple instances of "RE:"?

Best Answer
photo

We've tweaked the "reply to" feature, so it should work now in 3.2.1 release that would be live shortly.

Replies (10)

photo
1

If you are on 3.2 release, that shouldn't happen, as UseResponse adds Re: only once to the subject, so maximum you can get two Re:, though it shouldn't affect check on creating new ticket as we identify if user replied by ID of the ticket that is hidden in 3 different places.


Are you sure the ticket is opened each time when new Re: is added to the subject? As we can't reproduce it on our environment and matching of subjects should work without problems.

photo
1

Perhaps the "Re:" was a red herring. Upon further inspection of an affected ticket, I see the full history of the ticket in each reply, but unformatted.


Is it possible that the user's mail client is stripping formatting in the Reply, and when it does so, it removes the hidden ticket ID?

photo
1

I don't think it can strip all the hidden object ids, and even if it strips the formatting, our system should just parse what is above --REPLY ABOVE THIS LINE--


So everything below this should be stripped by the system and insert all history in all email notifications.

It would be great if you could attach html version of your notification in zip here, so we could check it, or better forward it to support@useresponse.com and we'll review it.

photo
1

Test Reply with Formatting Stripped

On Thu, Mar 5, 2015 at 9:41 AM, UseResponse <support@useresponse.com> wrote:

>

photo
1

So as you can see it works without problems.

photo
1

Indeed. We're definitely seeing tickets being opened by email responses, we just need to figure out why. It only affects some email replies, not all. We're doing additional testing to find out what the trigger causes might be.

photo
1

During our tests, we were able to reproduce it by adding a 2nd Re: when responding.


To be clear, it seems to happen only when a Replying User adds additional Re: tags. It's not a problem with outbound mail, but incoming.

photo
1

The problem is that even adding 2nd Re: doesn't create new ticket. It posts as reply.

Could you please reproduce it on your own, or keep an eye on the problem, so we could catch it and fix, as their should be some specifics

photo
1

Got it. We've caught the problem :) Thank you


Tweak should be in 3.2.1 that should be live shortly.

photo
1

Thanks Stas!

photo
1

Mike,


Could you please clarify what email client do you use, as we've noticed that it stripped all hidden object ids?

photo
1

Hi Stas,


I used Gmail to reply.

photo
1

So as I understand, you've changed subject manually - correct?

photo
1

That's correct - gmail maintains only one, by default. I'm not sure what client was in use by the customers experiencing the issue, but their tickets always showed the extra "re:".

photo
1

We've identified that the problem is in your customer's email client, though, we've decided to put hidden one more id as an attribute to specific tag that won't be stripped ever until following situation:


  • Client changes subject manually
  • Client also strips manually the content of reply

If client makes 2 above actions, new ticket will be created, but the situation most likely won't happen, as it would mean client just strips all the content when replying to it.

photo
1

We've tweaked the "reply to" feature, so it should work now in 3.2.1 release that would be live shortly.

Replies have been locked on this page!