Mark an attention item as Seen
The Görüldü (Seen) button shows up only on new rows, the ones with a purple dot. Press it once. Marking sends nothing to the customer and resolves nothing.
Marking tells your team that somebody reviewed the item. Every row locks for a moment while the request runs, and the row you pressed shows three dots. The server answers in one of four ways, and three of those raise a band across the top of the page. The record stays in the queue and only its chip changes.
Before you start
- A row in the new state; no purple dot means no button
- A user account that can open the supervision screen
- No other marking in flight at the same moment
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.
Find the item in Dikkat Kuyruğu
Switch to the Dikkat Kuyruğu (Attention Queue) tab on the Sohbet Gözetimi screen. Find the row with the purple dot, and press Sohbeti aç (Open chat) first if you need the context.
Press Görüldü at the right end of the row
Press the Görüldü (Seen) button once, at the right end of the row. Do not click empty space on the card, because that opens the transcript instead.
Look for the grey Görüldü chip
The purple dot disappears. A grey Görüldü chip takes its place, followed by the marking user's id, for example “Görüldü · user:42”. The Dikkat bekleyen card then counts one item less as new.
Result checkIf it did not work
Check these
- The band “Bu sohbete yeni mesaj geldi — kayıt yeniden açıldı, işaretleme geçerli değil.” means the customer wrote again and the mark did not hold. Open the transcript, read the new message, then mark it again.
- If the band reads “Bu kaydı başka biri az önce işaretlemiş.” or “Bu kayıt bu arada çözülmüş.”, the work is already done. Check the chip on the row and move on.
- “İşaretleme yanıt vermedi (20 sn).” leaves the outcome unknown. Press Yenile (Refresh) and read the chip on that row before you press Görüldü again.
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.
