MUGO

Thanks Meedo. I was more interested in measuring FRTs and SLAs in Tymeshift since it forecasts according to "Staffing parameters" that contains volume, wait time (sum of FRTs I assume), concurrency and AHT.  The point of using Tymeshift is not to use ZD Explore (or just to crosscheck and verify the data that Tymeshift streams) 

Hey there, 

Is there way of measuring FRT for chat/messaging tickets? 

Hello there. 

Is there an Explore recipe that shows/verifies the historical data Tymeshift uses?