The Inbox feed and the customer-profile feed are the same feed and the same templates — repackaged, never forked. Channel color language: text blue · email purple · call green · failure red · neutral gray. Long rows expand with an explicit Show / Hide control, not a bare chevron. Incoming and outgoing keep their alignment, and the accent bar follows the channel or state. Pending and cancelled rows use the dashed treatment. Chat in the feed is pink. The bubble and indicator variants in this atom family are colour-keyed, not channel-keyed — there is no .sb-bubble--text — so Chat follows the convention exactly with .sb-bubble--pink + .sb-ind--pink; a channel-keyed name would start a second naming system inside one family. Title grammar matches its siblings: Chat Sent / Chat Received, mark fa-comments. The sub-channel word lives in the existing .sub slot — the same slot SMS uses for “SMS” and AI-sent messages use for “Auto” — so Website / Facebook / Instagram needs no new markup. Inbound sits left with the indicator leading, outbound sits right with it trailing, and Show/Hide is unchanged. Consecutive turns from the same actor within a short window collapse to one stamp plus stacked bubbles (Chat runs dozens of short turns per conversation). The grouping window is per-actor. Implemented as a WRAPPER (.sb-turngroup) plus a condensed head modifier (.sb-stamp--grouped, height only). A grouped turn IS a feed item — .sb-activity.sb-turngroup, never a parallel atom — so it inherits every existing and future .sb-activity override (feed width and the rest) for free, with no page-local rule and no allowlist. The modifier class carries only what genuinely differs: the tighter stacked-bubble spacing — the six base .sb-stamp rules are byte-unchanged, so the customer-profile feed that shares the atom is untouched. Authorship extends the existing precedent, it does not replace it: the bubble stays the channel colour (pink) and the stamp row carries the DAISI glyph + actor name — AI messages are never tinted yellow. This is load-bearing, not cosmetic: 83% of the AI's messages are currently miscounted as human activity, and the GM's daily question is "what's the last thing a human did versus AI?". Hard constraint: a change of actor ALWAYS forces a new stamp — grouping never merges an AI turn with a human turn, which is what keeps authorship legible when turns collapse. .sb-feedmark is the feed's non-message row — composed the same way, .sb-activity.sb-feedmark, so it spans the feed column wherever the feed is widened — a quiet boundary, not a bubble: no channel colour, hairline rules + gray type only, so it never competes with the messages around it. It carries a short line plus an optional small icon. Its one use is the identification boundary in a chat that began before the customer existed: "Identified as Marcus Delgado — phone collected" marks the turn where an anonymous website visitor became a customer record, connecting the anonymous half of the transcript to the named half. A chat can begin before the customer exists — a nameless website visitor chats, the AI holds the thread, and only when a phone number is collected does the customer record get created and the whole transcript (anonymous part included) land on their timeline. Pre-identification turns render in the existing stamp with a neutral glyph (fa-globe) and the honest label "Website Visitor" — deliberately the same web-visitor vocabulary as the Website Session bubble (fa-globe, unnamed visitor), so an anonymous chat reads as its sibling in the same feed, not a foreign object. Consecutive anonymous turns group normally (one actor). Never back-filled: earlier turns keep the "Website Visitor" label permanently even after identity is known — the transcript records what was known at the time, and renaming them to the customer would misrepresent it (and imply the rep knew who they were talking to when they did not). The .sb-feedmark identification line ("Identified as Marcus Delgado — phone collected") is the third reserved use of the marker and is what connects the two halves. Do not "improve" this by back-filling names. Every item is a live locked atom — .sb-activity / .sb-bubble (+ --blue/--purple/--green/--orange/--indigo/--red/--gray4/--dashed/--live) / .sb-ind / .sb-stamp / .sb-diff / .sb-player + .sb-transcript — no new atoms, tokens byte-identical. Message lifecycle: .hide reads "Show" collapsed (header only) / "Hide" expanded (header + .content); Scheduled = --dashed + .sb-sched countdown, Failed = --red --dashed, Canceled = --gray4. Channels: bubble color = channel; DAISI is an actor ("DAISI Auto Responder" via .sb-ic-daisi in the .sb-stamp) sending a normal blue/purple bubble — not a yellow bubble. Calls use the .sb-player audio player + "View Transcript"; Call Received names the answering dealer in the title; --live is header-only In Progress; Failed = --red --dashed. Record rows use a neutral .sb-ind + plain .sb-bubble, status as bare colored .state text, and the edit state expands the .sb-diff field changes (red − / green +). The AI-summary / aiPending state was removed (it no longer renders in the feed).