Recent searches
No recent searches

DMKT
Joined Nov 10, 2022
·
Last activity Mar 29, 2024
Following
0
Followers
0
Total activity
42
Votes
13
Subscriptions
24
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by DMKT
DMKT commented,
Adding my comment to further increase the visibility of this much-needed feature update. Please include agent survey feedback as I'm sure there are more users out there that would love to see this gets implemented.
View comment · Posted Mar 04, 2024 · DMKT
0
Followers
1
Vote
0
Comments
DMKT commented,
Would love to see more than 10 personal views available... Our users (and I imagine other Zendesk users too) that require this function usually manages a bit more than that. Maybe if we can have 40 views maximum displayed like Zendesk has currently planned, but instead of a fixed amount for each views we let the users decide how many shared views and how many personal views they want to display as long as they don't go beyond 40? That way we have more flexibility on deciding which views to utilize for different team needs.
View comment · Posted Aug 09, 2023 · DMKT
0
Followers
1
Vote
0
Comments
DMKT commented,
Is it possible to include a customized "pre-preform" for this link to fire up when clicked? For a bit of context, we need to show customers who clicked on this link a preform within the widget to acknowledge using our services. We have this function on our websites if they contact us from there, but I'm not sure if there's a link that can do the same. (we still use phase1 chat links however we are using the latest chat accounts)
View comment · Posted Dec 09, 2022 · DMKT
0
Followers
0
Votes
0
Comments
DMKT created a post,
I absolutely understand this is common practice for all customer support SaaS systems, however it would still benefit our users if this feature could be implemented. Having multiple main receivers being addressed directly and equal ownership to the same ticket is very helpful. I suppose if the feature could be toggled on/off like CC it shouldn't impact others that don't need the complication.
Just wondering if this is more of a system limitation concern? (Need to update tickets for everyone whenever any requester respond to the ticket, creating issues for Guide datasets etc.)
Posted Nov 29, 2022 · DMKT
0
Followers
3
Votes
2
Comments
DMKT commented,
More granular control over which fields are hidden for which agent groups would be quite helpful as we have a lot of different teams using different "internal fields" and hiding them separately will prevent errors being made editing fields.
View comment · Posted Nov 18, 2022 · DMKT
0
Followers
0
Votes
0
Comments