Vahe Khumaryan

really needed for order screenshots

Hi Zendesk team. It's been more than a quarter after the last update here. Do you probably have an update on timeline? This would greatly optimize our own planned effort if know exactly whether Zendesk commits to resolving this security vulnerability asap. 

this is a must have to track the system automations uptime

Here is a workaround. 

1. Duplicate the macro and the DC item, make sure you have put the new DC item into the new macro. 

2. Provide explicit HTML formatting instead of the current text. For example use
for new lines. 
Like this:

Hello



Your issue is solved.



Best,

Agent

Hi Zendesk team. Can you please provide an update on when approximately we can expect a change to the bulk editing experience that will keep DC items formatting consistent?

I think there is a significant difference in one's approach to metrics in Zendesk, whether you have or have no operational capacity to maintain complex dashboards and reports (tagging triggers if any, and so forth). One should first answer this question: if I need to have +1, +2, etc team members focusing solely on QA, or data moving forward to have a complete control on what's going on with the rest of the team performance, does this effort pay off? The answer may depend both on the scale of the product / service and consequently the volume of requests, and the size of the team and other factors. I believe there is a threshold, which I honestly find hard to define for the moment, not passing which would rather incentivize you as a support manager to stick to default time metrics, maximum + SLA feature in Zendesk and the default dashboards. 

Hi Team Zendesk. Can you please specify what do we do to replace this native trigger and setting with our own, one that we can customize?
We need a list of all the actions the settings toggle and conducts behind the scenes. 

I am just about to migrate to Messaging. I noticed this before but I thought it just can't be, makes no sense, maybe I am getting something wrong with settings etc..

Of course we need to see all conversations with the bot irrespective whether an escalation occurs or not, how else should we be able to evaluate bot performance and improve it..

Hi Zendesk product team. Do you have any good news on this?

A native solution by Zendesk would be great, taken that extensions like Grammarly affect ticket view behaviour even in Chrome