Review risky conversations
The risky conversations tab holds five summary cards and a risk table. Filter with a card, open a row, then weigh the rationale against the messages.
Five cards split the risk groups. In the "Müşteri dönüş yapmadı" label it is the customer who stopped writing, not the clinic. Clicking a card drops the table to that group. The "Bekleme" column currently shows a dash on every row, because the source data does not carry that duration.
Before you start
- Conversation Analysis ("Konuşma Analizi") visible in the left menu
- At least one conversation carrying a risk label in the period you chose
Step by step
These screens sit inside the Intent AI section. Sign in, open Intent AI; the menu names below are in that section's left menu.
Open the risky conversations tab
Open Conversation Analysis from the left menu and click the "Riskli Konuşmalar" tab.
Pick a risk group
Click the summary card you care about; the table drops to that group.
Narrow the list
Filter with the priority and AI confidence menus, and the search box if you need it.
Open the row in the drawer
Press "İncele" on the row you want to inspect.
Confirm the risk type matches your group
The value in the risk type column should carry the card you picked.
Result checkIf it did not work
Check these
- The "Müdahale Gerektiren" card counts the rows of type "Şikayet sinyali" that are loaded into the table, within the 150-row limit. It drops to zero while another risk card is selected. It is not a risk type but a suggested intervention level.
- A dash in the waiting column is not a fault. Sort by last message or priority instead.
- Do not read the silent-customer rows as the clinic failing to answer. Open the row and read the transcript before you act.
- The red "Supervisor müdahalesi önerilir" note is not on the table row; it appears in the AI Tespiti section of the drawer you open with İncele, and only on records of type "Şikayet sinyali".
Does this step look different in your panel?
We can review the screen and exact error text together.
This guide was checked against the product UI and code inventory on 4 October 2026.
