Overview
Message scheduling in GoBlue allows you to send messages at optimal times for maximum engagement, create automated follow-up sequences, and respect recipient preferences. This guide covers advanced scheduling strategies, timezone handling, and automation techniques for sophisticated messaging campaigns.Message scheduling works in conjunction with iOS Shortcuts, which handles the actual message delivery at the scheduled time.
Scheduling Fundamentals
How Scheduling Works
GoBlue’s scheduling system operates through a multi-layer approach:1
Queue Management
Messages are queued with scheduled delivery times
2
iOS Shortcuts Processing
iOS Shortcuts polls the queue and sends messages at scheduled times
3
Status Updates
Delivery confirmation updates message status in real-time
4
Analytics Tracking
Performance metrics track optimal sending times
Scheduling Types
Immediate
Use Case: Urgent responses, confirmations
Delay: 0-5 minutes
Priority: High
Delayed
Use Case: Follow-ups, nurture sequences
Delay: Hours to days
Priority: Normal
Optimal Time
Use Case: Marketing campaigns, announcements
Delay: Based on recipient behavior
Priority: Variable
Sequence-Based
Use Case: Drip campaigns, onboarding
Delay: Progressive intervals
Priority: Low to normal
Timezone Management
Global Timezone Support
Handle recipients across different timezones effectively:Timezone Detection Methods
Phone Number Analysis
Phone Number Analysis
IP Geolocation
IP Geolocation
User Preferences
User Preferences
Optimal Timing Strategies
Engagement-Based Scheduling
Use historical data to determine the best times to message each contact:Industry-Specific Timing
Tailor message timing based on industry patterns:- B2B Industries
- B2C Industries
- Global Markets
Optimal Times:
- Technology: Tuesday-Thursday, 10 AM - 3 PM
- Healthcare: Monday-Friday, 9 AM - 11 AM, 2 PM - 4 PM
- Finance: Tuesday-Thursday, 8 AM - 10 AM, 1 PM - 3 PM
- Consulting: Monday-Thursday, 10 AM - 4 PM
Automated Sequences
Drip Campaign Scheduling
Create automated follow-up sequences with progressive delays:Conditional Sequences
Create sequences that adapt based on recipient behavior:Advanced Scheduling Features
Smart Retry Logic
Implement intelligent retry mechanisms for failed deliveries:Load Balancing
Distribute message load across time to avoid overwhelming iOS Shortcuts:Seasonal Adjustments
Automatically adjust scheduling for holidays and special events:Monitoring and Analytics
Scheduling Performance Metrics
Delivery Timing
- On-Time Delivery Rate: % of messages sent at scheduled time
- Average Delay: Difference between scheduled and actual send time
- Queue Processing Time: Time spent in processing queue
- Peak Load Handling: Performance during high-volume periods
Engagement Impact
- Response Rate by Send Time: Correlation between timing and responses
- Optimal Time Accuracy: How well predictions match actual performance
- Timezone Effectiveness: Response rates across different timezones
- Sequence Completion Rates: How many recipients complete sequences
Real-Time Monitoring
Best Practices
Scheduling Strategy
Respect Preferences
- Honor recipient timezone preferences
- Avoid known blackout periods
- Implement frequency capping
- Provide opt-out options for scheduling
Test and Optimize
- A/B test different send times
- Monitor engagement patterns
- Adjust based on performance data
- Track seasonal variations
Technical Reliability
- Implement robust retry logic
- Monitor queue health
- Handle timezone edge cases
- Plan for system maintenance
User Experience
- Provide clear expectations
- Allow schedule modifications
- Show delivery status
- Enable emergency overrides
Common Pitfalls to Avoid
Timezone Confusion
Timezone Confusion
Problem: Messages sent at wrong local times
Solution: Always store and display times in recipient’s timezone
Sequence Interruption
Sequence Interruption
Problem: Sequences continue after recipient responds
Solution: Implement response monitoring and sequence halting
Overloading iOS Shortcuts
Overloading iOS Shortcuts
Problem: Too many messages scheduled simultaneously
Solution: Implement load balancing and rate limiting