Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Sydney Neubauer
Beigetreten 15. Aug. 2022
·
Letzte Aktivität 21. Feb. 2025
Folge ich
0
Follower
6
Gesamtaktivitäten
1412
Stimmen
587
Abonnements
451
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Sydney Neubauer
Sydney Neubauer hat einen Kommentar hinterlassen
-
We are using email forwarding. I actually submitted a ticket to Zendesk premier and they had confirmed external emails added to Zendesk do not get the error. Can you clarify the scenarios that would get the error and would not? Perhaps add a chart with different scenarios. We have our own branded emails in Zendesk that are externally owned. inbound they forward to the Zendesk email but when it leaves Zendesk, it goes straight to the recipient.
- Thank you! Yes please add those items to the article
- Yes we are aware but that requires agent action to view the error (add email, expand the ticket by selecting ‘see more’ for headers, hover over the email added, see error). There is no immediate indication in big red letters to show there is no valid email and can be easily missed.
Kommentar anzeigen · Gepostet 21. Feb. 2025 · Sydney Neubauer
0
Follower
0
Stimmen
0
Kommentare
Sydney Neubauer hat einen Kommentar hinterlassen
I just got confirmation for my 2 points:
- As there is no email address to provide the bounceback, there will not be an error if you send an email to a profile with no email address
- If you use branded emails or addresses not owned by Zendesk, then no bounceback is present
This article is missing vital information. It needs to be updated to include these limitations as the article is very misleading without it:
- No bounceback for no emails
- No bounceback for non Zendesk email addresses
- No bounceback for Side Conversations
Kommentar anzeigen · Gepostet 19. Feb. 2025 · Sydney Neubauer
0
Follower
0
Stimmen
0
Kommentare
Sydney Neubauer hat einen Kommentar hinterlassen
Couple of questions:
- Is this feature going to also give an error when there is no email on a ticket and an outbound email is sent out? It is not specifically mentioned in this article but there is a feedback post on it: Notify users when trying to email to a user without email address – Zendesk help
- I don't see the items mentioned by Milena Rusanova's comment: https://support.zendesk.com/hc/en-us/articles/7917145637530/comments/8874699778458 Does this mean that we will always get the error and there are no limits to it only being for emails from zendesk owned emails?
- Can you please update the article to specifically state ‘Side conversations not impacted’? We shouldn't have to read the comments to find out that it isn't
Kommentar anzeigen · Gepostet 19. Feb. 2025 · Sydney Neubauer
0
Follower
0
Stimmen
0
Kommentare
Sydney Neubauer hat einen Kommentar hinterlassen
Is this going to be addressed with the bounceback errors that are rolling out? Understanding email delivery failures in the Zendesk Agent Workspace – Zendesk help
Kommentar anzeigen · Gepostet 18. Feb. 2025 · Sydney Neubauer
0
Follower
0
Stimmen
0
Kommentare
Sydney Neubauer hat einen Kommentar hinterlassen
D.Fitz Yes we ran into this aswell. It is a bug (reported almost 2 years ago now). Turns out you have to have a placeholder within Dynamic Content if there is formatting otherwise the formatting appears. As such, Zendesk did provide us with a workaround of a ‘blank’ placeholder we can slip into each DC
{{"}}
Kommentar anzeigen · Bearbeitet 13. Feb. 2025 · Sydney Neubauer
0
Follower
1
Stimme
0
Kommentare
Sydney Neubauer hat einen Kommentar hinterlassen
+1 we run into this issue as well if you copy and paste ticket content as it says ‘Yesterday’ which does not help for historical record. And when troubleshooting tickets, trying to find the impacted time range/date, takes time as you have to hover to see the date and time
Kommentar anzeigen · Gepostet 11. Feb. 2025 · Sydney Neubauer
0
Follower
0
Stimmen
0
Kommentare
Sydney Neubauer hat einen Kommentar hinterlassen
Joel Cohen Is there an announcement around this change? This is something we are eagerly awaiting and didn't see one come out aside from your comment
Kommentar anzeigen · Gepostet 05. Feb. 2025 · Sydney Neubauer
0
Follower
1
Stimme
0
Kommentare
Sydney Neubauer hat einen Kommentar hinterlassen
+1 I can definitely see a use for this
Kommentar anzeigen · Gepostet 03. Feb. 2025 · Sydney Neubauer
0
Follower
0
Stimmen
0
Kommentare
Sydney Neubauer hat einen Kommentar hinterlassen
+1 we would also like the ability to create tickets based on other comments. We have scenarios where someone will submit a single ticket for 10+ issues and we need to split them up to ensure the right team handles it. Having the ability to split tickets off would save so much time
Kommentar anzeigen · Gepostet 28. Jan. 2025 · Sydney Neubauer
0
Follower
1
Stimme
0
Kommentare
Sydney Neubauer hat einen Kommentar hinterlassen
+1 Even for maintenance purposes - we underwent a rebranding so we needed to search for certain keywords within macros. This would be easier if we could search for content
Kommentar anzeigen · Gepostet 28. Jan. 2025 · Sydney Neubauer
0
Follower
0
Stimmen
0
Kommentare