Out of Office app - official feature request thread
已于 2020年3月13日 发布
This is the official feedback topic for Out of Office. Please refer to the guidelines on feedback posts for Built by Zendesk apps (https://support.zendesk.com/hc/en-us/community/posts/360040001354-Feedback-on-Built-by-Zendesk-Apps-General-Guidelines) before posting here. We’ll try our best to check this and respond to your queries. Thank you for taking a moment to submit your feedback!
If you see a suggestion for a feature below that you would also find useful, please feel free to upvote it so that we can focus on features that would help the most users!
If you're looking for information on setup or use, please see the instruction article here: https://support.zendesk.com/hc/en-us/articles/204076066-Installing-and-using-the-Out-of-Office-v2-app
4
53 条评论
Hannah Lucid
What reporting is available for the out of office app?
0
Heather Valli
It would be lovely if we could set an expiration date on the OOO app. If I know I'm going to be on vacation from 5/20-5/25, I'd like to set that in the app so I don't forget to un-OOO myself when I get back. Sort of like how Outlook lets you set OOO messages for a date range.
0
Helen Davies
We have agents that put their out of office on and when they return from leave tickets have reopened in their name because a trigger has run (e.g. reopening a pending ticket after a time). Am I right in that the OOO app will not work when a trigger reopens a ticket or for tickets in pending that might reopen because a customer replies? If so has anyone found a workaround to this issue or is this part of the development needed for the app? Many thanks.
0
Kolten Kittleson
Hello folks,
Thank you for the active posts regarding the Out of Office app. As the new Product Lead for the team, it is great to see our user-base have such an active interest in making things better.
Well we aren't currently working on enhancements to the Out of Office application, the ability to custom roles as well as non-admins more configuration power is on the roadmap for 2024.
As we progress through some projects, I will be sure to keep this page updated on the progress and when we have more concrete timelines to share.
0
Yasser Taraka
We would like to have the ability to have other non-admin custom roles to also have the ability to set agents as Out of Office in case agents forget to do so. This is invaluable for our operations, would reduce potential human error and would offer a much needed flexibility for our leads.
0
Samual Preiss
Hello all, A quick question about the tags

Am I able to add a second tag to this field so I can automate internal comments? Or is that limited to just one?
1
Joey SALBERTER
Hello Zendesk,
Are you planning to make the Out of Office application usable by non-Admin users?
Currently, only Administrators can set agents to Unavailable, which is a serious security issue as we have to provide an Admin role to people who should not.
Thank you.
1
Priya Bhandari
Hi Zendesk Team,
While browsing through the Out of Office App functionality, I noticed that the app doesn't syncs with Google Calendar.
For example, if an agent has marked themselves OOO on Google Calendar, the Zendesk OOO still shows him as available until he manually toggles the OOO app to unavailable.
Just wanted to confirm - are there any plans on the roadmap to integrate the two to ensure that the Zendesk OOO app automatically updates if an agent is booked on vacation / OOO on Google Calendar?
0
John DiGregorio
@Binh Du did you ever figure out how to include open tickets
0
Scott
Our Playlist Routing App has a similar Out of Office feature. While I don't know exactly how Zendesk's app is implemented, I can say that there are API limitations preventing us from designing a scalable and robust solution. We get a lot of clients reporting inconsistencies too.
Our biggest challenge is with bulk updates. They are delayed and not guaranteed. We'd have to poll job statuses for UpdateConflict errors and retry failed updates. Polling counts against your rate limits, and it's slow. By the time the app retries, it's possible for an agent to be back online already. Polling and retrying is inefficient, defeating the purpose of bulk updating to minimize API requests, so our solution doesn't even bother retrying. Ideally, there is a synchronous bulk update option that we can use to guarantees an update every time.
Another fundamental issue is that there isn't an API to query for specific tickets using fresh data. Search API is not reliable due to the time required (1 - 5 minutes) to index records for search. We don't have an efficient way to get a full list of the agent's non-closed tickets at scale.
Once these API limitations are addressed, we could make dramatic improvements to our version of Out of Office.
0
登录再写评论。