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

Lester
参加日2021年4月15日
·
前回のアクティビティ2022年2月03日
フォロー中
0
フォロワー
0
合計アクティビティ
42
投票
10
受信登録
19
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Lester
Lesterさんがコメントを作成しました:
Hi Oscar
Sure. 80% of our customers are locked down behind firewalls where they have no internet access, beyond email, for security reasons. It’s very typical for our customer segments.
What we find is customers do want to participate in conversations off tickets, particularly around issues that are not really support related. For example, discussing alphas/betas or best workflows. We have been doing this through Google Mailing lists. But it’s a nightmare to use. We hate it, Customer hate it. But they are reluctant to move off it because they can’t use anything else.
We developed a solution around the Zendesk Communities for a very specific customer base who had internet access and they loved it. We used the Post Actions so customers can see what’s happening with each post and our Engineers have a way to provide feedback. It works really well and we wanted to roll that out to a wider group of customers. But the problem is, a lot of the target customers won’t be able to access the site to interact with us.
Even if they could access the internet, what we hear is; “If it’s in my inbox, I’ll help and provide a response. But I’m not going to bother going to a website to see what questions I can answer or take the time to login and post a reply”. If a user has to go out their way to provide answers, it’s a real barrier. The other problem is as people have mentioned, a customer who interacts with Zendesk assumes that they can reply to everything via email. Who really looks at the dontreply@ email address.
Our ideal solution
- Community threads are clearly branded differently to support tickets to avoid any confusion over who the recipients are.
- Customer can reply directly to a Community thread from their inbox and their response will be added to the topic.
I’m happy get someone to walk you through what we built and where we think it can be improved if it’s helpful.
コメントを表示 · 投稿日時:2019年2月20日 · Lester
0
フォロワー
1
投票
0
コメント
Lesterさんがコメントを作成しました:
Hi Bob
I don’t like having tickets open that relate to bugs as I have no control over when they will be fixed. I don’t like 2 year old tickets floating about and it relies on us knowing something changed to inform the customer.
What I did was sync our internal bug tracker to the help center. Essentially there is a script that looks in the database the engineers use (in our case Target Process) and checks to see if the bug is marked as public. If so, it creates a help center article that details the bug. The same script looks for changes. If a change is found, for example the state or release date is update, the bug in the help center is updated. The great thing about the help center is customers can follow articles, as soon as the state changes, they get an email so we don’t have to keep track of changes.
Benefits.
- We don’t have to keep tickets open longer than we have to. As soon as we find it’s a bug, we report it and give the customer a link to the article
- They can follow the article for instant notifications
- Bugs can be public or private
- If they are public, then it stops other customers asking the same question
- Using voting, you’ll get an idea of how many people have the same problem
We defined some custom views for bug articles and let customers filter on bugs for specific products, state and even product release.
It was a lot of customization, but we are happy with it
コメントを表示 · 投稿日時:2018年3月02日 · Lester
0
フォロワー
0
投票
0
コメント
Lesterさんがコメントを作成しました:
I do something similar
Firstly, you’ll need to go into Settings -> Extension and setup a new HTTP target.
- URL: https:// domain>/api/v2/tickets/{{ticket.id}}.json
- Method: put
- Comment type: JSON
- Authentication: whatever
Then you’ll need to create/update a trigger with:
Notify Target: what whatever you called your HTTP target
JSON body
{
"ticket": {
"comment": {
"public": false,
"body": "This customer is a member of: \n {{ticket.requester.notes}}"
}
}
}
If it’s a custom field on the Org. then then you’ll need to refer to it as:
{{ticket.organization.custom_fields.}}
Hope that makes sense
コメントを表示 · 投稿日時:2018年3月02日 · Lester
0
フォロワー
0
投票
0
コメント
Lesterさんがコメントを作成しました:
Difficult to be 100% sure, but my guess is with the next reply time. The next reply time is based on the oldest unanswered customer comment. So wondering if you have a comment from 6 months ago which you paused, and a comment from 2 months ago. If there is no public reply from an agent in between, the oldest date is used.
コメントを表示 · 投稿日時:2017年2月17日 · Lester
0
フォロワー
0
投票
0
コメント
Lesterさんがコメントを作成しました:
We have situations where we provide specific companies access to specific forms based on a tag on the organization.
Perhaps you could use a similar approach by reading a tag from the users profile, if it has a ‘no support’ tag, you hide the submit a request option.
Doesn’t work for email tickets, but just throwing it out there.
コメントを表示 · 投稿日時:2016年9月16日 · Lester
0
フォロワー
0
投票
0
コメント
Lesterさんがコメントを作成しました:
Just throwing my +1 in the hat.
Kinda annoying that the helpcenter behaves differently to the standard zendesk email. If you mix both HC and normal Zendesk support, customers don't know if they can reply or not.
コメントを表示 · 投稿日時:2016年1月20日 · Lester
0
フォロワー
1
投票
0
コメント