BrandJet AI
    HomePricing
    Contact us
    Get Started
    Quickstart
    Email Outreach
    Email Infrastructure
    Connect Email Accounts
    Campaigns & Sequences
    Why test emails are not arrivingPersonalization variables pulled the wrong dataTimezones, schedules and sending windowsTemplates library: reusable sequences and message templatesSequence Assistant: AI-drafted multi-step sequences
    Deliverability & Analytics
    Social & Multichannel
    Connect Social Channels
    Multichannel Campaigns
    Leads
    Find & Enrich Leads
    Import & Manage Lists
    Recurring Lead Collection
    Billing & Workspace
    Plans, Trials & Limits
    AppSumo, BYOK & Upgrades
    Workspace, Team & Account
    Replies & Unibox
    Unibox & Snippets
    Workflows
    Workflow Builder
    Lifecycle Sequences
    Artemis (AI Assistant)
    Getting Started with Artemis
    Troubleshooting Artemis
    Integrations & Developers
    MCP Server
    REST API & Webhooks
    CRM Integrations
    Slack, Discord & Notifications
    Monitoring & Intelligence
    Mentions
    Competitor & Social Tracking
    Content Feed & Website Analytics
    AI / LLM Monitoring
    Press & PR Tools
    Press Outreach
    AI Agents
    Agent Types & Setup
    Help Center/Email Outreach/Campaigns & Sequences

    5 min read

    Timezones, schedules and sending windows

    A campaign schedule controls when sends actually go out. BrandJet uses two layers: the campaign timezone for when the schedule applies, and the sending window for which hours of the day are allowed.

    Campaign timezone

    Each campaign has its own timezone. By default it inherits your workspace timezone, but you can change it for a specific campaign — useful when sending to a different region than where you are.

    • Set the timezone in Campaign → Settings → Schedule.

    • All sending window hours apply in that timezone, not in your local time.

    • Analytics charts in the campaign use the same timezone for daily and hourly grouping.

    Indian Standard Time and other regional zones

    IST (Asia/Kolkata, UTC+5:30) is supported alongside all standard IANA timezones. If you do not see your region in the list, search by city name (Mumbai, Karachi, Dhaka) — BrandJet uses IANA zone identifiers under the hood.

    Sending window

    Inside the schedule, set a daily start and end time and choose which days of the week are active. Campaign messages only send during the active window.

    • Default: Monday to Friday, 09:00 to 17:00.

    • You can overlap windows across multiple time blocks if you want a lunch break (for example 09:00 to 12:00 and 14:00 to 17:00).

    • A 24/7 sending window is allowed but rarely a good idea for cold outreach.

    How rate limits interact with the window

    Each inbox has a daily send limit. The campaign distributes the day sends across the sending window:

    • If you have 40 sends to do in a 4-hour window, sends are spaced roughly every 6 minutes.

    • If the window closes before all sends complete, the remainder rolls to the next active day.

    • BrandJet adds small randomness between sends so the cadence does not look automated.

    Schedule a campaign for a future launch

    If you want the first message to go out at a specific date and time:

    1. Build and review the sequence as usual.

    2. Click Launch, then choose Schedule.

    3. Pick the date, time, and timezone for the first send. The whole sequence then follows the configured delays from there.

    Pausing and resuming

    • Pausing a campaign stops scheduling new sends. In-flight sends already queued for the current minute will go out.

    • Resuming picks up the next eligible send in the next available sending window — no need to manually re-schedule.

    Per-lead scheduling

    If a lead has its own scheduledFor timestamp (set via API, workflow, or manual edit on the lead), that timestamp wins over the campaign window — useful for follow-ups timed to a webinar or event.

    Daylight saving time

    BrandJet follows the IANA timezone rules, so DST transitions are handled automatically. Your 09:00 send stays at 09:00 local time across the change.