Gravity Forms Delayed Email Notifications
Schedule Sending Gravity Forms Email Notifications by Period-of-Time, Specific-Date, or Form-Field from the Moment of Submission
You already know how to make Gravity Forms send a notification the instant somebody hits submit. That is the easy half. The emails that actually do the work — the onboarding tip three days later, the review request a week after delivery, the “your quote expires Friday” nudge — are the ones you have to remember to send. So how do you send a follow-up email after a Gravity Forms submission without logging in every morning to write one by hand?
The short answer: you schedule it instead of sending it. Gravity Forms Delayed Email Notifications queues notification emails to go out at a fixed interval after submission, relative to a date your user picks on the form, or at an exact date and time chosen in the form.

Why a Confirmation Email Is Not a Follow-Up
A confirmation email proves the submission landed. It arrives while attention is high — and is forgotten by lunchtime. A follow-up arrives when the decision is still live but the memory has faded. Same form, same recipient, completely different job.
Where scheduled follow-ups earn their keep:
- Onboarding — step two of a welcome or setup flow, a day or two after a signup form.
- Education — one useful tip three days after someone requests a quote or downloads a guide.
- Reminders — a payment, document or appointment reminder tied to a date the customer selected.
- Social proof — a review request a week after an order or service is completed.
- Recovery — a nudge to people who started a form and left before finishing.
Sending these by hand does not scale, and it fails quietly — nobody tells you the day-7 review request never went out. Scheduling fixes that, because the queue remembers what you would forget.
How Delayed Notifications Work in Gravity Forms
Every notification in Gravity Forms is a normal notification — recipients, from address, subject, message, conditional logic. The plugin adds a Delay Notifications checkbox at the bottom of that configuration. Tick it, choose the period (minutes, hours, days, weeks, months or years), enter how many, and save. Instead of firing immediately, the email is queued with a future send time.
Queued emails are stored as scheduled tasks and processed by WordPress’ built-in WP-Cron, and there is no limit on notifications per form — so one entry can produce a receipt now, a tip on day three and a review request on day seven. Everything still waiting to go out is listed on the Delayed Notifications screen, which is also where you cancel an email that is no longer appropriate.
Step 1: Schedule a Follow-Up With a Fixed Delay
Start with the most common case: a set interval after submission. A review request seven days after an order form, for example.
- Open Forms → Settings → Notifications and add a notification, or duplicate the one you want to re-time.
- Fill in the To, From, Subject and Message fields exactly as you would for an instant email.
- Scroll to the bottom of the notification and tick Delay Notifications.
- Pick the period — Days — and enter the number: 7.
- Save, then submit a test entry. The email appears on the Delayed Notifications screen with its scheduled send time instead of arriving immediately.
Keep the confirmation and the follow-up as separate notifications with separate subject lines — a receipt and a day-7 review request should never share a template.
Step 2: Start the Clock From a Date Your Customer Picks
A fixed delay measures from the moment of submission — sometimes the wrong anchor. If a client books a service six weeks out, a reminder that counts from the booking is useless. Point the notification at a date field on your form instead and the delay counts from that date, before or after it.

Typical setups: a reminder two days before a booked appointment, pre-arrival instructions the day before an event, a balance-due email three days after a requested start date. The same date-field logic powers the sequence in our earlier post on automated appointment reminder emails with Gravity Forms.
Step 3: Send at the Exact Date and Time Your User Chose (Pro)
The Pro version adds dynamic date and time notifications. Add a Date field and a Time field, let the visitor choose 12 October at 3pm, and the notification can be scheduled for that exact moment — or a set interval before or after it. That turns a WordPress form into a lightweight scheduler for consultations, webinars and equipment pickups: customers schedule their own follow-up simply by filling in the form.
Build a Three-Email Follow-Up Sequence
One delayed email is useful. Three notifications on one form, each with its own interval, is a sequence. A structure that works for most service forms:
- Day 0 — receipt with expectations. Instant, no delay, no selling: here is what happens next and when.
- Day 3 — the value email. One tip, one link, one question that invites a reply.
- Day 7 — the ask. A review, a testimonial, or a reminder that the offer or quote expires.
Because notifications support conditional logic, you can route different follow-ups by what the entry contains — an annual-plan customer and a quote request get different day-3 emails. Delays can also be queued from a partial entry when the Gravity Forms Partial Entries add-on is active, which is how you follow up with people who never finished the form.

How Do You Check, Cancel, or Reschedule a Queued Follow-Up?
Open the Delayed Notifications screen to see every email that has not gone out yet, the entry it belongs to and its scheduled time. If a customer cancels or reschedules, cancel the queued email there and then — no more “see you tomorrow” emails to someone who cancelled last week.
How Accurate Are Scheduled Emails?
WordPress’ WP-Cron is not a real clock. It runs scheduled tasks when someone visits your site, so on a quiet site a “day 7” email can drift past its scheduled time. The fix is the one in the plugin documentation: a server-level cron job that runs every minute.
# server crontab: run due WP-Cron events every minute
* * * * * cd /var/www/example.com && wp cron event run --due-now --url=https://example.com --quietTwo more habits worth keeping: give the follow-up its own subject line so it does not read like a duplicate receipt, and monitor a plain-text send-to address so deliverability problems surface early.
Conclusion: Let the Queue Send the Follow-Ups
To send a follow-up email after a Gravity Forms submission, decide the anchor first — submission time, a date the customer picked, or an exact date and time — set the delay on the notification, and let the queue handle delivery. Two or three well-timed emails beat a generic newsletter every time, and you never have to remember them again.
Gravity Forms Delayed Email Notifications handles the scheduling, the queue view and the cancelling, from $69 a year. Full features and pricing are on the plugin page at ristrettoapps.com.
Keep reading: how to organize Google Drive folders for Gravity Forms file uploads.
Can Gravity Forms send an email days after a form is submitted?
Gravity Forms sends notifications immediately. The Delayed Email Notifications plugin adds a Delay Notifications option to each notification, so an email can be queued to send minutes, hours, days, weeks, months or years after the entry is submitted — with a different delay per notification.
How many follow-up emails can I schedule on one form?
There is no limit. One form can hold several notifications, each with its own delay, recipients, message and conditional logic, so a single submission can trigger a receipt plus a day-3 tip and a day-7 review request. Any queued email can be cancelled from the Delayed Notifications screen.
Does it work with Gravity Forms Partial Entries?
Yes. Scheduled notifications can be queued from a completed submission or, optionally, when a partial entry is created by the Gravity Forms Partial Entries add-on — which makes it possible to follow up with people who start a form and leave.
Why did my scheduled follow-up email arrive late?
Because WordPress’ WP-Cron runs scheduled tasks when the site receives traffic, so on a quiet site delayed notifications can slip past their scheduled time. A server-level cron job that runs every minute keeps deliveries as close to schedule as possible.
