Conversations — how this works

In the app: /conversations

How it works

One thread per lead across every channel — email, LinkedIn, SMS, call, and voicemail — assembled live from the rows that already exist (replies, calls, appointments, sends), not a second copy. The left list is your triage queue with an SLA flag on any open conversation whose last inbound has gone unanswered too long; the right pane is the selected lead's thread, with claim / snooze / close. An inbound reply auto-populates the conversation and starts its SLA clock, and auto-pauses the lead's active cadence.

Data source

src/lib/inbox/conversationThread.ts (the thread view) + src/lib/inbox/conversationRepo.ts (the ownership/SLA overlay).

Troubleshooting

A conversation you expected isn't listed? The overlay row is created on the first inbound (or when you open/claim it) — a lead you've only ever sent to, with no reply yet, won't have one. SLA flags use the business timezone, not each lead's local time.

Who can see this: admin, setter