Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Gaillen
Beigetreten 22. Okt. 2021
·
Letzte Aktivität 16. Jan. 2024
Folge ich
0
Follower
0
Gesamtaktivitäten
7
Stimmen
2
Abonnement
1
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Gaillen
Gaillen hat einen Kommentar hinterlassen
As the OP, this issue was resolved when we installed the Send as Address app in December 2015. That app "Select an Address" is available here:
https://www.zendesk.com/marketplace/apps/support/46799/select-an-address
This is a reasonable solution, and Zendesk should have marked this issue resolved back then. Good on them for fixing it in the same year it was reported.
Since they let us edit the articles we post, I have updated the subject and description to include the resolved status and solution info.
Kommentar anzeigen · Bearbeitet 16. Jan. 2024 · Gaillen
0
Follower
1
Stimme
0
Kommentare
Gaillen hat einen Post erstellt
This issue affects accounts that have both Multi Brands enabled and have installed the Zendesk-made app "Select an Address". Additionally, all Agents in the account work across brands, so groups can't be used to filter, nor can the option to "use last address", since it may not be in the correct brand.
The goal is to ensure that email domains always match the Brand by default unless an agent intervenes and chooses to configure it differently.
Ideally, if you have both features enabled, an agent manually creating a new ticket would choose a brand on the left side of the ticket (required) and optionally choose to modify the sender address with the app on the right, but if they made no changes to the "Select an Address", then the default email for the brand they chose would be used.
This would match the behaviour of the "Select an Address" when used without Brands enabled, So the account only has a single brand. In this case, it can be optionally used, but if ignored on new manual ticket creation, the email address set as account default is used, and of course, since only one brand is in use, it matches.
Currently, what happens when both Multi Brands and "Select an Address" are used and an agent does not take the extra step to choose the email address is first or primary brand is default email is used. Example of what currently happens:
Brand A and Brand B exist in the account. Both brands have a default email configured in the brand admin area. Brand A was the first one created (not sure if the order of creation matters).
An agent chooses Brand B when manually creating a ticket but fails to manually adjust the "Select an Address" app. With no adjustments, when the agent submits the ticket, the "Select "Send As" Address" will change the email to Brand A's default email, ignoring that the brand of the ticket was set to Brand B.
Bearbeitet 16. Jan. 2024 · Gaillen
5
Follower
6
Stimmen
5
Kommentare
Gaillen hat einen Kommentar hinterlassen
This is an old issue that has been resolved with the Marketplace add on by Zendesk Labs called "Select an Address" https://www.zendesk.com/apps/support/select-an-address/?source=app_directory
Kommentar anzeigen · Gepostet 29. Juni 2018 · Gaillen
0
Follower
0
Stimmen
0
Kommentare
Gaillen hat einen Post erstellt
When we create tickets on behalf of our customers, as per this article https://support.zendesk.com/hc/en-us/articles/203690946-Creating-a-ticket-on-behalf-of-the-requester, we need a way to change which email address we send the ticket from. Currently, it uses the default support address, but we would like the flexibility to change to one of the non-default addresses that are configured on the email channel.
Note this was resolved with the release of the Zendesk-made app "Select an Address" Available here: https://www.zendesk.com/marketplace/apps/support/46799/select-an-address
Bearbeitet 16. Jan. 2024 · Gaillen
43
Follower
43
Stimmen
38
Kommentare