Recent searches


No recent searches

Leanne Britton's Avatar

Leanne Britton

Joined Apr 14, 2021

·

Last activity Sep 25, 2023

Following

0

Followers

0

Total activity

11

Votes

0

Subscriptions

4

ACTIVITY OVERVIEW

Latest activity by Leanne Britton

Leanne Britton commented,

CommentHelp with apps and integrations

Hi Jean, glad to hear you found the above steps helpful! The push notifications still work even if the channel is set to private. As long as the private channel is specified in your Slack app (Step 1.3) and you copy the webhook URL (Step 1.4) and paste it into your Zendesk webhook endpoint (Step 2.2), you'll still be able to receive the notification in the private channel. 

View comment · Posted Feb 15, 2023 · Leanne Britton

0

Followers

1

Vote

0

Comments


Leanne Britton created an article,

ArticleHelp with apps and integrations

Setting up a workflow that sends notifications in Slack when a ticket is rated negatively allows proactive handling of concerns and improves customer satisfaction. Achieve this goal through a combination of a custom Slack app with an incoming webhook, Zendesk webhook, and trigger.

The workflow includes the following step:;

Step 1: Create an app in Slack and an incoming webhook

  1. Create a custom Slack app following the Slack API document: Your Apps
    In this example, the Slack app is named CSAT Notifier.
  2. In Slack, the settings enable Incoming Webhooks using the toggle under Features > Incoming Webhooks.
  3. At the bottom of the Incoming Webhooks page, select Add a New Webhook to Workspace. As you configure the webhook, choose what channel should receive the notifications from the drop-down option. In this example, a unique Slack channel #zendesk-bad-csat was created to receive the notifications.
  4. After creating the URL, the system brings you back to a list of URLs for your app. Copy the one you just created using the Copy button.

For more information on creating Slack webhooks, see the Slack documentation: Sending messages using Incoming Webhooks.

Step 2: Create a webhook in Zendesk to send CSAT tickets to your new Slack webhook

  1. In Zendesk, create a new webhook.
  2. Use the following configuration
      • Name | Send negative CSATs to Slack
      • Endpoint URL | [Paste the Slack incoming webhook URL copied from step 1.4]
      • Request method | POST
      • Request format | JSON
      • Authentication | None
    Note: No credentials are required. The URL itself includes the secret required to POST messages.

The webhook should appear similar to the below image.

Step 3: Create a trigger to send negative CSAT tickets to your Slack channel

Lastly, create a trigger to specify what tickets should be sent to your channel. For this example, notify any tickets that receive a Bad or Bad with Comment CSAT. Follow the steps below to create this workflow.

To create the trigger

  1. Create a new trigger
  2. Under Meet ALL of the following conditions, add:
    • Object > Ticket > Ticket | Is | Updated
  3. Under Meets ANY of the following conditions, add:
    • Object > Ticket > Satisfaction | Changed to | Bad
    • Object > Ticket > Satisfaction | Changed to | Bad with comment
  4. Under Actions, add:
    • Other > Notify by > Active webhook | Select the webhook you created
    • In the Body, enter the Slack notification formatted in JSON. For example:
      {"text":"You've received a negative CSAT. See information below \n ticket ID:{{ticket.id}} \n ticket link: {{ticket.link}} \n csat rating: {{satisfaction.current_rating}} \n csat comment: {{satisfaction.current_comment}}"}
  5. Click Create trigger

Trigger to post in Slack when a ticket gets a negative rating.png

In the example above, the JSON body is configured to send the ticket ID, a link to the ticket, the CSAT rating, and the CSAT comment to the Slack channel.

JSON is highly customizable. Configure formatting options for Slack webhooks and include ticket-specific information with Zendesk placeholders. To customize the Slack message, you must startthe JSON body with {"text":} for the call to be received in proper formatting.

After the webhook and trigger are created, you receive the formatted Slack notification when your account receives a bad CSAT rating.

Tip: To configure other notifications in Slack, see the tip contributed by Jacob in the Community article: Push notifications from Zendesk to Slack.

Edited Jan 28, 2025 · Leanne Britton

2

Followers

3

Votes

3

Comments


Leanne Britton commented,

CommentBuilding reports
Hi Dean,
 
