Components
Conversation details sheet
Read routing, ownership and activity without confusing metadata with verified infrastructure.
On this page
Purpose and composition
Read routing, ownership and activity without confusing metadata with verified infrastructure.
Use for inspection, separate from the person profile and message-level source.
Anatomy
| Part | Responsibility |
|---|---|
| Summary card | Subject, queue/type and optional follow-up badges |
| Details | Person, inbox, assignee, recipients, messages and activity |
Configuration and variants
| Input / variant | Contract |
|---|---|
| conversation/contact | Required typed records |
| open/onClose | Controlled sheet |
States and feedback
| State | Visible / behavioral result |
|---|---|
| Assigned | Named teammate |
| Unassigned | Explicit fallback |
| No added recipients | Readable empty text |
| Open | Right-side native sheet |
Interaction and responsive behavior
- Read-only sheet; no metadata mutation.
- Resolve product/inbox through source helpers.
- Keep long address/subject content readable in narrow layouts.
Accessibility contract
- Definition list provides term/value relationships.
- Sheet close action is labeled.
Known implementation limits
Inbound route wording is a static source string, not evidence that the fixture was actually routed by a provider.
Composition example
<ConversationDetailsDialog conversation={thread} contact={person} open={open} onClose={close} />Source references
| File | Responsibility |
|---|---|
| components/inbox/conversation-details-dialog.tsx | ConversationDetailsDialog |
Examples from the app
Actual Sonarist components with fictional conversations, people, example.com addresses and simulated operational states. Captured at 2× resolution or higher. Select an image to inspect it full size.
Related topics
Source audit: 2026-10-08 · Revision 10f45d1377b5 · Documentation v1.0.0