최근 검색

최근 검색 없음

Naghash Baghdasaryan's Avatar

Naghash Baghdasaryan

가입한 날짜: 2021년 10월 16일

·

마지막 활동: 2023년 11월 14일

팔로잉

0

팔로워

0

총 활동 수

27

투표 수

7

플랜 수

12

활동 개요

님의 최근 활동 Naghash Baghdasaryan

Naghash Baghdasaryan님이 에 게시물을 만듦

게시물 Feedback - Chat and Messaging (Chat)
Agent's profile pictures are not seen in the emails because of the new simplified email threading.

Agent's profile picture is not displayed in the emails because of the new simplified email threading.
This is a real limitation to interact effectively with the end users.
Please, provide a workaround to fix this issue.

2023년 10월 19일에 편집됨 · Naghash Baghdasaryan

2

팔로워

3

투표 수

2

댓글

Naghash Baghdasaryan님이 에 댓글을 입력함

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

Hi Sean,
Is there any change/update on this topic?
We are still using a paid admin seat for the Jira integration. 

댓글 보기 · 2023년 10월 12일에 게시됨 · Naghash Baghdasaryan

0

팔로워

1

투표

0

댓글

Naghash Baghdasaryan님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Chat and Messaging (Chat)
커뮤니티

Hi Lisa Tam,
It would be great to be able to use regex field types in the Bot flow.
One very useful use case is checking the GPA format provided by the end user.

댓글 보기 · 2023년 7월 20일에 게시됨 · Naghash Baghdasaryan

0

팔로워

1

투표

0

댓글

Naghash Baghdasaryan님이 에 게시물을 만듦

게시물 Feedback - Apps and integrations (Platform)
Limitation of 200 tickets linked to a Jira issue.

Currently, up to 200 tickets can be linked to a Jira issue. There is a limitation.
It would be great to be able to link over 200 tickets to a Jira issue.

2023년 3월 02일에 게시됨 · Naghash Baghdasaryan

2

팔로워

8

투표 수

5

댓글

Naghash Baghdasaryan님이 에 게시물을 만듦

게시물 Feedback - Apps and integrations (Platform)
Zendesk Ticket Count limit in Jira

The Zendesk Ticket Count limit in Jira.
The linked Tickets field shows 99+ in Jira, and with Zendesk Ticket Field not updating it makes it almost impossible to check the actual number of tickets if there are over 99 linked tickets, which is currently done by manually counting the linked tickets number. Is there a way to upgrade this feature and instead of showing 99+ show the exact number of the linked tickets?

2023년 1월 30일에 게시됨 · Naghash Baghdasaryan

0

팔로워

2

투표 수

1

댓글

Naghash Baghdasaryan님이 에 게시물을 만듦

게시물 Feedback - Apps and integrations (Platform)
Zendesk is sparing a paid seat for Jira integration

It is not a good solution by Zendesk to spare a paid seat for Jira integration.
There is an option to disable creating the integration without the Jira user, but then, the updates will be shown by the user who set up the integration. 
Hope the product team finds an effective solution for this issue.

2022년 3월 21일에 게시됨 · Naghash Baghdasaryan

1

팔로워

4

투표 수

3

댓글

Naghash Baghdasaryan님이 에 게시물을 만듦

게시물 Feedback - Developer Platform
Multibranding email template for 7 languages

Since the Dynamic Content is not enabled for email templates, you can use this code for multibranding and multilanguage email templates in 7 languages:
(change the BrandName1 and BrandName2 to your brand names)





 Zendesk Email Template





{{delimiter}}

{% case footer %}



{% when 'This email is a service from BrandName1.' %}

custom code




{% when 'Это служебное письмо от BrandName1.' %}

custom code




{% when 'Este email é um serviço de BrandName1.' %}

custom code




{% when 'هذا البريد الإكتروني خدمة من Brandname1.' %}

custom code




{% when '本メールはBrandname1から送信されています。' %}

custom code




{% when 'Este correo electrónico es un servicio de BrandName1.' %}

custom code




{% when '此电邮是由 BrandName1 提供的服务。' %}

custom code




{% when '本電子郵件是 Picsart 提供的服務。' %}

custom code




{% when 'This email is a service from BrandName2.' %}

custom code




{% when 'Это служебное письмо от BrandName2.' %}

custom code




{% when 'Este email é um serviço de BrandName2.' %}

custom code




{% when 'هذا البريد الإكتروني خدمة من Brandname2.' %}

custom code




{% when '本メールはBrandname2から送信されています。' %}

custom code




{% when 'Este correo electrónico es un servicio de BrandName2.' %}

custom code




{% when '此电邮是由 BrandName2 提供的服务。' %}

