최근 검색
최근 검색 없음

Johnny
가입한 날짜: 2023년 8월 09일
·
마지막 활동: 2024년 12월 23일
팔로잉
0
팔로워
0
총 활동 수
37
투표 수
7
플랜 수
14
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Johnny
Johnny님이 에 댓글을 입력함
Jennifer Rowe Can we hide or deactivate the default 'All customers' list instead of deleting it?
댓글 보기 · 2024년 12월 18일에 게시됨 · Johnny
0
팔로워
0
투표 수
0
댓글
Johnny님이 에 게시물을 만듦
Hello,
We're encountering an issue with the new request list page in Zendesk. On the old request list page, we could easily edit and rearrange columns, example: moving the ID column to the first position and the subject column to the second. However, we’re unable to do this with the new request list page.
Has anyone else experienced this issue? Is there a workaround or a different approach we should be using to edit columns on the new page?
Any insights or suggestions would be greatly appreciated!
Thanks in advance for your help.


2024년 8월 19일에 게시됨 · Johnny
0
팔로워
0
투표 수
0
댓글
Johnny님이 에 게시물을 만듦
How can I create a landing page with an FAQ section in accordion style, similar to the Zendesk article [https://support.zendesk.com/hc/en-us/community/posts/4408860552730-Tip-Collapsible-headers-in-articles-or-templates-accordions], where the accordion functionality typically works within Zendesk articles but not directly on the landing page? I'm exploring options to implement this accordion style within the Categories/Articles section to collapse and hide content on the landing page itself.
For example, selecting "FAQ" should collapse to display the articles within the same page itself, without opening in a new page. Would this require custom coding, or is there another approach to achieve this?

2024년 7월 03일에 게시됨 · Johnny
0
팔로워
0
투표 수
0
댓글
Johnny님이 에 댓글을 입력함
Hi Greg Katechis, can you help? Currently, tickets created via messaging lack an option to switch back to email. While I see Zendesk implementing this feature as a temporary workaround, is it feasible to automatically update all tickets logged via messaging to the email channel using the API?
댓글 보기 · 2024년 1월 18일에 게시됨 · Johnny
0
팔로워
0
투표 수
0
댓글
Johnny님이 에 댓글을 입력함
Hey Anton, thanks, I've already enabled auto-translation for all supported languages. When applying the following code in the IDE, it seamlessly translates both standard responses and bot workflows for all supported languages:
댓글 보기 · 2024년 1월 17일에 게시됨 · Johnny
0
팔로워
1
투표
0
댓글
Johnny님이 에 댓글을 입력함
Hey Anton,
Thank you for the quick response. Yes, the translation issue persists for both standard responses in the messaging channel and the bot built with the flow builder. It currently translates only the conversation header, the 'built with Zendesk' logo, and the watermark text in the message box.
I am implementing multiple locales, with each locale being set based on the user's preferred language in their profile settings on our website.
I'm also facing challenges with the browser translation, as it's not dynamic. Users need to manually switch between (for instance) German and English for it to function properly.
댓글 보기 · 2024년 1월 17일에 게시됨 · Johnny
0
팔로워
0
투표 수
0
댓글
Johnny님이 에 게시물을 만듦
When applied in the IDE snippet, setting the locale to German ('de') ensures proper translation of the bot workflow into German.
zE('messenger:set', 'locale', 'de');
However, when applying the following snippet in the IDE, it doesn't translate the bot workflow content, it only translates the conversation header and the "built with Zendesk" logo at the bottom of the widget.
var UserLocale = $("#" + hdnAppCuesUserLanguage).val(); UserLocale = 'de'; // Set the locale to German ('de') zE('messenger:set', 'locale', UserLocale);
or this into the snippet: var UserLocale = $("#" + hdnAppCuesUserLanguage).val() || 'de'; // Set the locale to the chosen language or default to German ('de') zE('messenger:set', 'locale', UserLocale);
I would like the bot workflow to automatically translate based on the user's language preference on our website, not relying on the user's browser language. In some cases, users may have their browser language set to English, but their preferred language is different. How can I configure the bot workflow to adapt to the user's profile language rather than the browser-specific language?
I've already explored the articles in the help center before reaching out, so please avoid redirecting me to those resources. Unfortunately, I couldn't find a solution there, and it seems other users have encountered similar challenges.
Additionally, there are browser translation issues. Despite setting English as the default, when switching to German, the workflow translation is inconsistent, sometimes reverting to English.
Could someone provide assistance on this matter urgently? We need to expedite the resolution as the functionality is critical for us.
Much appreciated
2024년 1월 17일에 게시됨 · Johnny
0
팔로워
2
투표 수
4
댓글
Johnny님이 에 댓글을 입력함
Antonio Auctane +1 with your questions about multi-language support.
댓글 보기 · 2024년 1월 16일에 게시됨 · Johnny
0
팔로워
2
투표 수
0
댓글
Johnny님이 에 댓글을 입력함
+1
We need this feature, it would greatly benefit us in ensuring that agents can only access information within their assigned brand and not from any other brand, especially when managing multiple brands, some of which may involve confidential data including brand name. Can achieving this be possible through custom coding?
댓글 보기 · 2024년 1월 12일에 게시됨 · Johnny
0
팔로워
0
투표 수
0
댓글