You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I have a problem. Some of our clients are writing new emails by replying to old ones. They change title and remove the history. One of them has done it so wrong, so the most of the emails was in the reply formatting and was cut by freescout standard view. Is it possible, to not link the messages to proper conversations, when the situation happens? We received a very important message today with the words "Good morning" to old closed conversation and didn't know what going on. Maybe, Ticket Number module work would be enough to identify conversation continuity? Can you help me, please?
The text was updated successfully, but these errors were encountered:
@adam3278 This happens to me once in a while as well. I use the message drop-down in the upper right corner and choose "Show Original", and it will open a modal window showing the full message unmodified and without the pruning or clean-up that FreeScout is doing. Something as simple as a black background with white font breaks the standard view, and Show Original fixes that, in-line replies, and most other HTML issues.
It’s not the app bug. I examined the whole thread flow and created the special module that changes the whole reply separation feature in Freescout. I’m going to publish it in a few days, so anyone would be able to handle described situations.
Hello,
I have a problem. Some of our clients are writing new emails by replying to old ones. They change title and remove the history. One of them has done it so wrong, so the most of the emails was in the reply formatting and was cut by freescout standard view. Is it possible, to not link the messages to proper conversations, when the situation happens? We received a very important message today with the words "Good morning" to old closed conversation and didn't know what going on. Maybe, Ticket Number module work would be enough to identify conversation continuity? Can you help me, please?
The text was updated successfully, but these errors were encountered: