---
name: scheduled-message-sending
description: Schedule customer support responses to send at optimal times based on customer timezone, engagement patterns, and business hours. Use when managing timezone-aware message delivery, optimizing response timing, scheduling follow-up sequences, implementing smart send-time optimization, managing after-hours responses, or reducing notification fatigue. Triggers on phrases like "scheduled messages", "send at optimal time", "timezone-aware", "smart scheduling", "message scheduling", "send-time optimization", "after-hours response".
---

# Scheduled Message Sending

Deliver support responses at the optimal time for each customer, respecting time zones, engagement patterns, and business hours while maintaining response speed and quality.

## Workflow

### 1. Timezone Detection and Customer Profile Building

1. **Timezone identification sources**:
   - Account registration data: Timezone selected during signup
   - IP address geolocation: Detected from login activity (verified monthly)
   - Email engagement patterns: Average open times from email tracking
   - Calendar integration: If connected, infer timezone from calendar events
   - Manual override: Customer or agent can set timezone in profile
   - Confidence scoring: High (explicit profile), Medium (IP + engagement match), Low (single source)

2. **Engagement pattern analysis**:
   - Track email open times over last 90 days (minimum 10 data points)
   - Identify customer's active hours window (e.g., typically opens between 9-11 AM and 2-4 PM)
   - Detect working pattern: 9-5 standard, shifted hours, weekend worker, global nomad
   - Classify as: Early Bird (before 10 AM), Standard (10 AM-2 PM), Late (after 2 PM), Evening (after 6 PM)
   - Segment by day patterns: Monday-heavy, mid-week, end-of-week, consistent

3. **Customer communication preferences**:
   - Preferred channel: Email, SMS, in-app, phone
   - Do-not-contact windows: Customer-set quiet hours (e.g., no contact before 8 AM or after 8 PM)
   - Contact frequency cap: Max X messages per day/week from support
   - Language preference: Match response language to customer preference
   - Urgency override flag: Critical messages bypass all scheduling rules

### 2. Smart Scheduling Engine

1. **Send-time optimization algorithm**:
   - Priority 1: Customer's historical engagement window (when they typically read/respond)
   - Priority 2: Customer timezone business hours (8 AM-6 PM local)
   - Priority 3: Support team coverage (ensure agent availability for follow-up)
   - Priority 4: Avoid peak spam windows (9-10 AM on Monday — highest inbox volume)
   - Priority 5: Respect customer's do-not-contact preferences

2. **Urgency-based scheduling tiers**:
   ```
   SCHEDULING TIERS
   ================
   P0 - Critical (system down, security issue):
     Send immediately, regardless of timezone
     Additional channels: SMS + email + in-app notification
     
   P1 - High Priority (blocking issue, VIP customer):
     Send within 15 minutes
     Respect hard boundaries (after midnight local)
     If outside business hours: send with "We understand it's late — reply when convenient"
     
   P2 - Standard (regular support response):
     Schedule for next optimal time in customer's timezone
     Target: 9:30 AM - 11:30 AM local (highest open rates)
     Fallback: 1:00 PM - 3:00 PM local
     Max wait time: 4 hours from agent compose time
     
   P3 - Low Priority (informational, follow-up, survey):
     Schedule for best engagement time based on historical data
     Can wait up to 24 hours for optimal timing
     Batch with other scheduled sends to reduce frequency
   ```

