最近の検索


最近の検索はありません

Heather Rommel's Avatar

Heather Rommel

参加日2021年10月16日

·

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

Zendesk LuminaryThe Product Manager Whisperer - 2021Community Moderator

I love solutioning in Zendesk for different use cases. Working on Zendesk since 2015: Support, Guide, Chat, Talk, Explore (and Insights RIP).

フォロー中

0

フォロワー

10

合計アクティビティ

1828

投票

915

受信登録

492

アクティビティの概要

さんの最近のアクティビティ Heather Rommel

Heather Rommelさんが投稿を作成しました:

投稿Feedback - Zendesk QA

Hi team!

  • Feature Request Summary
    • We need APIs for Sentiment, Churn risk and other data.
  • Use Case
    • Zendesk QA is a powerful tool that we're starting to set up and were told there are APIs available. However, the APIs are restricted to data related to scorecards.  What we need to be able to do is pull the customer sentiment data and use it to display on a home grown app (a Zendesk app would be good too!) within Support itself so our support engineers have the information in front of them when they pick up/work a ticket.  In other words, if a customer sentiment is negative or churn risk is identified, we can use that data to potentially deflect manager escalations and churn by how we handle each ticket with the customer.  
  • Product limitation or missing feature
    • Right now, we have to leave Zendesk and go to Zendesk QA which is not ideal and frankly just not sustainable nevermind the fact that the data in QA is not available to all users that look at a given ticket in Support. So the API is really necessary!! 
  • Business impact of limitation or missing feature
    • We are “flying blind” during the lifecycle of the actual ticket and limited to case reviews in the QA module. This is not the ideal situation when working a ticket live.

投稿日時:2025年2月07日 · Heather Rommel

11

フォロワー

3

投票

1

コメント


Heather Rommelさんがコメントを作成しました:

コメントWorking with conversations in Zendesk QA

What is the purpose of hashtags other than seeing how often they are used?

コメントを表示 · 投稿日時:2025年2月06日 · Heather Rommel

0

フォロワー

0

投票

0

コメント


Heather Rommelさんがコメントを作成しました:

コメントThird party and social messaging channels

Note, Step 5 no longer shows when setting this up. Where do we go to update these settings? 

コメントを表示 · 投稿日時:2025年1月25日 · Heather Rommel

0

フォロワー

0

投票

0

コメント


Heather Rommelさんがコメントを作成しました:

コメントReceiving and giving feedback with Zendesk QA

Hi Zendesk team,

We just purchased this awesome add-on but our teammembers are getting emails titled “Time for some conversation reviews” and we're not even set up yet. The link brings them to the old Klaus App login, not the Zendesk QA module.

 

  • As an admin, I'd like to be able to turn off these weekly reminders (and any other notifications) until we are ready. 
  • As an admin, I'd like to manage Zendesk QA access in users' roles

 

Any ideas?

Thank you!

コメントを表示 · 投稿日時:2025年1月06日 · Heather Rommel

0

フォロワー

0

投票

0

コメント


Heather Rommelさんが投稿を作成しました:

投稿 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)

Since the last update of Zendesk Agent UI where we have new background color for comments (blue for customers and grey for us), we've received feedback from our agent base that they would like to customize the colors in comment boxes, sidebar, etc.  Right now, only admins can control a limited portion of the colors such as the sidebar.

 

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

Each agent has personal opinions about color, so it would be perfect to be able to customize some colors.

 

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)

This is an annoyance for the team every day

 

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

No workaround atm

 

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

I would like to see an option to allow Agents to customize the UI colors at an element level.

編集日時:2025年1月02日 · Heather Rommel

1

フォロワー

2

投票

1

コメント


Heather Rommelさんがコメントを作成しました:

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

AGREE!!!! My workaround is to zoom out… :(

コメントを表示 · 投稿日時:2024年12月17日 · Heather Rommel

0

フォロワー

0

投票

0

コメント


Heather Rommelさんがコメントを作成しました:

コミュニティのコメント Feedback - Ticketing system (Support)

Hi Scott Allison We'd love to hear from you on this when you get a moment :D 

コメントを表示 · 投稿日時:2024年10月22日 · Heather Rommel

0

フォロワー

0

投票

0

コメント


Heather Rommelさんがコメントを作成しました:

コミュニティのコメント Q&A - Tickets and email

I don't know for sure, but I suspect some sort of Trigger or webhook collision is going on. Can you please click “events” on the ticket and review what's firing on the ticket at the time of creation? That should get you in the right direction.

コメントを表示 · 投稿日時:2024年10月21日 · Heather Rommel

0

フォロワー

1

投票

0

コメント


Heather Rommelさんがコメントを作成しました:

コミュニティのコメント Feedback - Ticketing system (Support)

Hi team,

One thing that is missing from this AWESOME feature request list is the ability to determine what should happen if someone replies to a SC on a closed ticket. Currently when we new reply, say a month later, long after the ticket has been closed, a follow up ticket is created.

We do not think new tickets should be automatically created, as this can create clutter and we would like to (as admins) decide what happens next…

コメントを表示 · 投稿日時:2024年10月11日 · Heather Rommel

0

フォロワー

0

投票

0

コメント


Heather Rommelさんがコメントを作成しました:

コミュニティのコメント Feedback - Help Center (Guide)

Hi The Original DKNY ! We have interest in these features as well. Is there any progress on this as of late? Thanks in advance for your attention!

Here's our list of related requests:

--

Sometimes its useful to have an internal only text field available within articles where notes can be taken and no customer shall ever see it. Those internal notes might for example contain:

  1. A link to a Zendesk ticket whereas the investigation was done containing additional steps where the article was an outcome for
  2. A link to an Jira for tracking purpose of an BUG or Enhancement
  3. A link to an slack channel / thread
  4. A special instruction when sharing an article to a customer
  5. A note of why an Article is public / or internal for justification purpose

コメントを表示 · 投稿日時:2024年10月11日 · Heather Rommel

0

フォロワー

1

投票

0

コメント