Ola Timpson
-
Total activity133
-
Last activity
-
Member since
-
Following0 users
-
Followed by0 users
-
Votes35
-
Subscriptions52
Activity overview
Latest activity by Ola Timpson-
Ola Timpson commented,
We have over 20 brands, so going into each guide admin to check if there are articles that need reviewing isn't practical. We need to be able to get this programmatically.
-
Ola Timpson commented,
I know there is a webhook now for published articles, but when will we get one for an article awaiting review?
-
Ola Timpson commented,
This latest update causes more problems for us than it solves. Firstly, dashboard restrictions don't meet every use case for bookmarks. They can't be set up for different filter combinations to all...
-
Ola Timpson commented,
Love this idea! Different departments use our Zendesk too, so it would be a great fit for that. Also being able to have a slightly different survey (extra question maybe) for different types of tic...
-
Ola Timpson commented,
It seems so strange to me that this has been rolled out without the ability for admins to set the app shortcuts. Combining this feature with custom layouts would be so powerful. Also this being an ...
-
Ola Timpson commented,
Agreed! We have put effort into defining the order we want agents to work tickets. We want to switch to omnichannel routing, but losing that order would hurt our SLA so badly.
-
Ola Timpson commented,
David Launen for us, when the change was first rolled out it made a big difference. But then about a month ago we started getting lots of false negatives again. The theory we have is that one of th...
-
Ola Timpson commented,
Hi Barry Neary Definitely understand that reasoning - perhaps as Tobias suggested we could designate an 'off-shift' status that causes tickets to be reassigned? But a timer delay would be helpful t...
-
Ola Timpson commented,
What are plans to re-assign currently open tickets when an agent goes offline in the first place? This feature only seems to cover tickets that aren't open when the agent goes offline.
-
Ola Timpson commented,
PAUL STRAUSS you can definitely do that, using something like this: {% case ticket.brand.name %} {% when "brand1" %} Brand 1 phone number {% when "brand2" %} Brand 2 phone number {% else ...