3. **Holiday and awareness rules**:
   - National holiday calendar per country (US, UK, EU, APAC)
   - Major religious holidays by detected customer region
   - Black Friday/Cyber Monday awareness (lower engagement expected)
   - End-of-quarter awareness (higher volume, adjust expectations)
   - Company maintenance windows (don't send during planned downtime)

### 3. Message Queue and Delivery Management

1. **Queue management**:
   - Messages enter queue with: scheduled time, priority, customer ID, channel
   - Queue processes in priority order with timezone-adjusted delivery times
   - Conflict detection: If customer already has 3+ messages scheduled within 1 hour, delay lower-priority messages
   - Consolidation: Multiple low-priority messages to same customer → combine into single digest
   - Dead letter queue: Failed sends go to retry queue (3 retries, exponential backoff)

2. **Delivery optimization**:
   - Email: Optimize for mobile-first rendering, dark mode compatible
   - SMS: Character count optimization, link shortening, delivery confirmation
   - In-app: Notification timing to avoid interrupting active work sessions
   - Phone: Only for scheduled outbound calls (never auto-call outside business hours)
   - Channel fallback: If primary channel fails (email bounced), try secondary channel

3. **Agent workflow integration**:
   - Agent composes response as normal in help desk
   - System auto-suggests optimal send time: "Customer's timezone: EST (4 hours behind). Optimal send: 2:30 PM your time (9:30 AM their time)"
   - Agent can: Accept suggested time, pick custom time, send immediately, or schedule via calendar picker
   - "Schedule for optimal time" button: One-click auto-schedule
   - Draft auto-saves: Agent can revisit and edit scheduled messages before send
   - Bulk scheduling: Schedule multiple follow-up messages at once

### 4. Monitoring and Analytics

1. **Scheduling effectiveness metrics**:
   - Optimal-time send rate: % of messages sent during customer's engagement window
   - Open rate comparison: Scheduled vs immediate send (target: +15-25% improvement)
   - Response rate: Customer reply rate within 24 hours of scheduled message
   - Send-time distribution: Histogram of actual delivery times by customer timezone
   - Customer complaint rate about timing (e.g., "why am I getting this at 2 AM?")

2. **Continuous optimization**:
   - Weekly analysis of open/response rates by send time and day
   - A/B test different send-time algorithms
   - Update customer engagement profiles as new data arrives
   - Retrain send-time model monthly
   - Identify and flag customers with inconsistent patterns for manual review

3. **Exception monitoring**:
   - Messages that failed to send (delivery errors, bounced emails)
   - Messages sent outside customer's timezone (compliance audit)
   - Queue backlog warnings (if >500 messages pending at any time)
   - SLA breach risk: Scheduled message would miss SLA deadline

## Templates & Frameworks

### Scheduled Message Dashboard

```
SCHEDULED MESSAGES DASHBOARD — August 2025
===========================================

QUEUE STATUS:
  Messages in queue: 127
  Scheduled for next 1 hour: 34
  Scheduled for next 4 hours: 89
  Scheduled for next 24 hours: 241
  Failed/retry queue: 3

SEND-TIME OPTIMIZATION:
  Messages sent at optimal time: 8,430 (78%)
  Messages sent immediately (overridden): 2,150 (20%)
  Messages sent at suboptimal time: 320 (3%)
  
  Open rate comparison:
    Optimal-time sends: 47.2% open rate
    Immediate sends: 38.4% open rate
    Suboptimal sends: 29.1% open rate
    Improvement from optimal scheduling: +23% ✓

TIMEZONE COVERAGE:
  EST (Eastern):     2,340 messages scheduled
  PST (Pacific):     1,870 messages scheduled
  CET (Central EU):  1,540 messages scheduled
  JST (Japan):       890 messages scheduled
  IST (India):       1,230 messages scheduled
  Others:            1,630 messages scheduled

CHANNEL DISTRIBUTION:
  Email:     9,240 (85%)
  SMS:       890 (8%)
  In-app:    620 (6%)
  Phone:     20 (0.2%)

PRIORITY BREAKDOWN:
  P0 (Immediate):  180 (1.7%)
  P1 (Within 15m): 1,240 (11.5%)
  P2 (Standard):   7,680 (71.1%)
  P3 (Flexible):   900 (8.3%)

AGENT ADOPTION:
  Agents using scheduling: 38 of 42 (90.5%)
  Average scheduled messages per agent/week: 14
  Top adopter: Maria S. (27 scheduled/week)
  Most overridden: Immediate send (agents prefer sending right away for P2)

PERFORMANCE IMPACT:
  Customer response time (after scheduled email): 4.2 hours avg
  Customer response time (after immediate email): 6.8 hours avg
  CSAT for scheduled messages: 4.5/5.0
  Timing complaint rate: 0.3% (messages received at inconvenient time)

BEST PERFORMING SEND TIMES BY TIMEZONE:
  EST:  9:30 AM (48.1% open) > 1:00 PM (45.3%) > 11:00 AM (43.7%)
  PST:  10:00 AM (46.8%) > 2:00 PM (44.1%) > 9:00 AM (42.5%)
  CET:  9:00 AM (49.2%) > 11:30 AM (46.7%) > 3:00 PM (43.9%)
  JST:  10:00 AM (44.5%) > 1:00 PM (43.2%) > 4:00 PM (41.8%)
  IST:  11:00 AM (47.6%) > 5:00 PM (45.1%) > 9:30 AM (42.3%)
```

### Customer Engagement Profile Template

```
CUSTOMER ENGAGEMENT PROFILE
============================

ACME CORP — Contact: John Smith
  Timezone: America/New_York (EST/EDT) — Confidence: HIGH
  Timezone sources: Profile (explicit) + IP (consistent) + Engagement (matches)

ENGAGEMENT PATTERNS (Last 90 Days):
  Typical active window: 8:30 AM - 5:30 PM EST
  Peak engagement: 9:30 AM - 11:00 AM EST
  Secondary window: 1:00 PM - 3:00 PM EST
  Pattern type: Standard 9-5 worker
  Day preferences: Tuesday-Thursday (highest engagement), Monday (lower), Friday (lowest)
  
  Email metrics:
    Average open time: 10:14 AM EST
    Average response time: 3.7 hours after open
    Open rate (optimal timing): 52%
    Open rate (suboptimal timing): 31%
    
  Historical data points: 47 email opens tracked

COMMUNICATION PREFERENCES:
  Preferred channel: Email
  Do-not-contact: Before 7:00 AM or after 8:30 PM EST
  Max messages: 3 per day from support
  Language: English
  Urgency override: Yes (P0/P1 bypass all rules)

SCHEDULED MESSAGE HISTORY:
  Total scheduled messages received: 23
  Opened within 1 hour: 19 (83%)
  Replied to: 12 (52%)
  Never opened: 2 (9%)
  Opt-out requests: 0
  
  RECOMMENDED SEND TIMES:
  Best: Tuesday-Thursday, 9:30-10:30 AM EST
  Good: Tuesday-Thursday, 1:00-3:00 PM EST
  Acceptable: Monday/Wednesday/Friday, 9:00-11:00 AM EST
```

### Scheduling Policy Document

```
SCHEDULED MESSAGING POLICY — 2025
===================================

GENERAL RULES:
  1. All customer-facing messages should be scheduled when agent composes
     outside customer's business hours (before 7 AM or after 8 PM customer local)
  2. Agents MUST send immediately for P0/P1 issues (system down, security)
  3. Agents SHOULD schedule for optimal time for P2/P3 messages
  4. Agents MAY override scheduling if business justification exists

TIMEZONE COMPLIANCE:
  - Messages to customers in different timezones: Schedule for their business hours
  - Minimum timezone accuracy: Medium confidence (2+ sources)
  - If timezone unknown: Use US Eastern as default, flag for update
  - Never send to known timezone outside 7 AM - 8 PM local

FREQUENCY CAPS:
  - Maximum support messages per customer: 3 per day (P0/P1 exempt)
  - Survey/follow-up messages: Maximum 1 per week per customer
  - If queue has 3+ pending for same customer: Auto-consolidate lowest priority
  
  EXCEPTIONS (immediate send allowed):
  - P0: System outage affecting customer
  - P1: Security incident, data breach notification
  - Legal/Compliance: Regulatory notification requirement
  - SLA breach risk: Message required to meet SLA commitment
  - Customer-initiated: Reply to customer's immediate question

HOLIDAY AND AWARENESS:
  - No scheduled P3 messages on: Christmas Day, New Year's Day, 4th of July (US)
  - No scheduled P3 messages on regional holidays (per customer's detected region)
  - Black Friday/Cyber Monday: Pause all non-essential scheduled messages
  - End of fiscal quarter: Increase scheduled send volume for renewal reminders

COMPLIANCE:
  - All scheduled messages logged with: send time, timezone, priority, agent, customer
  - Audit trail available for 12 months
  - Customer opt-out honored within 24 hours
  - GDPR: Scheduled messages to EU customers require consent verification
  - CAN-SPAM: All emails include unsubscribe link and physical address

ESCALATION:
  - If scheduled message fails to send: Alert agent within 15 minutes
  - If queue backs up >500 messages: Alert support manager
  - If SLA breach risk from scheduling: Override and send immediately
  - If customer complains about timing: Review and update customer profile
```

## Integration Points

- **Help desk systems** (Zendesk, Freshdesk, Intercom): Message compose integration, scheduling API, agent workspace UI
- **Email service providers** (SendGrid, Amazon SES, Mailgun): Scheduling delivery, tracking opens/clicks, bounce handling
- **SMS platforms** (Twilio, Plivo): SMS scheduling, delivery confirmation, opt-out management
- **CRM systems** (Salesforce, HubSpot): Customer timezone data, communication preferences, engagement history
- **Calendar systems** (Google Calendar, Outlook): Business hours detection, holiday calendars, meeting context
- **Product analytics** (Mixpanel, Amplitude): In-app notification timing, user session data
- **Analytics platforms**: Open rate tracking, response rate measurement, A/B testing infrastructure
- **Holiday APIs** (Nager.Date, local holidays API): Regional holiday detection for scheduling avoidance

## Edge Cases

- **Customer in traveling timezone**: Frequent traveler with inconsistent IP-based timezone:
  - Prioritize explicit profile timezone over IP detection
  - Flag customers with >4 timezone changes in 30 days for manual review
  - Use email engagement patterns as secondary signal (more stable than IP)
  - Allow agent to set "fixed timezone" flag to prevent auto-changes
  - If truly nomadic: default to customer's home country timezone from billing address
- **Scheduled message becomes outdated**: Product changes or new information emerges while message is queued:
  - Agent receives notification: "You have a scheduled message for Customer X in 2 hours"
  - System surfaces recent product updates, incidents, or KB changes that may affect the message
  - Agent can edit or reschedule before send
  - Critical product changes: Alert all agents with scheduled messages about affected topics
- **Message delivery failures**: Scheduled email bounces or SMS fails:
  - Automatic retry: 3 attempts with 1-hour, 4-hour, 12-hour delays
  - After 3 failures: Alert agent, suggest alternative channel
  - Update customer profile: Flag email as invalid, suggest phone/SMS
  - Log delivery failures for sender reputation monitoring
  - Monitor: 1.2% delivery failure rate (target: <2%)
- **After-hours agent composing for after-hours customer**: Both in different timezones, both outside business hours:
  - System schedules for customer's next business hours (agent's after hours)
  - Agent goes offline knowing message will deliver at optimal time
  - If customer replies outside scheduled window, message goes to after-hours queue
  - On-call agent handles if P0/P1, otherwise waits for next business day
