Best practices for generating guides using transcripts
When you create a guide using the Transcripts option, it is recommended that you follow these best practices to improve the results:
- (Mandatory) Enable AI Insights for the selected queue at the program level. For more information, see Work with a program.
- Ensure that the selected queue is AI Insights-enabled during the chosen date range. This helps the system identify details such as the reason for contact.
- Select a queue with a sufficient volume of data. Each reason-for-contact group must include a minimum of 30 conversations, so the queue should realistically contain a few hundred conversations during the chosen time period. Otherwise, the system filters out all transcripts and fails to generate a guide.
- Ensure that the filters match the queue. The date range, channel, and language must reflect what the queue actually handles. Any mismatch in these criteria results in zero conversations.
- Use a sufficiently wide date range. Low-volume queues should look back further (for example, 30 days) so reason-for-contact groups can reach the required threshold.
- Preferably, select queues with resolved or partially resolved interactions. Conversations without a resolution outcome do not contribute to clusters.
[NEXT] Was this article helpful?
Get user feedback about articles.