Skip to main content
  • EN

Hey @FW Community,

anyone using Threads to collaborate with teams outside of Freshdesk?

We are exploring Threads as to be used to loop in an internal team (let’s say third level alike).
They are pretty well self-organized and use a group email in Outlook - So the plan is to keep them outside of Freshdesk.

Currently they are contacted from agent’s Outlook, so agents do copy&paste all relevant information into the email.
On top of that, agents have to juggle tickets in Freshdesk and the team’s responses in their Outlook.

With threads we could use canned responses to fill all the details directly from Freshdesk ticket and use automations to reopen tickets on the team’s reply.

 

Here’s the issue (or where at least I see a problem):

  1. Creating a Forward Thread via sending an email to the team from our main service address ([email protected])

    The email finds it’s way to the team, so all good.

  2. The team replies from Outlook - So one member from her/his private email address.
    As soon as the answer comes back into Freshdesk, the recipients list looks like this:
    So the replying member (Thomas in this case) is added to the recipients list, but the [email protected] (so the address where we started the Thread from) is now a recipient aswell!
    Is this intented behaviour? I guess probably not, because it really sends an email from Freshdesk to Freshdesk if an agent replies in that Thread.

Does anyone use Threads and experiences the same?

If you're facing unhelpful behavior in Freshdesk threads when collaborators reply, consider downloading reference guides or workflow examples from Pinterest video downloader tool using İndirPin. This tool can help you collect visuals or process ideas to streamline collaboration and improve responses.

Freshdesk is a great tool, but managing collaborator replies can sometimes get tricky. It would be helpful if replies were more streamlined for efficiency. For more tech solutions and tools, check out FlipperZeroUnleashed!

HI ​@Thomas H 

Thank you for bringing this up. 

The behavior where the [email protected] address appears as a recipient when the team replies to the thread is expected due to the threading functionality in Freshdesk. When an email is forwarded from Freshdesk and a reply is received, threading matches the conversation and adds the reply to the ticket while including all participants from the email chain.

To avoid emails being sent back to Freshdesk unnecessarily, you might consider these approaches:

  1. Adjust your workflows so that replies from the team are treated as private notes instead of public interactions. This can be done by manually copying the response content into a private note within the ticket.

  2. Explore using automations or ticket rules to process inbound replies from specific team members or external responders. For example, create a workflow to prevent replies from certain email domains (like those of the team) from generating additional email deliveries back to Freshdesk.

  3. Ensure clear communication about who should be the recipient of replies from the third-level team. Clarifying the email recipient details (like keeping [email protected] only in the CC field initially) can reduce unintended cycles in email communication.

  4. Use custom forwarding mechanisms via integrations or APIs to better control how replies are routed and added to tickets while avoiding direct service email loops.

These adjustments can help streamline collaboration with external teams while minimizing disruptions within Freshdesk tickets.

Thank you 

Hi ​@mahendarsingh,

thank you for your reply.

In my opinion, it does not really make sense to put the address, where the Thread originated from into the recipients list.

I just tested again and the behaviour, which causes emails sent from Freshdesk to Freshdesk also occurs, when you forward to any person directly (so not a team or group address).

Which means, that as soon as you use the Forward feature, you have to deal with unwanted emails sent from the Freshdesk Thread back to the same Freshdesk Thread.

I appreciate your list of workarounds and I guess one of them may work for us.

So thank you for listing them!

 

All the best

Tom


 

If a collaborator's reply feels unhelpful, it's best to address it constructively. Try to clarify your expectations, ask follow-up questions, or gently point out what kind of input would be more useful. Open communication helps keep teamwork productive and respectful — and often clears up misunderstandings quickly.

Hey ​@Zarakhan09 

thank you for your input.

It’s not the collaborator, which causes the issue here. All good with them, the team is doing wonderfully!
My point is, that the Thread feature sends an email to the email-address which the thread email originates from - Which causes a loop.
So the same message you send out appears as coming from outside.

That is not how digital conversations work and cannot be a feature!

Best

Tom

Reply


Terms of Use
OSZAR »