13 event types streamed
Notifications, replies, conversation turns, sent messages, drafts, new signals, new leads, status changes, agent run completions, listen yields, LinkedIn incidents, channel status flips, stats updates · all pushed live.
Old SaaS gives you a refresh button. CloseHunt gives you a live pipeline. Every inbound reply, every agent run, every draft, every signal lands in your dashboard within seconds via a single server-sent stream. Open a lead, watch a prospect type back, see the conversation update without lifting a finger.
Notifications, replies, conversation turns, sent messages, drafts, new signals, new leads, status changes, agent run completions, listen yields, LinkedIn incidents, channel status flips, stats updates · all pushed live.
A single SSE stream multiplexes everything you can see. The server filters by your org · and, if you've opened a lead or agent, by that entity · so bandwidth stays minimal.
If SSE breaks (corporate proxy, captive portal, mobile network), the client falls back to HTTP polling every 20s. A status pill in the topbar tells you which mode is active.
Each event carries an ISO timestamp. On reconnect, the client sends ?since=<last-seen> and the server replays anything missed. At-least-once delivery.
Phone went to sleep? Browser tab in the background? The moment the tab regains focus, the client checks for missed events and catches up. No stale state.
No Redis, no Pusher, no Postgres LISTEN/NOTIFY. The same SSE endpoint works in dev (SQLite) and prod (Postgres). Vendor pub/sub later is a swap-out, not a rewrite.
Server-Sent Events (SSE) · one-way push from server to browser via the native EventSource API. Simpler than WebSockets, no extra infra. When SSE is blocked (rare corporate networks), the client auto-falls back to HTTP polling every 20s.
End-to-end ~3-5 seconds from DB write to your screen on a healthy connection. The internal poll cadence is 3s · events are pushed the moment they're detected.
Yes · modern iOS and Android browsers handle SSE natively. The provider auto-reconnects on tab focus, so a sleeping phone catches up the moment you wake it.
Each tab keeps its own SSE connection. The server-side cost is bounded (one DB poll per active connection on a 3s cadence), and events are scoped to your org so cross-tab traffic stays light.
Trial on request · contact our sales team.