最近の検索


最近の検索はありません

Shweta Gupta's Avatar

Shweta Gupta

参加日2021年5月16日

·

前回のアクティビティ2021年10月27日

フォロー中

0

フォロワー

0

合計アクティビティ

18

投票

2

受信登録

8

アクティビティの概要

さんの最近のアクティビティ Shweta Gupta

Shweta Guptaさんがコメントを作成しました:

コメントGeneral questions and issues about tickets

Hi Leah,

Any updates on having a built-in capability within Zendesk for auto assignment?

コメントを表示 · 投稿日時:2021年6月22日 · Shweta Gupta

0

フォロワー

1

投票

0

コメント


Shweta Guptaさんがコメントを作成しました:

コメントService Level Agreements (SLA), macros, and CSAT

Hi Tiann,

This is helpful.

I have a follow-up question - Based on the above, how can I keep on assigning tickets to agents (round robin or any fashion). I tried the Round Robin app on marketplace and Play Mode on Zendesk and they are not really helpful and my usecase is not solved with them.

Thanks.

Regards,

Shweta

コメントを表示 · 投稿日時:2021年6月22日 · Shweta Gupta

0

フォロワー

0

投票

0

コメント


Shweta Guptaさんがコメントを作成しました:

コミュニティのコメント Q&A - Tickets and email

Hi,

I have a similar query. Incoming tickets have agent names, especially loyal customers who reach out to support directly addressing the agents they last worked with. I understand how to set this via triggers, but this results in false positive if the name of the customer is same as that of any agent.

I want to set a trigger or condition or using any other Zendesk capability, that can help me parse only the initial few lines in the email body (I wish to exclude the signature and have only salutations). Is there a way to do this?

コメントを表示 · 投稿日時:2021年6月10日 · Shweta Gupta

0

フォロワー

0

投票

0

コメント


Shweta Guptaさんがコメントを作成しました:

コメントBusiness rules

Hi,

Is there a way to set a trigger based on who the ticket was addressed to?

Context: Customers often tend to address the tickets to agents with whom they have had a good experience. This need not be the last agent they interacted with. So if a customer reaches out to me:

Hi Shweta 

< Ticket content>

Is there a way to automatically triage this based on the agent name it's been addressed to?

Thanks.

コメントを表示 · 投稿日時:2021年5月27日 · Shweta Gupta

0

フォロワー

0

投票

0

コメント


Shweta Guptaさんがコメントを作成しました:

コメントTicket automation and collaboration

Hi Brett,

 

Thank you for the prompt response. This helps. Just confirming that the customer will have an updated subject within the same email thread, right?

Also, if this is the case, what are the possible usecases for Set Subject then?

Thanks :)

コメントを表示 · 投稿日時:2021年5月14日 · Shweta Gupta

0

フォロワー

0

投票

0

コメント


Shweta Guptaさんがコメントを作成しました:

コメントTicket automation and collaboration

Hi,

Does using "Set Subject" creates a new ticket or just changes the subject of the entire ticket for the agent. Also can you let me know what would be the end customer experience on this one?

コメントを表示 · 投稿日時:2021年5月14日 · Shweta Gupta

0

フォロワー

0

投票

0

コメント


Shweta Guptaさんがコメントを作成しました:

コメントAdditional ticket channels

Hi Lisa,

Is all of the above mentioned functionality released now or there is something missing?

コメントを表示 · 投稿日時:2021年5月12日 · Shweta Gupta

0

フォロワー

0

投票

0

コメント


Shweta Guptaさんがコメントを作成しました:

コメントTicket automation and collaboration

Hi, 

I have been facing issues with Side conversations.

The behaviour is very erratic. A lot of times, these side conversations are not delivered. I have checked all the settings and confirmed with the team about any allowlist/blocklist or rules set that might cause this. But there isn't any.

Side conversations to other teams are not delivered which is why the team has to reach out to them using emails and other channels. I am sure you understand that this dilutes the very purpose of Side Conversations.

Can you help me understand:

  • If this is expected behaviour? If yes, can you share an ETA by when it will be resolved
  • If no, If there is anything else that needs to be checked in order to get this working?
  • If there is anything in your product pipeline that confirms a Delivered or a Read status on the sent Side conversations?

Thanks.

 

 

コメントを表示 · 投稿日時:2021年5月12日 · Shweta Gupta

0

フォロワー

0

投票

0

コメント