最近の検索
最近の検索はありません

Scott Allison
参加日2021年4月14日
·
前回のアクティビティ2025年1月28日
フォロー中
0
フォロワー
5
合計アクティビティ
591
投票
83
受信登録
279
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Scott Allison
Scott Allisonさんがコメントを作成しました:
I wanted to provide you all with an update here, and point you to a release that we started rolling out today that provides a solution for First Reply Time on voicemail tickets.
We're introducing advanced settings to three of the SLA metric types, first reply time, next reply time and periodic update. These new settings are optional, and give you the ability to change the logic for when an SLA metric is activated or fulfilled, on an individual policy basis.
Once the rollout is complete, go to the Admin Center page for SLAs, select your policy, edit First Reply Time and then click on Advanced Settings. Then check the box next to “When any ticket is created for an end user with an internal note”. Any new voicemail tickets will then have FRT applied.
This is what it looks like on a ticket:

Read more in the announcement here:
コメントを表示 · 編集日時:2024年7月22日 · Scott Allison
0
フォロワー
0
投票
0
コメント
Scott Allisonさんがコメントを作成しました:
I wanted to provide you all with an update here, and point you to a release that we started rolling out today.
We're introducing advanced settings to three of the SLA metric types, first reply time, next reply time and periodic update. These new settings are optional, and give you the ability to change the logic for when an SLA metric is activated or fulfilled, on an individual policy basis.
It addresses these needs
- Ensure end user tickets can have first reply time applied for all common use cases
- Apply SLAs when a CC’d end user replies to a ticket (next reply time)
- Apply First and Next Reply Time SLAs when an agent or light agent is the requester on a ticket
- Apply or fulfill First, Next and Periodic Update SLAs with internal notes
Read more in the announcement here:
コメントを表示 · 投稿日時:2024年7月22日 · Scott Allison
0
フォロワー
1
投票
0
コメント
Scott Allisonさんがコメントを作成しました:
I wanted to provide you all with an update here, and point you to a release that we started rolling out today.
We're introducing advanced settings to three of the SLA metric types, first reply time, next reply time and periodic update. These new settings are optional, and give you the ability to change the logic for when an SLA metric is activated or fulfilled, on an individual policy basis.
It addresses these needs
- Ensure end user tickets can have first reply time applied for all common use cases
- Apply SLAs when a CC’d end user replies to a ticket (next reply time)
- Apply First and Next Reply Time SLAs when an agent or light agent is the requester on a ticket
- Apply or fulfill First, Next and Periodic Update SLAs with internal notes
Read more in the announcement here:
Given the main request here was around Next Reply Time I'm going to mark this request completed. If you want to want to create a new request for any remaining needs, please do that here using the product feedback template. Thank you!
コメントを表示 · 投稿日時:2024年7月22日 · Scott Allison
0
フォロワー
0
投票
0
コメント
Scott Allisonさんがコメントを作成しました:
I wanted to provide you all with an update on our SLA capabilities and point you to a release that we started rolling out today. While it doesn't address pausing of SLA targets, it give admins a lot more control now over what activates or fulfills an SLA, on an individual policy basis.
These enhancements effect three of the SLA metric types, first reply time, next reply time and periodic update. These new settings are optional, and give you the ability to change the logic for when an SLA metric is activated or fulfilled, on an individual policy basis.
Read more in the announcement here:
Our next major piece of work on SLAs is going to be for providing near real-time notifications and actions, but for now we have no specific timeline for “pausing SLAs”. If this is still something you need, please fill out this form so we can understand more about your needs.
コメントを表示 · 投稿日時:2024年7月22日 · Scott Allison
0
フォロワー
5
投票
0
コメント
Scott Allisonさんがコメントを作成しました:
I wanted to provide you all with an update here, and point you to a release that we started rolling out today.
We're introducing advanced settings to three of the SLA metric types, first reply time, next reply time and periodic update. These new settings are optional, and give you the ability to change the logic for when an SLA metric is activated or fulfilled, on an individual policy basis.
It addresses these needs
- Ensure end user tickets can have first reply time applied for all common use cases
- Apply SLAs when a CC’d end user replies to a ticket (next reply time)
- Apply First and Next Reply Time SLAs when an agent or light agent is the requester on a ticket
- Apply or fulfill First, Next and Periodic Update SLAs with internal notes
Read more in the announcement here:
コメントを表示 · 投稿日時:2024年7月22日 · Scott Allison
0
フォロワー
1
投票
0
コメント
Scott Allisonさんがコメントを作成しました:
I wanted to provide you all with an update here, and point you to a release that we started rolling out today. It allows you to ensure next reply time SLA is started when any end-user replies on a ticket, not just the requester, even if it that reply is added as an internal note.
We're introducing advanced settings to three of the SLA metric types, first reply time, next reply time and periodic update. These new settings are optional, and give you the ability to change the logic for when an SLA metric is activated or fulfilled, on an individual policy basis. Read more in the announcement here:
コメントを表示 · 投稿日時:2024年7月22日 · Scott Allison
0
フォロワー
0
投票
0
コメント
Scott Allisonさんがコメントを作成しました:
Johannes Garske Thanks for the feedback! Can you tell me more about this need, specifically?
コメントを表示 · 投稿日時:2024年7月22日 · Scott Allison
0
フォロワー
0
投票
0
コメント
Scott Allisonさんがコメントを作成しました:
Scott Allisonさんがコメントを作成しました: