Close · Inbox

One inbox, and the poller is why

LinkedIn arrives on the poller's tick and email arrives on an inbound webhook, and both land in the same conversation table under the same pipeline. So a LinkedIn reply stops a sequence, honours a prose opt-out and reaches your CRM under exactly the rules an email reply does.

Talk to sales See pricing

GTM

MWMy workspaceworkspace

InboxSearch/14,208

AllRepliedBookedLost

Aisha BelloEmail

Thursday works. Send an invite for 2pm?

Booked

Priya RaghavanLinkedIn

Interesting. How does it handle our EU list?

Replied

Daniel OkoyeEmail

Not right now, maybe Q3.

Later

Jonas WeberEmail

Please take me off this list.

Opted out

Interesting. How does it handle our EU list?

Drafted · queued for the next tick

Honestly: we serve the US today and say so rather than implying otherwise. The controller-grade machinery is built. Provenance, retention, suppression, so an EU list is a decision rather than a rewrite. Worth twenty minutes Thursday?

Gate verdict recorded · unsubscribe and postal address injected

What is actually going on

Every claim below is followed by the mechanism under it, because a claim without a mechanism is a slide.

Channel-agnostic means channel-agnostic

The sequence stop, the keyword opt-out, the classification and the CRM dispatch are one code path. A LinkedIn opt-out suppresses by profile URL when no email exists.

Replying from a thread goes through the same gated path

There is no second send route out of the inbox. One click and the next eligible sending tick, not a new way to reach a person.

A chat id does not exist at send time

LinkedIn conversations learn their thread id from the first inbound message, which is the kind of detail that decides whether a reply threads correctly or opens a second conversation.

Lost is a folder, not a gap

Contacts whose sequence ran out move to lost with their conversations, so the pipeline reads as what is actually in play.

Step by step

How the unified inbox runs

1
Arrive
Poller tick for LinkedIn, inbound webhook for email.
2
Stop
Every pending step for that contact is skipped, before anything else runs.
3
Read
Keyword opt-out pass first, without a model. Then classification.
4
Dispatch
Contact record and a note out to the CRM, Slack, a Zap or a signed webhook.

The numbers

Facts, not adjectives

Every figure here is a real value from the running product. A cadence from the scheduler, a price from the credit table, a limit from the ramp. A marketing page that invents a limit is a support ticket with a delay on it.

CloseInbox

Poll cadence: Every minute
Email inbound: Webhook, on arrival
Opt-out: Keyword pass runs before classification
Suppression: One target per row. Both means two rows
Folders: Open, replied, booked, lost

The unified inbox, honestly

Why is the opt-out check not done by the model?

Because a missed opt-out is a regulatory failure and a missed nuance is a wrong badge. The keyword pass runs first, deterministically.

Does a reply to one channel stop the other?

Yes. Any inbound message skips every pending queue row for that contact regardless of which channel it arrived on.

Every reply, in one place, worked to a call

Every feature

Reply handlingClassified, drafted and queued. One unsent answer per threadOpen Booked meetingsThe calendar an agent books against, and the moment it tells everyoneOpen CRM & alertsSix CRMs, Slack, Zapier and signed webhooks. Verified before they read connectedOpen

Keep reading

All features

RepliesReply handlingClassified, drafted and queued. One unsent answer per threadRead more MeetingsBooked meetingsThe calendar an agent books against, and the moment it tells everyoneRead more ConnectorsCRM & alertsSix CRMs, Slack, Zapier and signed webhooks. Verified before they read connectedRead more

The unified inbox is one part of it. The rest runs too.

Sourcing, enrichment, intent, copy, sending, replies and reporting are one product with one bill and one gate. Connect a channel and the whole motion starts.