Hi there, I would like to attend customer through 2 channels, so I have configured two emails: "firstname.lastname@example.org" and "email@example.com" the first one is the main address and the second one is an alias, each email channel is attended by two different areas from the company.
So, when the customer sends an email to any of the two address configured, It is automatically set to the appropriate queue (I have set an automatic rule that separates each channel).
So, the problem is when I responded the email, it always goes out from the main email: "firstname.lastname@example.org". but I would like that the email who receive the issue should be the same email that responses the customer, (in that case should be the alias: "email@example.com").
Can anybody help me in this case?
PD: I have Jira ServiceDesk Software.
Thanks for your suggestion,
I have configurated two emails on ServiceDesk, a main email "firstname.lastname@example.org" and an alias "email@example.com", each one carries out a specific function, one is for technical support and the other one is for selling and give information to future customers.
So, the problem is, when someone creates a case sending an email to the alias (firstname.lastname@example.org), the ServiceDesk responses through the main email (email@example.com), I would like to know a way to set with the condition that the email receiver (the main or the alias) has to be the email that sends the notification (the main or the alias).
So in effect, regardless of what email your customers are writing to, their replies end up in the same service desk (project)? If this is the case then does it really matter from which of the two email they recieve your notifications?
In any case Jira can only send notifications from one email address per project and can't change it conditionally. Unless there's a 3rd party addon that can somehow do it, but I'm not aware of any.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs