Dispatch Queue
The human gate on the send layer: review the drafts your runs produced, set the channel and recipient, and approve one to dispatch, with a per-tenant kill-switch.
Overview
Dispatch Queue is the approval surface for outbound. Your scheduled runs draft messages; this page is where a human reviews one, sets the channel and recipient, and approves it to dispatch. Every attempt runs through the same deterministic dispatcher the rest of the platform uses, and every attempt, sent or held, is recorded to the sends ledger shown at the bottom of the page.
The send-layer kill-switch
Sending is off by default, per tenant. The toggle at the top of the page is the kill-switch: with it off, approving a draft records the attempt and reports it as held, but nothing is sent. Turn it on only when you are ready to send for real. This means you can wire up and review the whole flow, approvals included, before a single message leaves, and turn everything off instantly if something looks wrong.
Approving a draft
Each draft carries content, not a destination, so you choose the channel (email via Instantly, LinkedIn via HeyReach) and enter the recipient when you approve it. The dispatcher gates the send in order: approval, then the send-layer toggle, then the channel configuration, then the send. The result is shown inline on the draft, one of sent, held (send layer off), held (provider not configured), or an error, so you always know exactly what happened.
Honest about what is live
The cold-send vendor paths (Instantly for email, HeyReach for LinkedIn) stay gated until they are verified against a real account, so until then an approval on a configured channel is still reported as held rather than a fabricated send. Nothing here claims to have sent a message it did not. The recent-dispatches list is the audit trail: it records held attempts too, so you can see the full history of what was approved and what actually went out.