Vor Kurzem aufgerufene Suchen


Keine vor kurzem aufgerufene Suchen

Colin Hutzan's Avatar

Colin Hutzan

Beigetreten 23. Apr. 2023

·

Letzte Aktivität 03. Sept. 2024

Folge ich

0

Follower

0

Gesamtaktivitäten

38

Stimme

1

Abonnements

15

AKTIVITÄTSÜBERSICHT

Neueste Aktivität von Colin Hutzan

Colin Hutzan hat einen Kommentar hinterlassen

KommentarTicket editor, assignee, and requestor

Walter, there is a way to generate an external link to a different ticket. I read about it some weeks ago and did it successfully. I am having trouble finding it again now.

Kommentar anzeigen · Gepostet 03. Sept. 2024 · Colin Hutzan

0

Follower

0

Stimmen

0

Kommentare


Colin Hutzan hat einen Kommentar hinterlassen

KommentarTicket editor, assignee, and requestor

I am missing something very clear, I am sure

 

But I don't know how to link a DIFFERENT ticket for a customer using a placeholder. For example if I am communicating with a customer in one ticket and want to present them a link to a different one, what exactly do I need to type to do that?

Kommentar anzeigen · Gepostet 30. Aug. 2024 · Colin Hutzan

0

Follower

0

Stimmen

0

Kommentare


Colin Hutzan hat einen Kommentar hinterlassen

Community-Kommentar Feedback - Ticketing system (Support)

Shawna James I finally got around to using the template. I updated my note. Thanks for the suggestion!

Kommentar anzeigen · Gepostet 27. Jan. 2024 · Colin Hutzan

0

Follower

0

Stimmen

0

Kommentare


Colin Hutzan hat einen Kommentar hinterlassen

KommentarSalesforce integration

Hey Dwight Bussman, thank you.

Our integration is set up to match organization name with account record name.

Since that is a mapped field, I just went and edited the SalesForce organization name, then changed it back (so it matches the ZenDesk organization name again, the one that I had changed earlier).

We have no sync filtering.

This situation is where there was never a successful sync with this account because the account name was slightly different from the organization name in ZenDesk. I've now trued that up by changing the ZenDesk organization name to match the account name in SalesForce. We cannot edit SalesForce account names as they are integrated to other systems already.

How do I now make sure the account match happens and tickets populate properly?

We can certainly have a call! We have another item to follow up on anyway :)

Book time with Colin Hutzan  

Kommentar anzeigen · Gepostet 25. Jan. 2024 · Colin Hutzan

0

Follower

0

Stimmen

0

Kommentare


Colin Hutzan hat einen Kommentar hinterlassen

KommentarSalesforce integration

Oh hey Dwight Bussman!!

Your comment above actually answers my question partially. So my question as to how to force a sync remains. You mentioned that an account record being updated in SF will push a sync to ZenDesk. So, for example, could I just update some field in an account record in salesforce, change it back, and then a sync will happen? What do I need to do to force an account match with the integration after updating the name of an organization in ZD - so that a match happens and corresponding tickets show up via the integration in SF?

Kommentar anzeigen · Gepostet 25. Jan. 2024 · Colin Hutzan

0

Follower

0

Stimmen

0

Kommentare


Colin Hutzan hat einen Kommentar hinterlassen

KommentarSalesforce integration

Hello! 

We have the integration set up to sync SalesForce accounts to ZenDesk organizations based on the name.

I noticed in testing things out that the name for one customer was a bit different in SalesForce than ZenDesk, so I changed the ZenDesk name because SalesForce account names are already integrated to a different application for contracting and cannot be changed.

My question is - will a sync occur again automatically to find a match between the names? If so, how often does that happen? If not, how can I force one to happen?

We might find naming inconsistencies here and there and based on what I read above, the sync is one way so a change in ZenDesk will not update SalesForce. However, I also ready that the sync looks for matches - it seemed like, though not explicitly stated - that happens periodically.

Please help!

Kommentar anzeigen · Gepostet 25. Jan. 2024 · Colin Hutzan

0

Follower

0

Stimmen

0

Kommentare


Colin Hutzan hat einen Post erstellt

Post Feedback - Ticketing system (Support)

TITLE: Suspended ticket notification

I would like for ZenDesk to have the option for submitters of new tickets, or responses to existing tickets, where their communication ends up being suspended, to receive a notification of the suspension. Currently we have a high suspension rate as many submissions are being flagged as automated email responses when they are happening externally outside of the portal. Unless we have someone manually watching the suspended queue regularly, we fail to see these suspensions and submitters are under the impression that we are ignoring them.

What problem do you see this solving? (1-2 sentences) 

Overhead needed to monitor suspended tickets view: submitters could be automatically notified that they need to resubmit their communication through the portal (the notification option should allow for customized messaging). 

Lack of end user portal usage/lack of end users committing to best practices: End users, through the notifications, will be persuaded to use the ticketing portal for submitting and responding to tickets, rather than their email inbox. Email ticket submissions and responses are what lead to increased suspensions.

When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)

We regularly have suspended communications from end users, up to 50 in a week. Often from the same submitter who, though each communication in the suspended queue, can be observed as getting increasingly frustrated that they are failing to get an answer.

Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)

We sometimes monitor the suspended view, but we are a hyper growth startup and usually need to dedicate team capacity to other items. We try to encourage, through CSM interaction, our customers to use the ticketing portal instead of email, but it's difficult to do this especially for new customers who are already too mentally inundated with learning the software we just launched for them to be also learning the ticketing portal/system effectively.

What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)

I saw this as an option in the admin area under triggers and automations. The issue obviously is that a suspended ticket is not necessarily a ticket, so there's nothing to trigger off of. But, if there was a way to build a trigger off of 'new suspended communication' to send an email to the submitter email address, where we can customize the text of the email - that would be ideal. It would be good if it could come with filtering on email domain (eg. don't trigger if the domain is hausofphishing.com)

 
 

 

Bearbeitet 27. Jan. 2024 · Colin Hutzan

1

Follower

3

Stimmen

2

Kommentare


Colin Hutzan hat einen Kommentar hinterlassen

KommentarSalesforce integration

Trying this in sandbox and every new ticket created is creating a new organization in zendesk despite the org already existing (name match on the account name in SF). Please assist.

Kommentar anzeigen · Gepostet 18. Dez. 2023 · Colin Hutzan

0

Follower

0

Stimmen

0

Kommentare


Colin Hutzan hat einen Kommentar hinterlassen

Community-Kommentar Feedback - Ticketing system (Support)

+1.

I just added a note for requesters to subscribe to our status page to all agent signatures and without italicization, it looks bizarre 

Kommentar anzeigen · Gepostet 19. Okt. 2023 · Colin Hutzan

0

Follower

0

Stimmen

0

Kommentare


Colin Hutzan hat einen Kommentar hinterlassen

KommentarExplore recipes

Thanks James Skene - I thought that could be it but my metric on orgs matches the spelling in my account. ZenDesk escalated a ticket for me on this because they're having trouble figuring it out, even after assuming my account to investigate.

Kommentar anzeigen · Gepostet 19. Okt. 2023 · Colin Hutzan

0

Follower

0

Stimmen

0

Kommentare