At this time, we do not have the ability to report on the time in between the bot handoff and the agent's first reply. The closest available metric for this would be the Engagements First Reply time metric. As you noted however and as outlined in How is Engagement first reply time calculated when a bot transfers the chat to an agent?, this is calculated from the visitor's first message after the handoff and the agent's first reply, and not from the transfer event itself and the agent's first reply. With that said, our Product Team hopes to expand the reporting capabilities of Messaging within Agent Workspace. You can follow the Announcements page for more information on upcoming releases regarding Messaging reporting capabilities. 

View comment · Posted Feb 08, 2022 · Leanne Britton

0

Followers

0

Votes

0

Comments


Leanne Britton commented,

Community comment Q&A - Reporting and analytics
Hi Liz!
 
The best way to calculate the On Hold time for calls is by using one of the "Leg on-hold time" metrics in Zendesk Explore. Specifically, you can use the Leg on-hold time (sec), Leg on-hold time (min), or Leg on-hold time (hrs) metrics to see the total On Hold time in a ticket. You can find more information about these metrics in Metrics and attributes for Zendesk Talk.
 
For example, I created a basic report in my test account using the Talk: Calls Dataset. After applying the Leg on-hold time (sec) metric and the Ticket ID attribute, I'm able to see the total On Hold time for each of my Voice tickets:
 

View comment · Posted Jan 29, 2022 · Leanne Britton

0

Followers

0

Votes

0

Comments


Leanne Britton commented,

Community comment Feedback - Ticketing system (Support)
Hi Budi,

The first response time feature for Social Messaging is not GA yet and is currently gated under a flag. I will create a ticket on your behalf so we can discuss your options if this has not been enabled on your account.

If the Messaging First Response Time feature has been enabled in your account however, then you should be able to use the First Reply Time metric in the Support: Tickets Dataset to see the FRT of Messaging Channels (such as Facebook Messenger, Whatsapp, and Instagram DM).

To specify the Messaging channel you're interested in seeing, select the Messaging Channel(s) from the Ticket Channels attribute or filter. In my example below, I've filtered on the Facebook Messaging channel:



NOTE: The Messaging FRT enablement will only allow you to see FRT from Messaging channels from the time it was enabled onward and will NOT show historical data.

View comment · Posted Jan 05, 2022 · Leanne Britton

0

Followers

0

Votes

0

Comments


Leanne Britton created an article,

ArticleExplore recipes

Available on Suite Professional plans and aboveAvailable on Explore Professional plans and above

This recipe shows you how to combine zero agent replies into the one agent reply bracket when using the Agent replies brackets attribute.

What you'll need

Skill level: Moderate

Time Required: 10 minutes

How to create the report in Explore

    1. Open a report that uses the Agent replies brackets attribute, for example, Explore Recipe: Percentage satisfaction score based on agent replies.
    2. In the report builder, click the calculations icon () on the right sidebar and click Standard calculated attribute.
    3. On the Standard calculated attribute page, enter a Name for the attribute (for example LB Agent replies brackets), and then enter the following formula:
      IF(VALUE(Agent replies)=0)
      THEN "1"
      ELIF (VALUE(Agent replies)=1)
      THEN "1"
      ELIF (VALUE(Agent replies)=2)
      THEN "2"
      ELIF (VALUE(Agent replies)>2 AND VALUE(Agent replies)<=5)
      THEN "3-5"
      ELIF (VALUE(Agent replies)>5)
      THEN ">5"
      ELSE "0"
      ENDIF
      Tip: If you're working in a language other than English, read this article to help you enter Explore formulas in your language.
    4. Click Save.
    5. In the Columns panel, click Add.
    6. From the list of attributes, choose the custom attribute you created LB Agent replies brackets.

    You will no longer see a bracket for 0 replies because it is merged within the 1 reply bracket:

    Edited Oct 22, 2024 · Leanne Britton

    0

    Followers

    6

    Votes

    0

    Comments


    Leanne Britton commented,

    CommentAdditional ticket channels

    Hi Sarah,

    If an agent is already on a call with another agent, then it is not possible to simultaneously place a call to an end-user directly from a ticket. Instead, the agent would either need to transfer the call to the end-user's external number or need to add the end-user to the shared call via the Talk console. Steps to transfer a call can be found in Transferring calls and steps to add the user to the existing call can be found in Adding a third-party to a conference call.

    In either case, once the call to the end user has been completed, the agent(s) can then merge the new ticket into the existing end-user ticket.

    Hope this answers your question!

    Leanne Britton
    Technical Support Engineer

    View comment · Posted Aug 23, 2021 · Leanne Britton

    0

    Followers

    0

    Votes

    0

    Comments