Vor Kurzem aufgerufene Suchen


Keine vor kurzem aufgerufene Suchen

Allen Lai | Head of CX at Otter.ai's Avatar

Allen Lai | Head of CX at Otter.ai

Beigetreten 15. Apr. 2021

·

Letzte Aktivität 10. Dez. 2024

Folge ich

0

Follower

3

Gesamtaktivitäten

150

Stimmen

25

Abonnements

54

AKTIVITÄTSÜBERSICHT

Neueste Aktivität von Allen Lai | Head of CX at Otter.ai

Allen Lai | Head of CX at Otter.ai hat einen Kommentar hinterlassen

Community-Kommentar Feedback - Ticketing system (Support)

Gareth Elsby Sure here's how I did it.

 

  1. Create a trigger in Zendesk with the following conditions:
    1. Meet ALL of the following conditions
      1. Ticket status Changed from Solved
      2. Ticket status Changed to Open
    2. Actions
      1. Add tags “reopen_solved”
  2. Create a custom view in Zendesk with the following conditions:
    1. Tickets must meet all of these conditions to appear in the view
      1. Ticket status contains at least one of the following: Open
      2. Hours since status category open (calendar) is 1
      3. Tags contains at least one of the following: reopen_solved
  3. In Zapier, do the following:
    1. Step 1: Zendesk
      1. Event: New Ticket in View
      2. View: Select the view created in the previous step
    2. Step 2: Delay by Zapier
      1. Add a one-minute delay to ensure the trigger in step 1 occurs first.
    3. Step 3: Filter by Zapier
      1. Only continue if:
        1. Status Contains open; AND
        2. Tags Contains reopen_solved
    4. Step 4: Zendesk
      1. Event: Find Latest Comment
    5. Step 5: Filter by Zapier
      1. Only continue if:
        1. From Step 4, “Plain Body” Contains “thank you”; AND
        2. From Step 4, “Via Source From Address” Exists; OR
        3. From Step 4, “Plain Body” Contains “thanks”; AND
        4. From Step 4, “Via Source From Address” Exists
    6. Step 6: OpenAI
      1. Event: Send Prompt
      2. Model: gpt-3.5-instruct
      3. Prompt: "Review the first 255 characters of the message below from a customer. If the message is purely an expression of thanks without any indication that a reply or follow-up is needed, respond with 'TRUE'. Otherwise, respond with 'FALSE'. Note that any mention of an issue or request for assistance should lead to a 'FALSE' response. Here is the customer's message:

        "4. Plain Body"
    7. Step 7: Filter by Zapier
      1. Only continue if:
        1. From Step 6, Response Contains “true”
    8. Step 8: Zendesk
      1. Event: Update Ticket
      2. New status: Solved
      3. New Comment to add to the Ticket: “Zapier automatically updated the ticket status from Open to Solved because the customer was simply thanking us and a reply or follow-up is not needed.”
      4. Should the new Comment be public? No

Kommentar anzeigen · Bearbeitet 10. Dez. 2024 · Allen Lai | Head of CX at Otter.ai

0

Follower

0

Stimmen

0

Kommentare


Allen Lai | Head of CX at Otter.ai hat einen Kommentar hinterlassen

KommentarTicket automation and collaboration

I would like to be able to create Views based on the high-level intent, such as Account, Billing, etc. Currently, I can only create Views based on a specific intent, which is very time-consuming.

Kommentar anzeigen · Gepostet 21. Nov. 2024 · Allen Lai | Head of CX at Otter.ai

0

Follower

0

Stimmen

0

Kommentare


Allen Lai | Head of CX at Otter.ai hat einen Kommentar hinterlassen

KommentarSelf-service best practices and recipes

We're thinking of implementing an internal KB, and my only concern is that agents accidentally link to an internal article within their public response. Will it allow agents to do that?

Kommentar anzeigen · Gepostet 23. Okt. 2024 · Allen Lai | Head of CX at Otter.ai

0

Follower

0

Stimmen

0

Kommentare


Allen Lai | Head of CX at Otter.ai hat einen Post erstellt

