Please share the logic used by Conversation Aggregation to compute nConsult KPI

We have a case where nConsult metric is available only once per conversation but Conversation Aggregate provides nConsult = 2 which is correct.
Issue here is :- Conversation Detail query is missing one of the metrics : nConsult.
I would like to know, even in such case, how does conversation aggregate computes it correctly?
What is the additional logic it uses to compute count of of nConsult.

Create a customer care case so they can review your specific instance you're questioning and give guidance.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.