최근 검색


최근 검색 없음

DMKT's Avatar

DMKT

가입한 날짜: 2022년 11월 10일

·

마지막 활동: 2024년 3월 29일

팔로잉

0

팔로워

0

총 활동 수

42

투표 수

13

플랜 수

24

활동 개요

님의 최근 활동 DMKT

DMKT님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Ticketing system (Support)

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.

댓글 보기 · 2024년 3월 04일에 게시됨 · DMKT

0

팔로워

1

투표

0

댓글


DMKT님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Ticketing system (Support)

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.

댓글 보기 · 2023년 8월 09일에 게시됨 · DMKT

0

팔로워

1

투표

0

댓글


DMKT님이 에 댓글을 입력함

댓글Help with Web Widget

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)

댓글 보기 · 2022년 12월 09일에 게시됨 · DMKT

0

팔로워

0

투표 수

0

댓글


DMKT님이 에 게시물을 만듦

게시물 Feedback - Ticketing system (Support)

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.)

2022년 11월 29일에 게시됨 · DMKT

0

팔로워

3

투표 수

2

댓글


DMKT님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Apps and integrations (Platform)

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.

댓글 보기 · 2022년 11월 18일에 게시됨 · DMKT

0

팔로워

0

투표 수

0

댓글