Julian Kossak

P.S.: Like refreshing browser tab submitting the ticket also triggers the display of the deliverly failure notice in the ticket…
Seems that's the point: the newest comment triggers not the display of delivery failure when the ticket is updated…

Hi, 

I can confirm that.
 

It seems there are two variations: In the case of the first message in the ticket to the requester that cannot be delivered, the delivery failure is displayed directly in the events AND in the ticket under the comment.

For each subsequent message to the requester, the delivery failure notification only appears after another update of the ticket (by refreshing the browser tab or sending another message, for example).
 

When multiple messages are sent to the requester, the delivery failure is always shown only up until the penultimate comment, never on the latest comment. At the latest comment the delivery failure is only shown in the ticket events and not visible in the ticket.

I put some screenshots in here for visualisation.

Please check and fix this display issue!

Thanks and regards,
Julian

Hi,

if the comment field is minimized and using a macro with a public comment, the comment field will open up automatically.

If the macro only includes a internal notice, the comment field will not open up by itself. You have to open it by yourself.

I think it would be consistent to manage both cases identically.

Thanks and regards

Julian

Hi Shawna,

I don't see any inappropiate critic in the posts here.

Perhaps some irony - but that only reflects the irony which a customer (this is us btw) definitely feel while following this thread and topic over the last decade.

I remember a time where we got bounce information and can handle it initiative.
Then, I think in ~2017 Zendesk launched an revised bounce feature thing. But it failed and has been deactivated some weeks later. 

Since then we are waiting for this feature…

Reminder: we're talking about a bounce notification. Every, EVERY!!! simple mail server gets this information.

Zendesk is a huge system with thousands of customers who have millions of customers and the central feature is to send an email - and there is no bounce notification???

I'm sorry, but this is a bad joke in my eyes.

I know a lot of Zendesk costumers who think like me, even if here in the forum just a small proportion if them made an input…

What shall we do? Another ten years of please please please it's IMPORTANT?

I would like to know, too, what the reasons has been over so many years not to implement such a simple but important feature.

If I would act like this with my tasks I would be unemployed within a short time…

Regards
Julian

That would be a great thing!

Hi,

we are still experiencing problems with the notification of incoming chat messages.

If the ticket tab is in background because the agent needs to search something in the knowledge base (e.g.) and a new chat message is coming in in one of his/hers assigned chat tickets, there is often no acustic notification.

Please solve this issues asap!

Thanks and regards
Julian

Looks like a never ending story...

How is it possible, that a big player like ZenDesk is obviously not able to realize such a simple solution for this important aspect of their users?

And one more +1...

It's a shame, such an important and frequently asked feature, which is nothing super special complex, not to implement for nearly a decade.

We are not in the 1950s. Today in our digital world, 8 years is are a really long time...

Hey Phil,

yes, exactly. :-)

E.g. for me it's not clear why under "Team" the point "team members" is located over "roles" and "groups". 

Same in the other sections like "Configuration" oder in "Channels" etc.pp.

Thanks + regards
Julian

Hello,

I would be thankful if Zendesk could step to an alphabetical order in their menus.

It's a daily struggle to find the different menu points in the menus. An alphabetical order would be a huge help.

Thanks + regards
Julian