Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

MineralTree | Support
Beigetreten 15. Apr. 2021
·
Letzte Aktivität 27. März 2024
Folge ich
0
Follower
2
Gesamtaktivitäten
58
Stimmen
5
Abonnements
25
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von MineralTree | Support
MineralTree | Support hat einen Post erstellt
I would like to be able to track the SLA history of a ticket. Something like:
Ticket 12345
First Reply Metric Entered, 03/26/2024 9:15 AM
First Reply Metrice Success (i.e. first reply was sent) 03/26/2024 10:00 AM
Customer Replied 03/26/2024 10:05 AM
Next Reply Metric Entered, 03/26/2024 10:05 AM
Next Reply Metric Failed, 03/28/2024 10:06 AM
Agent Replied 03/28/2024 11:30 AM..
Etc.
Anybody have any way to make this happens? The above format is not firm…I'm open to anything that makes it easy to see what happened.
Gepostet 27. März 2024 · MineralTree | Support
0
Follower
2
Stimmen
2
Kommentare
MineralTree | Support hat einen Kommentar hinterlassen
That nailed it. One of the problems I was having was that I TRIED Metric filter but I couldn't figure out how to get rid of the low value of '0'. I couldn't move the slider. This time I clicked on the 0 and it became an editable field.
Thank you!
Kommentar anzeigen · Gepostet 18. Dez. 2023 · MineralTree | Support
0
Follower
0
Stimmen
0
Kommentare
MineralTree | Support hat einen Post erstellt
I'm fairly certain that when this gets answered I'm going to say "of course, that was a dumb question" but here it is...
I've created a metric for tickets that have had >5 touches.
I've created a report with that as the chosen metric.
The filters are for a certain group and a certain date range.
If I put "Ticket ID" as one of the attributes, I get a list of ALL tickets that meet the filter criteria as well as a column for the metric with a "0" or "1" representing, as we know, whether or not that ticket met the criteria of the metric.
What I WANT to see is only tickets that are part of the metric, i.e. only those that the metric column shows a '1'.
Maybe it's because I'm doing this late on a Friday and my brain has stopped working but I just can't get the results I want.
Any help would be appreciated
Gepostet 15. Dez. 2023 · MineralTree | Support
1
Follower
2
Stimmen
2
Kommentare
MineralTree | Support hat einen Kommentar hinterlassen
Shawna,
I appreciate you chiming in here. As big of a problem it is that this functionality is not in the product nor has been delivered in the timeframes laid out, the bigger problem for many of us is the complete lack of response to our requests for updates.
If you read through the comments you'll see that time and again this community is ignored when asking a very valid question: could someone tell us what's going on?
I don't know if it is because nobody on the Zendesk Product team wants to take ownership, or if it's just a difficult question to answer, knowing that the community is upset but regardless of the reasoning the ending result is that you are perceived to be uncaring and apathetic to your customer base.
I'm sure that this has already cost Zendesk $$$ when it comes to renewals and it will cost them more as long as your company continues to ignore your customers.
Kommentar anzeigen · Gepostet 06. Dez. 2023 · MineralTree | Support
0
Follower
3
Stimmen
0
Kommentare
MineralTree | Support hat einen Kommentar hinterlassen
We use 2 ticket custom fields that are also required for resolution. They are both drop down types. One field is "classification" where the agent must select a classification, for instance "Login::Unable to log in".
This list is old with many outdated choices. We are going through a process to evaluate each 'resolution' and decide if it is still fitting. The end result of this project will be that we will delete many resolutions an add more.
What sort of effect will this have on our data? What about our reporting? If I remove a resolution will I still be able to report, filter or sort on it in Explore? What sorts of things should we be aware and wary of?
Kommentar anzeigen · Gepostet 10. Okt. 2023 · MineralTree | Support
0
Follower
0
Stimmen
0
Kommentare
MineralTree | Support hat einen Kommentar hinterlassen
What I need to do is combine two 'channels' into one. We consider "Web" and "Email" as the same channel. Right now my reporting looks like this...
I want to add Web+Email so I show them as one of 3 channels along with Voice and Chat.
Can someone point me in the right direction?
Kommentar anzeigen · Gepostet 27. Sept. 2023 · MineralTree | Support
0
Follower
0
Stimmen
0
Kommentare
MineralTree | Support hat einen Post erstellt
We have a need that I can't imagine is unique to us: We need our agents to be able to quickly identify that an incoming ticket is from a VIP customer. Tagging the VIP orgnizations is an easy thing to do but we need that to be in "flashing letters and sirens" (exaggeration intended) for our agents to see on the ticket. I can imagine this happening in a number of the ways I'll list below but I'm open to whatever might be available:
* A dialog box opening up when a ticket from a VIP is opened.
* A change in the organization name field at the top of the ticket (a colored icon gets added?)
* A change in the subject line that is obvious.
We just need something to be obvious so our agents are aware that they are talking to a high(er) value customer.
Is there anything out there? Is there a way to do it in the Support app that I'm missing? Is there something in the marketplace. I searched and didn't find anything seemingly useful but maybe I'm missing something. Has anybody else been faced with this challenge and found a resolution?
Gepostet 11. Sept. 2023 · MineralTree | Support
1
Follower
11
Stimmen
8
Kommentare
MineralTree | Support hat einen Kommentar hinterlassen
thanks for the response. I'll take a look at this.
Kommentar anzeigen · Gepostet 23. Juni 2023 · MineralTree | Support
0
Follower
0
Stimmen
0
Kommentare
MineralTree | Support hat einen Post erstellt
It's been a while since I've written a Standard Calculated Attribute and I'm failing miserably. I need to combine the "Email" and "Web" values of the Ticket Channel attribute. Any guidance would be appreciated.
Gepostet 08. Juni 2023 · MineralTree | Support
0
Follower
3
Stimmen
2
Kommentare
MineralTree | Support hat einen Kommentar hinterlassen
Hey, that was it. Actually, once I changed the "metrics" to tickets updated" and the filter to "update - timestamp" it all fell into place.
A big THANK YOU for this.
Kommentar anzeigen · Gepostet 21. Apr. 2023 · MineralTree | Support
0
Follower
1
Stimme
0
Kommentare