custom code




{% when '本電子郵件是 Brandname2 提供的服務。' %}

custom code


{% else %}



custom code for ELSE option







{% endcase %}





{{content}}







{% case footer %}



{% when 'This email is a service from BrandName1.' %}

custom code




{% when 'Это служебное письмо от BrandName1.' %}

custom code




{% when 'Este email é um serviço de BrandName1.' %}

custom code




{% when 'هذا البريد الإكتروني خدمة من Brandname1.' %}

custom code




{% when '本メールはBrandname1から送信されています。' %}

custom code




{% when 'Este correo electrónico es un servicio de BrandName1.' %}

custom code




{% when '此电邮是由 BrandName1 提供的服务。' %}

custom code




{% when '本電子郵件是 Picsart 提供的服務。' %}

custom code


{% when 'This email is a service from BrandName2.' %}


custom code




{% when 'Это служебное письмо от BrandName2.' %}


custom code




{% when 'Este email é um serviço de BrandName2.' %}


custom code




{% when 'هذا البريد الإكتروني خدمة من Brandname2.' %}


custom code




{% when '本メールはBrandname2から送信されています。' %}


custom code




{% when 'Este correo electrónico es un servicio de BrandName2.' %}


custom code




{% when '此电邮是由 BrandName2 提供的服务。' %}


custom code




{% when '本電子郵件是 Brandname2 提供的服務。' %}


custom code


{% else %}


custom code for ELSE option


 






{% endcase %}


2021년 12월 24일에 게시됨 · Naghash Baghdasaryan
0
팔로워
2
투표 수
0
댓글
Naghash Baghdasaryan님이 에 댓글을 입력함
커뮤니티 댓글  Feedback - Ticketing system (Support)
커뮤니티
I came across the same problem and the only solution for the multibranding and multilanguage email template I was able to build is the following for 7 languages:
(change the BrandName1 and BrandName2 to your brand names)


 








 Zendesk Email Template





{{delimiter}}

{% case footer %}



{% when 'This email is a service from BrandName1.' %}

custom code




{% when 'Это служебное письмо от BrandName1.' %}

custom code




{% when 'Este email é um serviço de BrandName1.' %}

custom code




{% when 'هذا البريد الإكتروني خدمة من Brandname1.' %}

custom code




{% when '本メールはBrandname1から送信されています。' %}

custom code




{% when 'Este correo electrónico es un servicio de BrandName1.' %}

custom code




{% when '此电邮是由 BrandName1 提供的服务。' %}

custom code




{% when '本電子郵件是 Picsart 提供的服務。' %}

custom code




{% when 'This email is a service from BrandName2.' %}

custom code




{% when 'Это служебное письмо от BrandName2.' %}

custom code




{% when 'Este email é um serviço de BrandName2.' %}

custom code




{% when 'هذا البريد الإكتروني خدمة من Brandname2.' %}

custom code




{% when '本メールはBrandname2から送信されています。' %}

custom code




{% when 'Este correo electrónico es un servicio de BrandName2.' %}

custom code




{% when '此电邮是由 BrandName2 提供的服务。' %}

custom code




{% when '本電子郵件是 Brandname2 提供的服務。' %}

custom code


{% else %}



custom code for ELSE option







{% endcase %}





{{content}}







{% case footer %}



{% when 'This email is a service from BrandName1.' %}

custom code




{% when 'Это служебное письмо от BrandName1.' %}

custom code




{% when 'Este email é um serviço de BrandName1.' %}

custom code




{% when 'هذا البريد الإكتروني خدمة من Brandname1.' %}

custom code




{% when '本メールはBrandname1から送信されています。' %}

custom code




{% when 'Este correo electrónico es un servicio de BrandName1.' %}

custom code




{% when '此电邮是由 BrandName1 提供的服务。' %}

custom code




{% when '本電子郵件是 Picsart 提供的服務。' %}

custom code




{% when 'This email is a service from BrandName2.' %}


custom code




{% when 'Это служебное письмо от BrandName2.' %}


custom code




{% when 'Este email é um serviço de BrandName2.' %}


custom code




{% when 'هذا البريد الإكتروني خدمة من Brandname2.' %}


custom code




{% when '本メールはBrandname2から送信されています。' %}


custom code




{% when 'Este correo electrónico es un servicio de BrandName2.' %}


custom code




{% when '此电邮是由 BrandName2 提供的服务。' %}


custom code




{% when '本電子郵件是 Brandname2 提供的服務。' %}


custom code


{% else %}


custom code for ELSE option


 






{% endcase %}


댓글 보기 · 2021년 12월 24일에 편집됨 · Naghash Baghdasaryan
0
팔로워
1
투표
0
댓글