Post Q&A - Reporting and analytics

I'm looking to create a report showing the average number of agent comments required to resolve a ticket, but I'm having trouble finding an obvious way to do this. Has anyone else had success with this?

Gepostet 21. Aug. 2024 · Allen Lai | Head of CX at Otter.ai

0

Follower

0

Stimmen

0

Kommentare


Allen Lai | Head of CX at Otter.ai hat einen Post erstellt

Post Q&A - Reporting and analytics

I notice that when an agent puts themselves on “Unavailable” using the Out of Office app, it adds the tag “agent_ooo” to their tickets. When they return from vacation and set themselves back to “Available,” it removes the “agent_ooo” tag. When I look at a report that shows how many tickets they've updated, this skews their numbers.

 

I was hoping to create a standard calculated attribute that I could filter on, but I can't quite figure if it's possible. Something like the following is what I'm looking for:

 

IF ([Changes - Field name] = "tags" AND
CONTAINS [Changes - New value], "agent_ooo")
THEN "true"
ENDIF

 

Similarly, I'd need another to filter when the tag is removed.

Gepostet 08. Aug. 2024 · Allen Lai | Head of CX at Otter.ai

0

Follower

0

Stimmen

0

Kommentare


Allen Lai | Head of CX at Otter.ai hat einen Kommentar hinterlassen

KommentarTicket basics

When an email is forwarded to our support address, is there any attribute I can use within a trigger to tag these tickets? I want to differentiate these tickets by adding a tag or updating one of the ticket fields. Thanks!

Kommentar anzeigen · Gepostet 31. Mai 2024 · Allen Lai | Head of CX at Otter.ai

0

Follower

0

Stimmen

0

Kommentare


Allen Lai | Head of CX at Otter.ai hat einen Kommentar hinterlassen

Community-Kommentar Feedback - Ticketing system (Support)

I created an automation via Zapier using a prompt in OpenAI, which is working wonders for us. I would highly recommend it.

Kommentar anzeigen · Gepostet 04. Mai 2024 · Allen Lai | Head of CX at Otter.ai

0

Follower

1

Stimme

0

Kommentare


Allen Lai | Head of CX at Otter.ai hat einen Kommentar hinterlassen

KommentarBuilding reports

From my understanding, the Requester Wait Time is only calculated after a ticket is updated. So you don’t get an accurate way to gauge the average wait time of all New and Open tickets. I learned this the hard way when I manually exported our tickets and then calculated it myself, and found that the value for Requester Wait Time was severely understated. Seems like something that should be improved, otherwise, you’re reporting inaccurate information. 

Kommentar anzeigen · Gepostet 02. Mai 2024 · Allen Lai | Head of CX at Otter.ai

0

Follower

1

Stimme

0

Kommentare


Allen Lai | Head of CX at Otter.ai hat einen Kommentar hinterlassen

KommentarBuilding reports

I'm trying to calculate the Requester Wait Time to include the time it spends in New or Open status before an agent has replied. We sometimes have tickets in Open status if automation attempts to answer the customer's request but is unsuccessful.

Here's my attempt, but I wasn't sure if this was the right way to calculate it.

IF ([Ticket status]="New") OR (([Ticket status]="Open" AND [Assignee stations brackets]="NULL" AND VALUE(Agent replies)<1))
THEN DATE_DIFF(NOW(),[Ticket created - Timestamp],"nb_of_hours") 
ELSE VALUE(Requester wait time - Business hours (min))/60
ENDIF  

Kommentar anzeigen · Gepostet 24. Apr. 2024 · Allen Lai | Head of CX at Otter.ai

0

Follower

0

Stimmen

0

Kommentare


Allen Lai | Head of CX at Otter.ai hat einen Kommentar hinterlassen

KommentarBuilding reports

Amy Dee Do you know a way to calculate the 90th percentile of the Requester wait time?

Kommentar anzeigen · Gepostet 23. Apr. 2024 · Allen Lai | Head of CX at Otter.ai

0

Follower

0

Stimmen

0

Kommentare