Recent searches
No recent searches

Naghash Baghdasaryan
Joined Oct 16, 2021
·
Last activity Nov 14, 2023
Following
0
Followers
0
Total activity
27
Votes
7
Subscriptions
12
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Naghash Baghdasaryan
Naghash Baghdasaryan created a post,
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.
Edited Oct 19, 2023 · Naghash Baghdasaryan
2
Followers
3
Votes
2
Comments
Naghash Baghdasaryan commented,
Hi Sean,
Is there any change/update on this topic?
We are still using a paid admin seat for the Jira integration.
View comment · Posted Oct 12, 2023 · Naghash Baghdasaryan
0
Followers
1
Vote
0
Comments
Naghash Baghdasaryan commented,
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.
View comment · Posted Jul 20, 2023 · Naghash Baghdasaryan
0
Followers
1
Vote
0
Comments
Naghash Baghdasaryan created a post,
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.
Posted Mar 02, 2023 · Naghash Baghdasaryan
2
Followers
8
Votes
5
Comments
Naghash Baghdasaryan created a post,
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?
Posted Jan 30, 2023 · Naghash Baghdasaryan
0
Followers
2
Votes
1
Comment
Naghash Baghdasaryan created a post,
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.
Posted Mar 21, 2022 · Naghash Baghdasaryan
1
Follower
4
Votes
3
Comments
Naghash Baghdasaryan created a post,
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 %}
Posted Dec 24, 2021 · Naghash Baghdasaryan
0
Followers
2
Votes
0
Comments
Naghash Baghdasaryan commented,
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 %}
View comment · Edited Dec 24, 2021 · Naghash Baghdasaryan
0
Followers
1
Vote
0
Comments