最近の検索


最近の検索はありません

Bobby Koch's Avatar

Bobby Koch

参加日2021年11月03日

·

前回のアクティビティ2025年2月17日

Zendesk Luminary

フォロー中

1

フォロワー

1

合計アクティビティ

332

投票

76

受信登録

114

アクティビティの概要

さんの最近のアクティビティ Bobby Koch

Bobby Kochさんがコメントを作成しました:

コメントWorkflow best practices and recipes

need to be able to send more than 1 of these per ticket…

コメントを表示 · 投稿日時:2025年2月17日 · Bobby Koch

0

フォロワー

1

投票

0

コメント


Bobby Kochさんがコメントを作成しました:

コメントWorkflow best practices and recipes

Is there a way to change this from saying “Zendesk”

コメントを表示 · 投稿日時:2025年2月13日 · Bobby Koch

0

フォロワー

0

投票

0

コメント


Bobby Kochさんがコメントを作成しました:

コミュニティのコメント Feedback - Chat and Messaging (Chat)

adding my two cents - not speaking for Chris. 

 

We would like to see something like you both said, where we can either solve a ticke/mark as abanonded, or if the user leaves the session before an agent responds, deprioritize it or add it back to the queue should they go active again

コメントを表示 · 投稿日時:2025年2月10日 · Bobby Koch

0

フォロワー

0

投票

0

コメント


Bobby Kochさんがコメントを作成しました:

コミュニティのコメント Feedback - Admin Center

+1

コメントを表示 · 投稿日時:2025年2月04日 · Bobby Koch

0

フォロワー

0

投票

0

コメント


Bobby Kochさんがコメントを作成しました:

コメントBusiness rules

Liia just disable it and create a trigger. Should work, I do it that way in my sandbox account. 

コメントを表示 · 投稿日時:2025年2月03日 · Bobby Koch

0

フォロワー

0

投票

0

コメント


Bobby Kochさんが投稿を作成しました:

投稿 Feedback - Chat and Messaging (Chat)

 

Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)

Nested fields (i.e., Pizza Toppings - Cheese::Mozzerella, Cheese::Cheddar) are a great way to route tickets in GUIDE. In messaging, the nested front-end does not work, and instead you see the values you enter in admin. This is a horrrible customer experience. 

What problem do you see this solving? (1-2 sentences) 

Feature parity. This is not a “problem” this is a must have and frankly unacceptable today. 

When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)

Today. There are two options:

- Create a second field for nested questions (defeats the whole purpose)
- Create separate fields for your messaging experience and your web portal experience. This causes disjointed data, and is also a bad option. 

Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)

Yes, I have to create separate fields and not use the ultra convenient nested fields. 

What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)

Just make it work. This is not a suggestion, it's basic functionality that works in one plac eand not in another. 

投稿日時:2025年1月30日 · Bobby Koch

0

フォロワー

1

投票

1

コメント


Bobby Kochさんが投稿を作成しました:

投稿 Feedback - Ticketing system (Support)

 

Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)

With complex workflows, we have adopted many custom statuses now. However, the limitation can be confusing when you have many custom statuses in the same category. It's confusing for support agents and engineers to quickly use the status they should. 

What problem do you see this solving? (1-2 sentences) 

Faster time to resolution, similar answer to above. 

When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)

Every day. There are certain workflows that are status dependent, and if someone clicks the wrong one, it can cause a ticket to be orphaned or solved slower. 

Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)

No

What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)

Just give a color selector/hex code field for us to set whatever color we want. If Zendesk is stuck on the colors for categories being consistent, at least give us different hueues/shades of the colors to pick from, within each status category. 

投稿日時:2025年1月30日 · Bobby Koch

3

フォロワー

5

投票

5

コメント


Bobby Kochさんがコメントを作成しました:

コメントMeasuring success

what is the ETA for being able to customize this page with our design requirements?

コメントを表示 · 投稿日時:2025年1月27日 · Bobby Koch

0

フォロワー

0

投票

0

コメント


Bobby Kochさんがコメントを作成しました:

コメントTicket automation and collaboration

when can we see this in explore? we'd like to store summaries (the last one generated) we see immense value here

コメントを表示 · 投稿日時:2024年11月26日 · Bobby Koch

0

フォロワー

1

投票

0

コメント


Bobby Kochさんが投稿を作成しました:

投稿 Feedback - Apps and integrations (Platform)

Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)

Copying text from zendesk ticket should be formatted, not unformatted

 

What problem do you see this solving? (1-2 sentences) 

clarity for the team on the receiving end of the ticket

 

When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)

every day, it slows down our engineers working on tickets created from customer problems

 

Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)

no

 

What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)

Just use the formatted text placeholers instead of the unformatted 

投稿日時:2024年10月16日 · Bobby Koch

1

フォロワー

1

投票

1

コメント