Social Messaging - First Reply Time SLA (missing) | Community
Skip to main content
Delivered

Social Messaging - First Reply Time SLA (missing)

Related products:Ticketing system (Support)
  • November 2, 2020
  • 35 replies
  • 0 views

At this moment is not possible to have an SLA about "First Reply Time" in Social Messaging Tickets.

This particular SLA is very important, especially in this type of channel.

This topic has been closed for replies.

35 replies

  • November 3, 2020

Hi Unai,

 

Thanks for the feedback!

 

Can you tell me a bit more about why this is important for you and your team?

 

Also, is it more important for your agents to see the SLA badge in tickets or for you as an admin to be able to report on the first reply time in Explore?

 

Thanks,
Dean


  • Author
  • November 3, 2020

Hi Dean,

We need to use this SLA because is the way we use to prioritize our ticket in views. And the "Fist Reply time" is key in our Social Channels like WhatsApp.

Thanks,


  • November 4, 2020

Thanks, Unai,

 

We are planning reporting improvements in Explore, targeting H12021. This will include key metrics like First Reply Time, Comments etc.

 

SLAs are on our mind for 2021, but we don't have any concrete timelines right now.

 

I will add to this thread as things progress.

 

Thanks for your feedback.

Dean


Mary24
  • July 23, 2021

Gracias Dean, por la iniciativa del equipo!

Con respecto al SAT  (encuestas de satisfacción) para la mensajería WhatsApp, ¿también lo incluirán?


  • July 29, 2021

+1 

First reply time and Next reply SLAs are absolutely needed for social messaging channels, because customers' expectation is to get a near real-time response via these channels.

Any update on when that will be available?


  • August 3, 2021

It's a must thing, how I can know wether my agent replied customer in very first sec. or not. 

This will increase customer satisfaction. I don't know why zendesk provided this with email but not a will messaging platform as we are very well aware with technology, everything getting shifted to whatsapp and other communication platforms. 

Please requesting to implement its ASAP. This is a key function for us and reason as well to join zendesk. 


  • August 5, 2021

Barbara, 
SLA work is under discussion we still don't have a concrete timelines on the same, from feature perspective customers can now measure FRT for messaging conversation from explore. 


  • August 17, 2021

Hi Arpan,

Thank you for your response. Could you please guide me on how to achieve this within explore? When I set up a query using SLA dataset and choose "First reply time (min)", then all the Whatsapp tickets are showing only blanks. Please help. Thanks.


  • August 17, 2021

Hi Barbara, 

The first response time feature is not GA yet and is currently gated under a flag, you can reach out to us via support and we can enable the fix and guide you on steps for you to build the FRT reports. 


Erkin
  • October 7, 2021

Dear Arpan Nagdeve,

Could you please help us for FTR reports especially for WhatsApp. is there a native fix for that?

Thanks.


Erkin
  • November 8, 2021

Dear Arpan,

 

Could you please guide us for the next steps after the fix to build FRT Reports.

 

Thank you.

 


Budi
  • December 28, 2021

Dear Zendesk,

First reply time in Explore is an important metrics for us, as most of our customers come via Social Messaging channels (Whatsapp, Facebook, Instagram). We would like to know whether our agents are overloaded. Is there a a way to build this report on Explore?


Leanne12
  • January 5, 2022
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.

Mariana14
  • January 13, 2022

Hi team! I'm struggeling to calculate FRT for messaging channels in my Explore reports, If I select Whatsapp channel the metric First Reply time shows me blanks, there's any way to build a calculated field to get this information?
Thanks!!


Dane13
  • January 25, 2022
Hi Mariana,
 
As Messaging is fairly new, FRT is currently one of its limitations. However, it is currently being worked on and is already near fruition. We don't have an exact date yet so please keep an eye for any updates on our page.
 
Hope this helps.
 
Cheers,
Dane

  • January 25, 2022

Hi Dane,

Are you also planning to include "Next reply time" metrics for Social messaging channel in the future? That would be very useful too.

Thanks.


Dane13
  • January 25, 2022
Hi Barbara,
 
A new Messaging dataset is currently being worked on. Like the FRT, we don't have an exact date yet so please keep an eye for any updates on our page.
 
Cheers,
Dane

  • February 23, 2022

Since migrating from Live Chat to Messaging, we are now missing a vital piece of reporting - First Reply Time for Messaging. 

Checking in for an update please as I notice the latest comment here was last month.

Thanks, Emma


  • March 4, 2022

Hi Emma, 
 

The messaging dataset is slated to be released in Q3 however we have worked on a FRT metric for messaging ahead of time behind a feature gate for messaging that i have turned on for your subdomain, so you should be able to see it in explore now.

Do take note the FRT metrics currently has its smallest denominator in minutes and we are slated to release the FRT metrics in seconds at the end of April. 

Do let me know if you have any further questions!

Cheers,

Mei-E


Erkin
  • March 4, 2022

Hi Mei-E Loh,

Do we have to subscribe for the feature gate in order to see the FRT metrics in seconds at the end of the April? Or will the release done for all subdomains?

Cheers,

Erkin


  • March 8, 2022

Hi Erkin, 

 

There will be a feature gate for FRT metrics in seconds, we will probably add all the accounts currently on the chat ticket metrics feature gate to it.

Do let me know if you are not already on the chat ticket metrics, I can have your subdomain added to that and subsequently to FRT metrics in seconds. 

Cheers,

Mei-E 

 


Tim18
  • March 23, 2022

Hi Mei-E Loh,

What is this feature gate, is this an EAP or something else? I can't find FRT metrics for socials/messaging in this list.

As a Zendesk Partner, we have a customer who is really waiting on SLA for Whatsapp tickets. 


Erkin
  • March 23, 2022

Hi, 

I have checked the account which has been implemented a fix by Zendesk team. However there is no fix for second for FRT on WhatsApp channel. Can we use metrics in seconds right now? 

Thank you

 


  • March 23, 2022

Hi Tim, 

It is a short term fix for serving FRT metrics to messaging customers. I suspect it is not on the list as it is meant to be a short term fix and there is a long term plan to introduce this metric with the Messaging dataset that is currently in the works slated for EAP end of Q2 but i will find out if i can get it listed. 

In the meanwhile, if you send me a a list of customer subdomains i can get them added to the feature gate. Do take note that the FRT metric is currently only available in minutes at the moment and we will be releasing seconds on the API in early April and in Explore in early May. 

Cheers,

Mei-E 


  • March 23, 2022

Hi Erkin, 

As mentioned above, the FRT seconds is not available yet and will be released on the ticket metric API early April and in explore Early May. 

If you are already on the feature gate for messaging FRT it will be made available to you automatically then. 

Cheers, 

Mei-E