Inbox and direct messages
Reading threads, composing messages, uploads, provisional send states.
Last updated: May 2026
Capabilities
The Fulreach LinkedIn-aligned inbox exposes:
- Conversation list enriched when possible with prospect/contact stage labels (A/B/C/D tagging).
- Message history, sorted chronologically ascending in web UI irrespective of upstream default ordering inconsistencies across legacy stacks.
- Compose textual messages or uploads classified as
audio,video, or generic file`—first outbound to a participant may implicitly create a LinkedIn DM thread through Unipile.
Sending flow (what you see)
Optimistic UI inserts a provisional message while upload/multipart payload proxies to API—then marks sent if provider acknowledges message_id. Failures mark failed with toast for text errors (media paths may differ slightly).
Client timeout guard: if a send sits > 60s pending, UI may mark failed even if network eventually succeeded—refresh thread to reconcile rare race.
Reliability notes
Unipile remains source of truth for chat bodies in TypeScript API mode—Fulreach layers enrichment (contact/prospect joins) best-effort; missing enrichments don’t block core send/read.
Search caveat (legacy mismatch)
Some UI query parameters for server chat search historically misaligned parameter names—if search feels inert in an older build, rely on scroll + filters or upgrade build where fix shipped.
Realtime
Server supports SSE streaming hooks for message events, but web inbox historically leaned on polling/manual refresh—don’t assume instant push until your deployment advertises live subscription.
Cross-links
Automated sequences ultimately call the same send stack as manual messages—see Sequences and automated follow-ups.