Pesquisas recentes


Sem pesquisas recentes

Almog Zamir's Avatar

Almog Zamir

Entrou em 25 de jan. de 2023

·

Última atividade em 20 de fev. de 2025

Seguindo

0

Seguidores

0

Atividade total

122

Votos

72

Assinaturas

28

VISÃO GERAL DA ATIVIDADE

Atividade mais recente por Almog Zamir

Almog Zamir comentou,

ComentárioTicket customization

Hi

We are also looking forward to getting this Organization card. 
I read here a comment you said it will be available in early 2024 - we are now at early 2025! What can we expect for?

Exibir comentário · Publicado 20 de fev. de 2025 · Almog Zamir

0

Seguidores

0

Votos

0

Comentários


Almog Zamir comentou,

ComentárioTicket basics

Hey there
Is there a way to add links or embedded sections to the Agent Home page?

Exibir comentário · Publicado 26 de set. de 2024 · Almog Zamir

0

Seguidores

0

Votos

0

Comentários


Almog Zamir comentou,

Comentário na comunidade Feedback - Ticketing system (Support)

Hey, ZD team, it's been more than two years since your last “official” announcement about this feature.
Can you share when it will be released (as part of your roadmap)? 

Exibir comentário · Publicado 29 de ago. de 2024 · Almog Zamir

0

Seguidores

0

Votos

0

Comentários


Almog Zamir comentou,

ComentárioHow to solve unexpected issues with reports

Are you planning any potential solution for this issue?

Is someone in the community developed/found a solution/workaround to this?

Exibir comentário · Publicado 02 de jul. de 2024 · Almog Zamir

0

Seguidores

0

Votos

0

Comentários


Almog Zamir comentou,

ComentárioExplore recipes

Hey Tony, thank you for your reply!
On Explore, there are already at least two metrics that have been calculated within business hours (based on Schedules):
1) "First reply time—Business hours (mins or hrs)"  
2)"Full resolution time—Business hours (min or hrs)"
Therefore, the mechanism already exists in ZD's backend. 

Is there an option for you to provide the logic/mechanism of those metrics calculations so we could use it for every two timestamp fields, which would give us the flexibility to use it for any use case we wish?

Exibir comentário · Publicado 29 de mai. de 2024 · Almog Zamir

0

Seguidores

2

Votos

0

Comentários


Almog Zamir comentou,

ComentárioExplore recipes

Hey Dainne Kiara Lucena-Laxamana 
We set multiple Schedules, which means we have several business hours (several time zones) based on the Customer's region. How does this recipe support our need to calculate metrics within different business hours (regions' business hours)?

Exibir comentário · Publicado 28 de mai. de 2024 · Almog Zamir

0

Seguidores

0

Votos

0

Comentários


Almog Zamir comentou,

ComentárioExplore recipes

Hey there!
We have multiple Schedules, which means we have different business hours (several time zones). How does this recipe support our need to calculate metrics only within business hours?

Exibir comentário · Publicado 28 de mai. de 2024 · Almog Zamir

0

Seguidores

0

Votos

0

Comentários


Almog Zamir comentou,

ComentárioExplore recipes

How does it work for calculations within business hours?
 

Exibir comentário · Publicado 26 de mai. de 2024 · Almog Zamir

0

Seguidores

0

Votos

0

Comentários


Almog Zamir comentou,

ComentárioGlobal security and user access

Please correct me if I am wrong, but can I delete a ticket that is not archived as part of this feature?
I mean, let's say I want to set a schedule that deletes tickets after 30 days. I can't do it because schedule deletion only affects archived tickets, which means at least 120 days after the ticket was solved.

Exibir comentário · Publicado 20 de mai. de 2024 · Almog Zamir

0

Seguidores

0

Votos

0

Comentários


Almog Zamir comentou,

Comentário na comunidade Feedback - Ticketing system (Support)

A must!

Exibir comentário · Publicado 11 de dez. de 2023 · Almog Zamir

0

Seguidores

0

Votos

0

Comentários