Skip to main content

Scheduling & Recurrence

Most rules run the moment a matching email arrives. But some automations should only be live for a while — like a vacation auto-reply — or should run some time after an email lands. MailPrism handles both.

This page covers three related ideas:

  • Rule schedules — when a rule is allowed to run (a date range, or certain hours).
  • Auto-disable — turning a scheduled rule off automatically when its window ends.
  • Delayed actions — running an action later, not instantly.

Rule schedules​

A schedule limits when a rule is active. There are two kinds.

ScheduleWhat it doesUsed by
Date rangeThe rule is active between a start date and an end date (in your timezone)Vacation / out-of-office responders
Time-basedThe rule is active during — or outside — set hours on chosen days of the weekAfter-hours responders
Where schedules come from

You don't hand-build these schedules on a normal rule. MailPrism sets them up for you when you turn on an auto-responder — the Vacation responder creates a date-range schedule, and the After-hours responder creates a time-based schedule. You'll find these under Settings → Auto-Responder.

Date-range schedule (vacation)​

When you set a vacation responder's start and end dates, MailPrism only runs the auto-reply rule between those dates. Outside the window, the rule sits idle — no replies go out. Everything is evaluated in the timezone you choose, so "ends June 30" means the end of June 30 where you are.

Time-based schedule (after-hours)​

An after-hours responder is active outside your business hours. You set:

  • Business hours — a start time and end time (for example, 09:00–17:00).
  • Work days — which days those hours apply (for example, Monday–Friday).
  • Timezone — so the hours track your local clock.

The responder then replies only to mail that arrives outside those hours.

Auto-disable when the window ends​

A scheduled rule can turn itself off once its end date passes, instead of just going dormant. This keeps your Rules list honest: a finished vacation responder shows as disabled, not lingering as "on."

Why this matters

Auto-disable means you won't come back from vacation to find the responder quietly still armed. When the end date passes, the rule flips to off on its own.

Delayed actions​

Instead of scheduling the whole rule, you can delay a single action. In the rule editor, click the clock icon next to an action to add a delay.

The clock only appears on actions MailPrism can schedule — labels, read/unread, importance, archive, trash, stars, and Forward Email. Replies, drafts, notifications, unsubscribe, tracking actions, and nudge/reminder flows always run right away. The full list is in Actions → Which actions can be delayed.

A delayed action waits a set amount of time before it runs:

  • Wait a number of minutes, hours, days, weeks, or months.
  • Then run the action (apply a label, archive, forward, and so on).

Cancel if replied​

When you add a delay, you also get a "then…" option that can cancel the action if there's a reply before it runs:

Cancel if repliedThe delayed action is skipped when…
You replyyou respond in the thread first
The sender repliesthe other person responds first
Anyone replieseither side responds first

Example: Wait 3 days, then apply the label "Follow up" — but cancel it if anyone replies.

Following up on a quiet thread

To actually send a follow-up when nobody answers, use a nudge flow (the Start Nudge Flow action). Nudges wait between steps and stop on their own when the other person replies.

Recurring actions​

Not in the rule editor

Repeating an action on a cadence (daily, weekly, monthly) is only available through MailPrism's API — there's no recurrence control in the rule editor, and auto-responders don't use it. For repeating follow-ups, use a nudge flow.

Putting it together​

A vacation responder is the clearest example of all of these working as one:

  1. You pick start and end dates → a date-range schedule.
  2. The responder replies to matching mail for the whole window — the end date counts until the end of that day in the vacation's timezone.
  3. The responder's own short response delay spaces out the reply.
  4. When your end date passes, the rule auto-disables → auto-disable.

→ Learn the basics: Conditions · Actions · Best practices