Pesquisas recentes
Sem pesquisas recentes

karankuwarbidxb
Entrou em 23 de jun. de 2023
·
Última atividade em 27 de jan. de 2025
Seguindo
0
Seguidores
0
Atividade total
71
Votos
0
Assinaturas
29
VISÃO GERAL DA ATIVIDADE
MEDALHAS
ARTIGOS
PUBLICAÇÕES
COMENTÁRIOS NA COMUNIDADE
COMENTÁRIOS EM ARTIGOS
VISÃO GERAL DA ATIVIDADE
Atividade mais recente por karankuwarbidxb
karankuwarbidxb criou uma publicação,
Problem statement:
In create many api, we do not get individual tracking-id for each ticket object, Instead in response we get an array of objects and one tracking id for all ticket objects, so it is difficult for us to create a mapping.
Expected output-
in request body we can share a uuid for each object with which they can map the response and with GET api provide the same to us. in response of create many provide us a uuid and when we hit API for response of create many provide same id with status
Publicado 27 de jan. de 2025 · karankuwarbidxb
0
Seguidores
2
Votos
1
Comentário
karankuwarbidxb criou uma publicação,
In our organization, sometimes the CC'ed users (mostlly our internal team members who are not on zendesk) try to create a private email conversation without the customers. And if a manager with Zendesk license replies to that email, all the conversation is sent to zendesk on that thread.
Now I understand that this is because one of the Zendesk support address is added to the email conversation but is it possible to prevent a public comment notification to go out to the customer if the update channel is outside of Zendesk? I don't see any such distinction in the triggers yet.
I understand that We have Mail APIs but I cannot expect all our team members around the world to remember them to send email.
Editado 13 de nov. de 2024 · karankuwarbidxb
0
Seguidores
1
Votos
0
Comentários
karankuwarbidxb criou uma publicação,
Simply, I'd need a row level data with the following headers:

Publicado 04 de nov. de 2024 · karankuwarbidxb
1
Seguidor
2
Votos
1
Comentário
karankuwarbidxb comentou,
Hi Agnieszka Pyzik you mentioned that “On October 9th and 10th, we will release the feature to pods 17, 23, 27, and 28.”
I'm on POD 17 and haven't received this update yet.
Exibir comentário · Publicado 10 de out. de 2024 · karankuwarbidxb
0
Seguidores
0
Votos
0
Comentários
karankuwarbidxb comentou,
At present this is what the side conversation panel says:
And the team is unable to reopen a closed conversation.

Exibir comentário · Publicado 02 de jul. de 2024 · karankuwarbidxb
0
Seguidores
2
Votos
0
Comentários
karankuwarbidxb criou uma publicação,
Hi Team,
I noticed today that the side conversation view has been completely moved to Context panel. The team is kind of used to seeing the Side conversation button next to the ticket number on all the tickets and they are finding this extremely confusing, especially without any announcement from Zendesk on this matter.
Is it possible to revert this change and move side conversation to it's old place (Next to the ticket number)?
Thanks!
Publicado 02 de jul. de 2024 · karankuwarbidxb
1
Seguidor
2
Votos
1
Comentário
karankuwarbidxb criou uma publicação,
Hi, I have created two calculated attributes in the "Support: Update history" dataset. The results are coming out just fine, the only issue is that the output is coming up in separate rows. I really want to create a report where every ticket accounts to only one row and all the default attributes plus the calculated attributes are shown in just one row.
Expected output:
Actual output:
Publicado 22 de mar. de 2024 · karankuwarbidxb
0
Seguidores
4
Votos
3
Comentários
karankuwarbidxb comentou,
Hi Team,
Can I have a custom status disabled on the front end (Agent interface) but available to our system on the backend for automation?
For eg: I want to have a custom status 'Auto closed' that I want to use when I solve tickets through trigger. But I don't want this status to be available to agents using Zendesk as they will incorrectly use this status.
Exibir comentário · Publicado 15 de fev. de 2024 · karankuwarbidxb
0
Seguidores
1
Votos
0
Comentários
karankuwarbidxb comentou,
Presently, if I have an agent with skill 'Poland' he is being assigned tickets with this skill plus if there are tickets with no skill.
I want them to only attend to tickets matching there skill even if there's no other person for rest of the tickets.
Exibir comentário · Publicado 06 de dez. de 2023 · karankuwarbidxb
0
Seguidores
0
Votos
0
Comentários
karankuwarbidxb comentou,
Hi Barry Neary,
I created a skill called Poland based on some customers from that region. And I assigned this skill to an agent and turned the omnichannel routing on
This agent has a capacity of 20 tickets but at some days the flow is less. It seems like they are also getting tickets which has a 'null' skill. Is there any way to limit routing of cases with the matching skill ONLY. And not the null ones.
Exibir comentário · Publicado 06 de dez. de 2023 · karankuwarbidxb
0
Seguidores
0
Votos
0
Comentários