Skip to content
  • There are no suggestions because the search field is empty.

How Scheduling Works in Telerivet

Scheduling in Telerivet lets you automate when messages go out so your communication stays consistent, timely, and aligned with your goals. Whether you are running a one-time announcement, a recurring reminder, or a multi-step journey, scheduling ensures your messages reach people at the right moment without manual effort.

This article explains the core concepts behind scheduling in Telerivet and how it behaves across different features.


Why Scheduling Matters

Many communication programs rely on timing. Your audience expects reminders, confirmations, and updates that align with their daily routines. Scheduling helps you:

  • Plan messages in advance
  • Reduce manual work and operational overhead
  • Keep communication consistent across regions
  • Protect delivery quality by avoiding message spikes
  • Coordinate campaigns, alerts, and automations without constant monitoring

Scheduling is foundational to campaigns, journeys, and automated services. It allows Telerivet to blend human planning with automated execution at any scale.


Where Scheduling Lives in Telerivet

Scheduling appears across several parts of the platform, each using the same underlying engine while adapting to the workflow.

Scheduled Broadcasts

Broadcasts can be sent immediately or scheduled for later. When scheduling, you choose the date, time, and timezone. This works well for one-time announcements, emergency alerts, or planned outreach.

See:Sending and Scheduling Messages

Campaign Scheduling

Campaigns help you run structured and repeatable communication programs. A campaign message may be:

  • A one-time broadcast
  • A sequence delivered over several days
  • A schedule tied to each contact’s enrollment date
  • A trigger-based journey supported by delays

Campaign scheduling allows your message flow to match your audience’s lifecycle.

See:Creating Campaigns

Time-Based Triggers in Automated Services

Automated Services can run based on time, not only when users send messages. Time-based triggers allow you to set:

  • Daily or weekly jobs
  • Hourly or interval-based tasks
  • Scheduled events inside custom logic

This helps you run recurring processes such as daily syncs, timed reminders, or automated data checks.

Delays in Flows and Journeys

Delays help shape the pacing of your flows. You can set:

  • Wait times between messages
  • Follow up reminders
  • Drip sequences over multiple days

Delays use the same scheduling engine and allow each participant to receive messages based on their own interactions.

How the Scheduling Engine Works

Telerivet’s scheduling engine follows a few core principles.

Local Timezone Awareness

Every schedule uses your project’s timezone. For organizations operating in multiple countries, each project can use a different timezone so message delivery remains aligned with local hours.

Smart Queueing

Scheduled messages enter a delivery queue. Telerivet manages routing, throughput, and carrier rate limits based on your selected channel such as SMS, WhatsApp, Viber, or BYOC. This helps maintain delivery stability during high-volume periods.

Reliability and Recovery

If a route is temporarily unavailable at the scheduled time, Telerivet automatically retries delivery and failover. Campaigns and automation continue running when connectivity returns. This reduces manual intervention and helps large-scale programs operate smoothly.

Quiet Hours and Overrides

Quiet Hours help you prevent sending non-essential messages  during sensitive times such as late nights or restricted windows. When needed, you can override Quiet Hours for transactional or operational messages that require immediate delivery. This gives you flexibility while remaining compliant with communication guidelines.

Best Practices for Scheduling

To get the most value from scheduled messaging:

  • Align send times with audience behavior
  • Avoid sending large volumes during carrier peak hours
  • Use delays rather than fixed times when designing automated journeys
  • Test with smaller audiences before scaling
  • Review project timezone settings regularly
  • Combine scheduling with segmentation for more relevant targeting