
The unified Inbox
Inbox is the catch-all for messages that came in (or went out). Every inbound email, every inbound SMS, every reply waiting on you, in one list, sorted newest first. It's the place to triage when you sit down at the start of the day or come back after a showing.
What shows up here
The Inbox aggregates Activities across channels:
- •**Email** (inbound replies routed through Nylas, plus your outbound sends if you switch to the Sent tab)
- •**SMS** (inbound texts from your Twilio number, plus outbound if you switch tabs)
- •**Calls** show up too when filtered (recent inbound, missed, voicemail)
Each row shows the contact name, channel icon, subject or preview, time ago, and an unread dot for inbound rows you haven't opened yet. Threaded conversations roll up: if a contact sent you three replies in a row, you see one row with a count badge, not three rows.
Three tabs that shape what you see
Across the top:
- •**Direction:** Received / Sent / All. Default is Received (inbound only). Sent is your outbound log. All shows everything chronologically.
- •**Ownership** (only meaningful on Received / All): My queue / Unassigned / All team. By default you see your queue: rows assigned to you. Unassigned is the team triage view (anything inbound that nobody's claimed yet). All team is the firehose.
- •**Channel filter:** All / Email / SMS, plus an Unread toggle.
The Unassigned tab is the team-lead's view. When a teammate inherits a lead from you, or when a new inbound lands without an obvious owner, it shows up here for someone to claim.
Claiming
Inbound rows that aren't assigned to anyone show a "Claim" button. Hit it: the row assigns to you, and a reply-auto-claim rule means any further inbound on that thread also lands in your queue. You won't fight over threads with a teammate.
Marking read
Rows mark themselves read when you click them and land on the contact card. There's a "Mark all read" button in the header for clearing the queue in one shot when you've triaged.
Marking-read is a unread-state-only operation. It doesn't archive, doesn't dismiss, doesn't hide anything. Every Activity remains queryable forever. Cody can still find it when you ask "did Sarah ever email me about 142 Eastern?"
Inbox vs. Brief: when to use which
This is the question. Short version:
- •**Brief** is the AI catch-all chat thread. You go to Brief when you want to *do something*: draft an email, run a CMA, ask "what needs my attention today?", drop a PDF. Brief is conversation-first. It tells you what's hot and what slipped.
- •**Inbox** is the message list. You go to Inbox when you want to *scan what came in*: read replies, claim unowned threads, see who hasn't gotten back to you. Inbox is list-first.
A typical morning: open Brief, ask "what needs my attention today?", get the daily brief with hot leads and stalled deals. Then jump to Inbox, scan inbound from overnight, reply to anything urgent, claim anything new. Then back to Brief to actually draft the work.
If you only use one, use Brief. If you have a team, you'll live in Inbox.
Where to go next
- •`brief`: the daily catch-all chat thread
- •`notifications`: push + the in-app notification bell
- •`email-in-closr`: how inbound email routing works under the hood