Email Scheduling & Send Queue

NurtureHub automatically dispatches approved nurture emails on a timed schedule, manages retries on failure, and emits events for tracking — all without any manual intervention once a sequence has been approved.

How It Works

When an agent approves a nurture sequence for a contact, the scheduler immediately registers all three emails in the send queue with their target dispatch times. From that point, everything is handled automatically.

Default Send Schedule

Email	When It Sends
Email 1	Immediately on sequence approval
Email 2	3 days after approval
Email 3	7 days after approval

Delay intervals are configurable at the tenant level. Contact your account administrator to adjust the defaults for your agency.

Business Hours & Timezone

The scheduler is timezone-aware and respects each tenant's configured business hours. If a send time falls outside the configured window, the email is held and sent at the start of the next available business hours window.

Timezone and business hours are configured in Settings → Agency Preferences.

Send Queue Architecture

The send queue is built on Inngest, a durable event-driven job scheduler. This ensures:

• Reliability — jobs are persisted and survive restarts or transient infrastructure issues
• Precision — emails are picked up and dispatched at their scheduled time
• Observability — every send attempt, result, and provider message ID is recorded

Delivery Flow

Sequence Approved
       │
       ▼
Email 1 queued → dispatched immediately
Email 2 queued → dispatched after 3 days
Email 3 queued → dispatched after 7 days
       │
       ▼
[At send time]
Pick up from queue
       │
       ▼
Route through delivery adapter
       │
    ┌──┴──┐
  Success  Failure
    │          │
    ▼          ▼
Record result  Retry with backoff
+ message ID        │
    │          (persistent failure)
    ▼               ▼
emit email.sent   Record error

Failure Handling & Retries

If a delivery adapter returns an error, the send queue automatically retries with exponential backoff. If the send continues to fail after the retry policy is exhausted:

• The failure and adapter error detail are recorded against the email record
• The email is marked as failed in the contact's nurture timeline
• No email.sent event is emitted

Failed sends are visible in the contact's nurture history. No manual queue management is required.

The email.sent Event

A successful send emits an email.sent event. This event is the upstream signal for:

• Engagement tracking — open and click events are correlated to this send
• Intent scoring — real-time lead score updates depend on engagement data linked to email.sent
• Hot lead alerts — alert thresholds are evaluated against intent scores derived from tracked sends

If an email fails to send, none of the downstream tracking for that email will occur.

Tenant Configuration

Setting	Location	Description
Send delays	Tenant admin settings	Override default 3-day / 7-day intervals
Business hours	Settings → Agency Preferences	Windows during which sends are permitted
Timezone	Settings → Agency Preferences	Used to interpret business hours
Delivery adapter	Settings → Email Delivery	Provider credentials and sender identity