최근 검색
최근 검색 없음

Megan Oksendahl
가입한 날짜: 2023년 5월 16일
·
마지막 활동: 2024년 7월 30일
팔로잉
0
팔로워
0
총 활동 수
16
투표 수
2
플랜 수
7
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Megan Oksendahl
Megan Oksendahl님이 에 댓글을 입력함
Looking for assistance with creating triggers for follow-up tickets. I do not see any tags or unique identifiers on follow-up tickets to setup a trigger just for follow-ups.
When a follow-up ticket is created, all the previous ticket fields are copied, including our resolutions. We need to find a way to remove the resolution when a follow-up is created. Many times, the follow-up is related to the same or similar concern/request, but the copied resolution is now incorrect.
Since the resolution is pre-filled, we are having a hard time with the agents going in and deleting/removing any stored values in the fields. They are simply changing the resolution, which does not remove stored values in follow-up fields, and so the ticket is closed with incorrect stored values.
Example, we have “refund” as one of our resolutions. When an order is refunded, the agent has to then enter the value of the refund to close the ticket. Then a fan sends a reply and a follow-up is created. This ticket is reopened with the same fields, including the refund resolution and value. Unless the agent deletes the refund value and saves the ticket on Open/Pending, then goes back and changes to a different resolution and solves, the refund value is stored on the follow-up ticket.
This is resulting in our reports showing escalated costs since the values are stored from previous tickets.
댓글 보기 · 2024년 7월 30일에 게시됨 · Megan Oksendahl
0
팔로워
2
투표 수
0
댓글
Megan Oksendahl님이 에 댓글을 입력함
I'm trying to use this feature, but the directions do not match my environment. We do use Messaging and OmniChannel Routing.
Again, here are the directions I am following from this article:
- In Admin Center, click
Channels in the sidebar, then select Messaging and social > Messaging.
- Click Manage settings.
- In the Advanced section, click Capacity release.
However, the only options under advanced settings are Email Identities and Conversation Control. There is no option for Capacity release.
Is this still available? Why can't I locate this setting following said directions?
댓글 보기 · 2024년 7월 02일에 게시됨 · Megan Oksendahl
0
팔로워
3
투표 수
0
댓글
Megan Oksendahl님이 에 댓글을 입력함
Is there any way to include page views in any business rules? I'd like to use business rules to update tickets if a fan is able to successfully checkout after interacting with our team, which is tracked within the interactions - within the timeframe before a ticket is closed.
Thanks
댓글 보기 · 2023년 10월 20일에 게시됨 · Megan Oksendahl
0
팔로워
0
투표 수
0
댓글
Megan Oksendahl님이 에 댓글을 입력함
The copies text below does not exist.
- Admin Center, click Objects and rules in the sidebar, then select Business rules > Messaging triggers.
I did read that chat triggers will not work for messaging, so I am assuming you should just use Business rules > Triggers, then select messaging as a channel when building the trigger. Is this correct?
How do I select the option "Run only once per ticket"?
In general, there have been so many changes to messaging, even in the recent months, that I find a lot of zendesk articles out of date.
댓글 보기 · 2023년 10월 20일에 편집됨 · Megan Oksendahl
0
팔로워
0
투표 수
0
댓글
Megan Oksendahl님이 에 댓글을 입력함
Repeating some of the feedback suggested above. When will color text be available as an OOTB feature in Sell like it is in Support?
Also, interesting to read the following feedback from another customer. We have our lead sales person who has been with the company for years and has never been able to integrate their email with Sell. We've involved our IT and help from Zendesk and Zendesk IT just refered us to microsoft IT for support connecting the email address. We have other users in Sell that connected just fine, but they're newer employees. The following feedback was never shared with us, and based off the size limitation could be a reason the sync is never finishing - a full year later.
1) Importing email from mail server: We have thousands of emails - and growing -in our inbox on the mail server and we had to reconnect Sell to it twice to adjust connection configuration. In both cases, we ran into the (known) issue that only up to about 1500 emails get imported (separately from "inbox" and "sent" folders), and friendly support folks did some back-end magic to have more emails imported - but never did really all emails get imported. This can be unpleasant because you're replying to an email from a customer who you had a conversation before but Sell isn't showing that and it's kind of rude to show the customer that you don't have your past communication with them at hand. We now have to check for previous communication directly on the email server in case we suspect the customer may have been in contact with us before. I'm not sure where this "1500 emails" limitation comes from but it would be really nice to somehow eliminate it.
댓글 보기 · 2023년 9월 13일에 게시됨 · Megan Oksendahl
0
팔로워
0
투표 수
0
댓글
Megan Oksendahl님이 에 댓글을 입력함
Megan Oksendahl님이 에 댓글을 입력함
We originally rolled out the answer bot in 2021 and had to deactivate it due to the influx in negative feedback from our customers.
Since then, Zendesk has focused a lot of improvement on the Agent Workspace and their AI. We've been monitoring Zendesk advancements in the flow builder and answer bot and despite some cons, we have been making our own updates to move back to answer bot.
With this change we will not be switching to answer bot. We may even disable autoreply during our peak season. Autoreply has helped us, but it does not make enough impact to resolve customer issues to justify paying for.
댓글 보기 · 2023년 5월 16일에 게시됨 · Megan Oksendahl
0
팔로워
2
투표 수
0
댓글