- **Bulk scheduled sends causing notification fatigue**: Multiple agents schedule messages to same customer within hours:
  - Queue consolidation: If 2+ non-urgent messages scheduled within 2 hours → combine into single digest
  - Frequency cap enforcement: 3rd message per day requires manager approval
  - Smart batching: End-of-week summaries batched into single Friday message
  - Customer-controlled: Allow customers to request "weekly digest" instead of individual messages

## Output

### Monthly Scheduling Performance Report

```
SCHEDULED MESSAGING MONTHLY REPORT — August 2025
==================================================

VOLUME METRICS:
  Total messages scheduled: 10,900
  Total messages sent immediately: 2,470
  Scheduling adoption rate: 81.6% (↑ 5.2% from July)
  Messages successfully delivered: 10,756 (98.7%)
  Delivery failures: 144 (1.3%)

EFFECTIVENESS:
  Metric                    | Scheduled    | Immediate    | Difference
  --------------------------|--------------|--------------|----------
  Open rate                 | 46.8%        | 38.1%        | +8.7 pts ✓
  Response rate (24h)       | 31.2%        | 24.7%        | +6.5 pts ✓
  Customer CSAT             | 4.5/5.0      | 4.3/5.0      | +0.2 ✓
  Timing complaints         | 0.2%         | 1.1%         | -0.9 pts ✓
  Opt-out requests          | 0.1%         | 0.4%         | -0.3 pts ✓

TIMEZONE IMPACT:
  Messages across timezones: 7,340 (67.3% of scheduled)
  Timezone-accurate sends: 7,210 (98.2% of cross-timezone)
  Estimated timezone-improvement: +12.4% open rate for cross-timezone sends
  Top timezone pairs: EST→CET (1,230), PST→JST (890), CET→IST (760)

AGENT ADOPTION:
  High adopters (>20 scheduled/week): 18 agents
  Medium adopters (10-20/week): 16 agents
  Low adopters (<10/week): 8 agents
  Non-adopters: 0 agents (100% adoption achieved!)
  
  COACHING TARGETS:
  - 3 agents averaging <5 scheduled/week — suggest training session
  - 2 agents with 95%+ immediate sends — discuss timezone awareness
  - Top performer (Maria S.) to share best practices at next team meeting

COST AND EFFICIENCY IMPACT:
  Reduced after-hours support requests: 23% decrease
  Agent satisfaction with scheduling tool: 4.3/5.0
  Estimated time saved (fewer re-sends/replies): 120 hours/month
  Customer engagement quality improvement: +15% overall
```