Threads group related events into a single conversation view. An inbound Slack thread, an email reply chain, and the outbound replies your agent sent — all land in one thread. Find the thread view at Projects → your project → Threads.
The list
Each row is one conversation. A row shows:
- Source pills — which channel types the thread spans (email, slack).
- Title — the opening line of the conversation. Email threads use the
subject; slack threads use the first message’s text, with mentions
like
@alicerendered inline. - Summary — a one-line preview beneath the title; the first message’s short description.
- Metadata — message count, other participants, last activity.
Threads without a derived title (older conversations, or events that
didn’t carry a useful snippet) fall back to a predictable
<participant> · <channel> label so rows always read cleanly.
Filters + search
- Channel pills — scope the list to
email,slack,webhook, orall. - Search — matches across title and participant. Useful for finding a conversation by the person’s email or slack handle.
Opening a thread
Click a row for the full timeline. Each event shows inline with any replies your agent sent beneath it. Click any event to open the full event detail (raw payload, deliveries, verification state).
How threads are grouped
- Email: followed via the
References/In-Reply-Toheaders. Replies to your agent’s outbound reply also join the correct thread, even when the customer’s mail client strips the header chain. - Slack: grouped by
thread_ts— Slack’s own thread identifier. A reply to a message under a thread lands in the same Nevo thread; a top-level message starts a new one. - Webhook / cron: these don’t form conversations, so they don’t appear in the thread list. They’re inspected from the Events view instead.
Titles + summaries
Titles and summaries are snapshot once from the first message. Later replies in the same thread don’t rename the conversation or overwrite the preview, so the list row stays anchored to how the exchange opened. This keeps a long-running support thread from drifting away from what it was originally about.