Skip to main content
Question

Forwarding ticket to the email address of another Workspace

  • February 28, 2025
  • 8 replies
  • 52 views

Forum|alt.badge.img+5
  • Skilled Expert
  • 21 replies

Hello,

We have an email address which our IT Workspace frequently forwards from tickets to and liais with the delegates of that email mailbox. Today that team was setup with a separate Workspace utilising this email address.
Is there a way that we can still forward from our IT Workspace to this email address so that the team in the other Workspace can respond or would we be forced to use the Move functionality?

It is causing quite the headache at the moment.

Thanks!

Did this topic help you find an answer to your question?

8 replies

kubernetesdashboard
Community Debut
Forum|alt.badge.img

You're dealing with Workspace limitations when forwarding tickets between different environments. Typically, forwarding to an external Workspace email should work unless restrictions are in place. If forwarding isn't an option, using the Move functionality might be necessary. However, you could explore these alternatives:

  1. Allowlist the Email: Check if the receiving Workspace blocks external emails and allowlist the IT Workspace's email.
  2. Shared Mailbox Access: If both teams need to collaborate, setting up a shared mailbox across Workspaces might help.
  3. Automated Rules: Some Workspace platforms allow auto-forwarding rules for seamless communication.

Would love to know what platform you're using—there might be specific settings to tweak!


Forum|alt.badge.img+5
  • Author
  • Skilled Expert
  • 21 replies
  • March 17, 2025
kubernetesdashboard wrote:

You're dealing with Workspace limitations when forwarding tickets between different environments. Typically, forwarding to an external Workspace email should work unless restrictions are in place. If forwarding isn't an option, using the Move functionality might be necessary. However, you could explore these alternatives:

  1. Allowlist the Email: Check if the receiving Workspace blocks external emails and allowlist the IT Workspace's email.
  2. Shared Mailbox Access: If both teams need to collaborate, setting up a shared mailbox across Workspaces might help.
  3. Automated Rules: Some Workspace platforms allow auto-forwarding rules for seamless communication.

Would love to know what platform you're using—there might be specific settings to tweak!

Is this a bot response?
The first alternative doesn’t make any sense in context.


Daniel Söderlund
Skilled Expert
Forum|alt.badge.img+14
Razor wrote:
kubernetesdashboard wrote:

You're dealing with Workspace limitations when forwarding tickets between different environments. Typically, forwarding to an external Workspace email should work unless restrictions are in place. If forwarding isn't an option, using the Move functionality might be necessary. However, you could explore these alternatives:

  1. Allowlist the Email: Check if the receiving Workspace blocks external emails and allowlist the IT Workspace's email.
  2. Shared Mailbox Access: If both teams need to collaborate, setting up a shared mailbox across Workspaces might help.
  3. Automated Rules: Some Workspace platforms allow auto-forwarding rules for seamless communication.

Would love to know what platform you're using—there might be specific settings to tweak!

Is this a bot response?
The first alternative doesn’t make any sense in context.

yes bot. FW drops e-mail sent from one FS mailbox to another FS mailbox. cloning the ticket or create a subticket. 


Forum|alt.badge.img+5
  • Author
  • Skilled Expert
  • 21 replies
  • March 19, 2025
Daniel Söderlund wrote:
Razor wrote:
kubernetesdashboard wrote:

You're dealing with Workspace limitations when forwarding tickets between different environments. Typically, forwarding to an external Workspace email should work unless restrictions are in place. If forwarding isn't an option, using the Move functionality might be necessary. However, you could explore these alternatives:

  1. Allowlist the Email: Check if the receiving Workspace blocks external emails and allowlist the IT Workspace's email.
  2. Shared Mailbox Access: If both teams need to collaborate, setting up a shared mailbox across Workspaces might help.
  3. Automated Rules: Some Workspace platforms allow auto-forwarding rules for seamless communication.

Would love to know what platform you're using—there might be specific settings to tweak!

Is this a bot response?
The first alternative doesn’t make any sense in context.

yes bot. FW drops e-mail sent from one FS mailbox to another FS mailbox. cloning the ticket or create a subticket. 

Thanks.
I’m assuming there’s no way around the hardcoded ticket loop prevention when sending from one Workspace email to another, even with skip email notification present?


Daniel Söderlund
Skilled Expert
Forum|alt.badge.img+14
Razor wrote:
Daniel Söderlund wrote:
Razor wrote:
kubernetesdashboard wrote:

You're dealing with Workspace limitations when forwarding tickets between different environments. Typically, forwarding to an external Workspace email should work unless restrictions are in place. If forwarding isn't an option, using the Move functionality might be necessary. However, you could explore these alternatives:

  1. Allowlist the Email: Check if the receiving Workspace blocks external emails and allowlist the IT Workspace's email.
  2. Shared Mailbox Access: If both teams need to collaborate, setting up a shared mailbox across Workspaces might help.
  3. Automated Rules: Some Workspace platforms allow auto-forwarding rules for seamless communication.

Would love to know what platform you're using—there might be specific settings to tweak!

Is this a bot response?
The first alternative doesn’t make any sense in context.

yes bot. FW drops e-mail sent from one FS mailbox to another FS mailbox. cloning the ticket or create a subticket. 

Thanks.
I’m assuming there’s no way around the hardcoded ticket loop prevention when sending from one Workspace email to another, even with skip email notification present?

No, I have a idea of using a sidebar app, where you select the workspace and group. It clones the ticket. 
Still The idea is to get feedback from the other group on a ticket.  Create tasks or child ticket that you assign the to the other group. 


Daniel Söderlund
Skilled Expert
Forum|alt.badge.img+14

This was Freshdesk ? ignore the task bit then :) 


Forum|alt.badge.img+5
  • Author
  • Skilled Expert
  • 21 replies
  • March 19, 2025
Daniel Söderlund wrote:
Razor wrote:
Daniel Söderlund wrote:
Razor wrote:
kubernetesdashboard wrote:

You're dealing with Workspace limitations when forwarding tickets between different environments. Typically, forwarding to an external Workspace email should work unless restrictions are in place. If forwarding isn't an option, using the Move functionality might be necessary. However, you could explore these alternatives:

  1. Allowlist the Email: Check if the receiving Workspace blocks external emails and allowlist the IT Workspace's email.
  2. Shared Mailbox Access: If both teams need to collaborate, setting up a shared mailbox across Workspaces might help.
  3. Automated Rules: Some Workspace platforms allow auto-forwarding rules for seamless communication.

Would love to know what platform you're using—there might be specific settings to tweak!

Is this a bot response?
The first alternative doesn’t make any sense in context.

yes bot. FW drops e-mail sent from one FS mailbox to another FS mailbox. cloning the ticket or create a subticket. 

Thanks.
I’m assuming there’s no way around the hardcoded ticket loop prevention when sending from one Workspace email to another, even with skip email notification present?

No, I have a idea of using a sidebar app, where you select the workspace and group. It clones the ticket. 
Still The idea is to get feedback from the other group on a ticket.  Create tasks or child ticket that you assign the to the other group. 

I like this idea!
We have the clone ticket app but it’s still extra steps for those involved which they can’t seem to learn, everyone in our Business Workspaces has been forwarding emails for years now and untraining this behaviour is difficult.
I’ve managed to figure something out in my other thread 

but it’s very janky, so an app that could just do this easily would be a great solution.

EDIT: Is Freshservice not Freshdesk


Daniel Söderlund
Skilled Expert
Forum|alt.badge.img+14

@Kamakshi V can you please move this thread to FS ? 


Reply