Here is the use case:
Currently, we are able to look at the transcript traces and logs view along with the audio file to be able to go through the entire session and identify hiccups.
When we do identify a particular hiccup (e.g. an STT accuracy issue in a particular scenario, an LLM error, or even the SFX not being played from our backend), I would like to tag those issues within the timeline of the call and then aggregate those issues through some statistical coding (like axial codes).
This way, if we review say 50 sessions, we can pinpoint what the top 10 issues are and also identify these sessions that correlate to those 10 issues at a timestamp level so that we can snipe out the issues.
Let me know if this is clear