delivery-queue — Delayed Segmented Delivery

To schedule drip campaigns with human-like outbound pacing, you queue JSON delivery records with specific deliver_at timestamps. This approach segments message flows into timed intervals, preventing one-shot bot-like messaging across WhatsApp and Telegram.

Yes, you can flush pending queued messages to send them immediately. The delivery queue includes a flush mechanism that bypasses the original deliver_at timestamps, pushing all pending items through your connected channels without delay.

Segmented message delivery breaks outbound message flows into timed parts queued for specific timestamps. You need it to replicate natural cadence in multi-part product introductions, reducing spam detection risk and improving prospect timing.

Yes, the message queue supports delivery retries and lifecycle management. It maintains status transitions for pending, cancelled, and sent items, validates channel and recipient formats, and includes counters to track delivery attempts.

You cancel a specific scheduled message by updating its lifecycle status to cancelled before the deliver_at timestamp. The queue management system tracks status transitions, allowing you to cleanly abort pending deliveries while keeping records intact.

Delayed message scheduling requires validated channel and recipient inputs, properly formatted JSON delivery records, and correct delay ranges. It relies on manual queue management for cleanup of old sent or cancelled entries to maintain reliability.