Previously: We counted every CQL score assignment as 1 CQL in this metric. This meant that if a conversation was marked with ⚡️⚡️ and you changed it to ⚡️⚡️⚡️, this counted as 2 CQLs.
Now: Conversations can only count as 1 CQL total, no matter how many times that score was applied. 1 conversation = 1 lead, so the report reflects that now.
CQL Score
Before: We counted every CQL score assignment as 1 CQL in this metric. This meant that if a conversation was marked with ⚡️⚡️ and you changed it to ⚡️⚡️⚡️, this counted as 2 CQLs.
Now: Conversations can only count as 1 CQL total, no matter how many times that score was applied. 1 conversation = 1 lead, so the report reflects that now.
Conversations
Previously: A conversation's "time," i.e. where it shows in your timeframe filtering, was decided by the timestamp of the first message sent in it, whether it be from the bot, from an agent, or from the end user.
Now: The conversation's "time" is decided by the timestamp of the end user's first response.
Overall, this should have a minimal effect on your CQL total, but may be noticeable for lower volume customers, especially because of the recalculation of which conversations are counted in "this month," "last month," etc. As always, if you have a question, just chat us up down below!
Comments
0 comments
Article is closed for comments.