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

Anton Maslov
参加日2023年6月12日
·
前回のアクティビティ2025年1月14日
フォロー中
0
フォロワー
0
合計アクティビティ
42
投票
6
受信登録
19
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Anton Maslov
Anton Maslovさんがコメントを作成しました:
This feature is not compatible with SSO:
1. Clients can see MFA under their profile, and enable it but they won't be able to use it, because with SSO Zendesk Auth is disabled.
2. Moreover, if your SSO has its own MFA some clients try to put in code generated by Zendesk MFA and cannot log in.
The fact that this exists and cannot be managed/disabled is a huge issue that results in negative end-user experience.
コメントを表示 · 編集日時:2024年11月05日 · Anton Maslov
0
フォロワー
5
投票
0
コメント
Anton Maslovさんがコメントを作成しました:
Erin O'Callaghan any plans to add the same functionality for the Regex field type? It would be nice to automatically add like order ID or license number.
コメントを表示 · 投稿日時:2024年8月16日 · Anton Maslov
0
フォロワー
2
投票
0
コメント
Anton Maslovさんが投稿を作成しました:
Similarly to “draft” mode now in Agent Workspace we'd like to have a confirmation for the outbound call request: sometimes agents may missclick the call button switching from i.e. Messaging to email or smth else.
投稿日時:2024年6月04日 · Anton Maslov
0
フォロワー
2
投票
2
コメント
Anton Maslovさんがコメントを作成しました:
Is there new on phase 2, when we can expect it?
>The ability to pin important notes at the top of the conversation.
This is quite hot feature we are looking forward too.
>Collapsed view of already-read messages
We had a system with this feature in the past: I hope messages will collapse per user basis, because we had incidents when someone collapsed message with important info, which other agent missed.
コメントを表示 · 投稿日時:2024年5月23日 · Anton Maslov
0
フォロワー
1
投票
0
コメント
Anton Maslovさんがコメントを作成しました:
- It depends on how quick you want to react and what is normal volume for you.
- Depends also on how many organizations you want to monitor
For us some most of the organizations had like 5-20 tickets per week so it was no sense to monitor it daily.
What we did for example is we focused on top 20 organizations and created a “Health Dashboard” for them with key KPIs like CSAT, Time to First Reply, Average Resolution Time, amount of tickets.
Now, for CSAT and the rest where you have goal you can use color schemes.
For tickets you can do the following:
1. Create metric like “average amount of tickets per week for the last quarter”
2. Put it next to last_week ticket amount
3. Send dashboard weekly by email to the team of Account Managers.
If you need to catch like daily spikes and you have 1000 tickets per week let's say - then tools above is likely your choice.
コメントを表示 · 投稿日時:2024年5月09日 · Anton Maslov
0
フォロワー
0
投票
0
コメント
Anton Maslovさんがコメントを作成しました:
Here is how you can create a ticket with Messaging if needed:
First, you need to create API key and add it to “Connections” to allow Messaging doing API calls to your own Zendesk instance:
1. Go to Admin > Apps & Integrations > Zendesk API. Create an API token here.
2. Now got to Apps & Integrations > Connections and create a new one:
- Specify Connection name
- Select type as “Basic authentication”. Your username would be your admin email /token like “admin@example.com/token”. Your password - API key you created on step 1.
- Specify your Zendesk instance subdomain name as “Allowed domain”: example.zendesk.com
You are now ready to create a ticket by Messaging.
1.First, create a custom ticket fields with “text” type which you will use to ask for issue description. Make it editable by end users and name it for example “How can I help?”
2. Now add step “Ask for details” if needed where you'll ask “Name”, “Email” and also add “How can I help” field there as well.
3. Now add step “Make an API calls”:
- Method “POST”
- Endpoint URL your Zendesk subdomain: https://example.zendesk.com/api/v2/tickets.json
- Now, as a body you will put JSON with your ticket parameters. Let's say you want to keep it simple and use customer's name in subject and text he put to field “How can I help” as ticket description. Just click {+} and add variables you need to the JSON body.
- Under “Authentification” select Connection name from step 2 you created.
{
"ticket": {
"subject": "Offline request from {{sf.requester.name}}",
"requester": {
"name": "{{sf.requester.name}}",
"email": "{{sf.requester.email}}"
},
"tags": [
"offline_ticket"
],
"comment": {
"body": "{{tf.22638143652759}}",
"public": true
}
}
}
4. Now you can use “Make an API call" to test that it works and also save ticket_id as a variable and use it later to tell client his ticket ID that was created.
コメントを表示 · 投稿日時:2024年5月09日 · Anton Maslov
0
フォロワー
5
投票
0
コメント
Anton Maslovさんがコメントを作成しました:
Overall feedback from the agents is very positive, although we found a bug:
1. We use Zendesk Chat and send initial message with chat:send command which basically sends it on behalf of the agent.
2. Although in MCE it is displayed as a message from client, not from agent. see screenshot.
コメントを表示 · 投稿日時:2024年4月19日 · Anton Maslov
0
フォロワー
0
投票
0
コメント