최근 검색
최근 검색 없음

Atanas Tomov
가입한 날짜: 2023년 5월 25일
·
마지막 활동: 2025년 2월 21일
팔로잉
0
팔로워
1
총 활동 수
506
투표 수
256
플랜 수
120
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Atanas Tomov
Atanas Tomov님이 에 게시물을 만듦
Hello,
Currently, when an end-user submits a form via the Help Center Page - ticket will be created in Support with ticket channel “Web Form”.
Same also applies when an agent send an outbound e-mail to an end-user.
What we need is a clear native differentiation and indication in Explore which form the end-user has submitted and it will be immediately clear to anyone creating or filtering an existing report.
This will solve countless filtering options that need to be selected or excluded in order to find that information. This increases the chance of exporting incorrect data which is then presented to stakeholders, potentially influencing decisions and untimately impacting the business.
What we can utilize is a new data filter or altering existing one which will give more control over what data is presented and setting clear differentiation between tickets coming from different web forms.
Workaround we are currently using is to filter reports by channel and for selected forms which in our case could be dozens increasing chance for error.
2025년 2월 21일에 게시됨 · Atanas Tomov
0
팔로워
0
투표 수
0
댓글
Atanas Tomov님이 에 게시물을 만듦
Hi Team,
We are currently looking into implementing the “End Session” feature for Messaging. However, we noticed that when enabled, the feature is activated at the instance level and not per brand.
By making it per brand, we will have more granular control, which is something Admins should always have for every new functionality that is released.
We are not currently directly affected by the lack of this functionality. However, in the future, should stakeholders want this feature enabled on one brand and not the other for one reason or another, we would like to have this as an option.
The ideal solution would be to simply have a toggle for brands when “End Session” is enabled.
2025년 1월 10일에 게시됨 · Atanas Tomov
2
팔로워
3
투표 수
1
댓글
Atanas Tomov님이 에 게시물을 만듦
Hi Team,
Recently, we needed a more in depth reporting capabilities in terms of checking agent capacity historically to determine whether an agent was at full capacity at the time when a messaging conversation was requested.
We were attempting to use the default Omnichannel dashboard to find this information, however it was missing some metrics and attributes to accurately establish an outcome.
One of these attributes is Ticket ID, which will help us see on which tickets the agents were working on during a specific time-frame. Another attribute which is missing is the agent status.
We would appreciate if these can be added and the omnichannel dataset is further developed as it can show a lot of in depth and important data which is crucial for properly managing team workload.
2024년 12월 10일에 게시됨 · Atanas Tomov
2
팔로워
2
투표 수
1
댓글
Atanas Tomov님이 에 댓글을 입력함
Hi Orsolya Forster,
Idea behind this suggestion is to have control over published articles and their visibiliy.
Our particular use case in this situation would be the following:
- An end-user has a very specific or sensitive issue/topic he needs to have information for.
- We create an article specifically for this case, however since it could be sensitive - we do not want to expose this article to all end-users.
- We need to have visibility restrictions on articles which will allow us to publish this article but not make it publicly visible.
- By utilizing this restriction, only Admins and relevant team members with access will be able to view the article, then the URL of this article can be taken from the address bar and sent directly to the end-user, so that he can view it as well.
This is somehow similar to custom forms which can be seen and accessed by end-users only via a direct link to the form itself.
Let me know if you need more information on this topic.
댓글 보기 · 2024년 11월 12일에 게시됨 · Atanas Tomov
0
팔로워
1
투표
0
댓글
Atanas Tomov님이 에 게시물을 만듦
Hi Team,
I wanted to bring to your attention a recent announcement from Zendesk regarding user suspension for the messaging channel. Link to article can be found here.
We’ve had some interest and questions about this new functionality, which were addressed by a support representative. According to the information provided, the permission to suspend users is granted based on the agent’s role. This is quite disappointing for us, as we use Unified accounts where all contact details (email, phone number, external ID, etc.) are consolidated in an end-user’s account. Consequently, this feature becomes completely obsolete for our needs.
The current role-based permission means that if an agent is granted this ability, they will suspend not only the messaging channel but all other communication channels for an end-user. This broad scope of suspension is not practical for our operations.
For the future, we strongly recommend making permissions more granular, for example specifically making this one based on channel rather than role to accomodate a broader audience of your customers including us, who find the current implementation unusable.
Thank you.
2024년 11월 04일에 게시됨 · Atanas Tomov
4
팔로워
3
투표 수
1
댓글
Atanas Tomov님이 에 게시물을 만듦
Hi Team,
Currently there is no way to differentiate between Authenticated and Non-authenticated end-users in Messaging when reporting in Explore.
We are currently looking to activate Messaging for both types of customers and therefore we will need to divide them within reporting.
Having some kind of native solution will really help us to determine volumes of each contact origin in terms of authenticated or not customer.
We are currently being affected by this lack of functionality and subsequently looking for workarounds which we are currently in the works of.
Ideal solution would be to tag these interactions with a system tag, so that they can later be divided in Explore.
2024년 9월 13일에 게시됨 · Atanas Tomov
3
팔로워
3
투표 수
1
댓글
Atanas Tomov님이 에 댓글을 입력함
We are currently exploring this feature for possible implementation and also encountered this limitation for Callback functionality. Being able to select particular working hours for this feature will greatly improve its efficiency, usability and most importantly the end-user experience. Offering a callback when the support team is close to EOD (last hour) is not a good end-user experience as there will be no one to pick it up.
Another thing I would like to bring to your attention is the inability to customize the 3 sub-greetings when requesting the callback. The pre-recorded messages are too robotic and mundane.
@..., do you have any updates about it and is it on your roadmap currently?
댓글 보기 · 2024년 8월 01일에 편집됨 · Atanas Tomov
0
팔로워
2
투표 수
0
댓글
Atanas Tomov님이 에 게시물을 만듦
Hi Team,
We have noticed that in the new Consolidated Macros Management interface, in some cases the macro name column will overlap the date created column if it is too long:

Additionally, it would be great if a couple of new columns will be added such as “Created by” and “Last update by”. This will be highly useful for audit purposes.
No workaround is currently possible for either feature improvements.
2024년 6월 21일에 게시됨 · Atanas Tomov
2
팔로워
3
투표 수
7
댓글
Atanas Tomov님이 에 게시물을 만듦
Hi Team,
We have noticed that Videos on the Help Center can only be displayed through online video streaming platforms such as YouTube, Vimeo etc.
If we would like to display a particular video on our help page, we have to upload it to one of these platforms and then link it to our Help Center.
However, this could sometimes be a blocker or the process could take time or these videos are intended to be visible only to our end-users , so we would appreciate the ability to manually upload videos in certain formats to Help Center library which we will then be able to use freely.
2024년 6월 21일에 편집됨 · Atanas Tomov
5
팔로워
3
투표 수
2
댓글
Atanas Tomov님이 에 댓글을 입력함
Hi Karen,
Metrics which I think could be useful for the dataset are:
- Tickets reassigned to secondary group
- Reopened tickets which were initially assigned to secondary group
- Primary and secondary group first reply time
- Requester wait time in queue
These are just some of the main ones which I could think of, however more metrics will always be appreciated to accurately measure the performance of these queues.
댓글 보기 · 2024년 6월 20일에 게시됨 · Atanas Tomov
0
팔로워
3
투표 수
0
댓글