Inbox — conversation list
Tamika Jefferson2
Customer
Is the 2023 BMW 530i still available for a test drive this weekend?
37 sec ago
Robert Cook
Customer
Sounds good — I'll see you Saturday at 11. Thanks for holding it for me.
2:14 PM
Berald Jones1
Customer
Missed call — no voicemail left
Yesterday
Marcus Webb
Automation
Service reminder: your lease ends in 45 days. Let's talk about your options.
Mon
Priya Anand
Sales
Congrats again on the Defender! I've emailed your finance paperwork over.
Jun 12
Nadia Sole3
Customer
Is the Rubicon still on the lot? Chatting from your site.
2 min ago
Wes Colby
DAISI
Thanks for reaching out! A specialist will be with you shortly.
18 min ago
R2 leading icon = last ACTIVITY/CHANNEL type (text=comment · call=phone · email=envelope), WHITE by default; a MISSED call is the only colored case (red phone-slash, e.g. Berald Jones). Actor word (Customer/Sales/Automation/DAISI) + direction arrow (incoming ↙ / outgoing ↗) follow. Independent axes: selected (row 2, gray-07 .is-selected) · unread (leading blue-01 dot + blue .sb-marker count) · fully-read. .sb-statusdd footer left (with caret) + time bottom-anchored right. Each row carries the customer name, the customer status pill, channel/actor-type iconography, a generalized actor — Customer, Dealer, DAISI or Automation, never a proper name — a snippet of the last relevant message, and a timestamp of the last call, text or email in either direction, anchored consistently in the row. A blue dot marks an unread thread. The numeric badge counts unread incoming activities only — call, SMS and email — and excludes logs and every other non-incoming type. The unread dot is deliberately distinct from the customer-status color cues so the two are never confused. Read model (CPO ruling, 09-02 — the mail-client model). Opening a conversation marks it read. Unread is dealership-wide: one shared timestamp on the customer, so the first person to open the thread clears it for the whole team — there is no per-user read tracking. Chat rows carry the fa-comments mark in the single icon slot — the plural bubble form, because both single-bubble marks (fa-comment-alt-dots, fa-comment-dots) already read as SMS. The sub-channel is NOT shown at list density (08-06 ruling). The row has exactly one icon slot, one generalised actor word and one direction arrow, and it shows the class of sender because that is what triage needs; Website vs Facebook vs Instagram is revealed in the conversation header and on the bubble, never in the row.