Deliveries

The "Deliveries" section is used to send messages to selected leads in bulk. You can prepare text and attachments, check recipients, send a test, start immediately or on a schedule, and view the result.

Open Deliveries in the project side menu. The delivery list opens.

What You Can Do

• create a delivery and prepare its message;
• select and check recipients;
• send a test, start immediately, or schedule a start;
• understand statuses and stop, copy, share, or delete a delivery.

Delivery List

The tabs group deliveries by state:

• "Waiting" - deliveries that have not started and scheduled deliveries;
• "Processing" - deliveries that are queued, collecting recipients, or sending;
• "Completed" - completed, stopped, and failed deliveries;
• "Deleted" - deleted deliveries.

Search checks the delivery name and message text.

Each delivery row always shows the name. Depending on the delivery and current tab, it may also show the scheduled start, attachment count, recipients, sent and not sent messages, progress, and update date. The visible columns also depend on screen width.

Select a row to open the delivery. Its commands are also available in the actions menu; the available set depends on status and run history.

Reading The Metrics

On the "Waiting" tab, the recipient count is calculated from the current filters and shows unique people, not lead records. Before a run, it can change as leads, subscriptions, and audience settings change.

After a run starts, "Recipients" shows the audience size of that run. "Not sent" combines skipped messages and sending errors. On the "Processing" tab, progress shows the share of recipients already processed.

Detailed statuses and commands for each state are described in Statuses and Actions.

Access

Viewing the list and delivery cards requires permission to view deliveries. The same permission is enough to copy an eligible delivery or share it by link. Creating, editing, testing, starting, stopping, and deleting require permission to manage deliveries; importing a copy requires manage access to every package resource type in the target project.