Nobody Is Following Up on Your Form Leads. Automate It.
The fastest way to automate form submission follow-up on WordPress is to connect your form plugin to Krom Automation, set the form submission as a trigger, and build a sequence of actions that run automatically every time someone fills out a form. You can do this without touching a line of code, and the free version covers the core setup for any major form plugin.
Most sites stop at a single confirmation email. The lead comes in, an autoresponder fires, and then nothing happens until someone checks the inbox manually, which might be tomorrow, might be next week.
Studies on lead response consistently show that replying within the first few minutes produces dramatically higher conversion rates than replying hours later. Manual follow-up cannot win that race reliably.
This guide covers five automation actions worth building after any form submission, explains how to branch the sequence based on real engagement signals, and links to the setup docs for the most common WordPress form plugins so you can build rather than just read.
Browse the full feature list for Krom Automation to see what triggers and actions are available before you start.
Why a Single Confirmation Email Is Not Enough
A confirmation email tells the person their message was received. It does not move the conversation forward, qualify the lead, or do anything that actually helps your business. For contact forms, quote requests, and lead magnets, that first email is the floor, not the ceiling.
The real problem is what happens at Day 3 and Day 7. If someone filled out your contact form on Monday and has not heard from you by Thursday, they have already contacted two of your competitors. No single-email autoresponder addresses this because there is no logic after the first send.
A confirmation email tells the person their message was received. It does not tell them why they should wait for your reply instead of moving on.
Competitors ranked for this topic focus on that first triggered email: set the form submission as the trigger, add a send email action, done. That is useful for day zero. It does not solve the follow-up problem at all.
Which Form Plugins Work With This Approach
Krom Automation integrates natively with all of the major WordPress form plugins. Each integration page shows the exact trigger to select and the fields that become available as merge tags in your follow-up emails.
- Gravity Forms: field-level merge tags, conditional entry routing, payment form support
- WPForms: submission trigger with full entry data, works on both free and Pro forms
- Contact Form 7: submission trigger, full field access including file uploads
- Fluent Forms: submission trigger plus step form support for multi-page forms
- Elementor Forms: native trigger inside Elementor Pro, no extra plugin required
- Ninja Forms: submission trigger with full field mapping
If you are not sure which form plugin fits your workflow setup best, our guide to the best WordPress form plugins for automated workflows compares the options with automation in mind.
The Five Things Worth Automating After Any Submission
Work through these in order. The first two run at the moment of submission.
The next three require delays and branching, which is where most setups stop short. Skipping ahead to step four without step two configured means you will send follow-up emails to people who never got a confirmation.
1. Immediate Confirmation Email with Personalised Content
This is the baseline. The trigger fires the moment the form is submitted, and the first action sends a confirmation email. The key detail is using merge tags to pull the submitter’s name, the specific answers they gave, and any relevant next steps into the email body.
A generic “Thanks for your message, we’ll be in touch” is better than nothing, but it is not personalised. If someone selected “Enterprise” from a pricing tier dropdown on your contact form, your confirmation email should acknowledge that. Merge tags make this a one-time configuration, not a manual task per submission.
- Use
{{form.field_name}}style tags to pull specific answers into the subject line - Match the tone of the confirmation to the form type: a quote request gets a different email than a newsletter signup
- If you have a visual email builder available (Krom Automation Pro includes one), design a template once and reuse it across forms
- Set the From name to a real person, not “noreply”, since replies to automated emails are signals worth capturing
2. CRM Contact Creation or Tag Application
Every form submission should create or update a CRM record automatically. Doing this manually means some contacts never get created, field data gets mistyped, and your CRM is always slightly wrong. Automating it means the record exists within seconds of submission, with every field mapped correctly.
Krom Automation connects to the major CRM and email marketing platforms that WordPress sites actually use:
- FluentCRM for self-hosted contact management with tags and lists
- ActiveCampaign for contact creation, tagging, and list assignment
- Mailchimp for subscriber creation and audience segmentation
- ConvertKit for subscriber tagging and sequence enrollment
- MailerLite for group assignment and subscriber creation
The practical benefit is that your sales or support team opens the CRM and the contact already exists, tagged with the form they submitted and the answers they gave. No copy-pasting from email threads.
If your CRM contact only gets created when someone on the team remembers to create it, your CRM is not a system of record. It is a partial list of the people you happened to notice.
3. Internal Team Notification with Routing Logic
Sending every form submission to the same inbox is a problem at scale. A contact form submission asking about enterprise pricing should reach a different person than one asking about a refund. Conditional branching in Krom Automation lets you read the value of a specific form field and route the notification accordingly.
This is not just about email. You can send a Slack message to the sales channel for high-value leads and an email to support for billing queries. The messaging integrations for Slack, Discord, Twilio and Telegram are all available in Pro, and each one supports merge tags so the notification contains the actual submission data, not just an alert to go check the inbox.
4. Time-Delayed Follow-Up Sequence
This is where the gap in every competing guide appears. Sending one confirmation email and treating the job as done leaves real revenue on the table.
A lead who did not reply to the first email is not necessarily uninterested. They may have been busy, may have read it on mobile and forgotten to reply, or may need one more prompt.
The sequence structure that works for most contact and quote forms looks like this:
- Day 0: Immediate confirmation with personalised content (step 1 above)
- Day 3: A short follow-up that adds value rather than just asking if they received the first email. A relevant resource, a case study, a specific question about their situation.
- Day 7: A final nudge that explicitly closes the loop. Something like “I’ll assume you found what you needed, but if you’d still like to talk, here’s how to book time.”
Delays and scheduling in Krom Automation let you postpone any action by minutes, hours, days, or weeks. Each delay node sits on the canvas between the previous action and the next one. You set it once and the sequence runs automatically for every submission from that point forward.
The critical detail most guides miss: delays in Krom Automation run via Action Scheduler in the background, so a delayed email fires when it is supposed to, not during a page load and not dependent on someone being logged in. On low-traffic sites, configure a real server cron to ensure WordPress Cron fires on schedule rather than waiting for a visitor to trigger it.
5. Branch the Sequence on Whether Someone Replied
A Day 3 follow-up email sent to someone who already booked a call is annoying at best and actively harmful to the relationship at worst. The full solution requires branching based on an engagement signal: did this person take the action you wanted, or not?
There are two practical approaches depending on your setup:
- Tag-based suppression: When someone books, fills out a second form, or completes any action that signals conversion, apply a tag or update a custom field. Build your follow-up sequence to check for that tag using a condition node before sending each delayed email. If the tag exists, the workflow exits without sending.
- Webhook-based signal: If your booking tool or CRM fires a webhook when someone converts, the incoming webhook receiver in Krom Automation Pro can catch that signal and update the contact’s status in WordPress, which your follow-up workflow then checks before proceeding.
This is not a simple setup, but it is the difference between an automated sequence that helps and one that damages relationships by ignoring the reality of what the person did.
What Each Approach Costs You in Time and Money
The table below compares the realistic time cost of manual follow-up against a configured automation, and what each option costs over 12 months at different submission volumes.
| Scenario | Manual follow-up | Krom Automation (free) | Krom Automation Pro |
|---|---|---|---|
| 50 submissions per month | ~4 hours/month at $50/hr = $2,400/yr | $0/yr after ~2 hours setup | $119/yr (Basic, 1 site) |
| 200 submissions per month | ~15 hours/month = $9,000/yr | $0/yr, no run caps | $119/yr (Basic, 1 site) |
| Multi-site agency (5 sites) | Scales linearly with headcount | $0/yr per site, unlimited runs | $199/yr (Standard, 5 sites) |
| Delayed sequence (3 emails) | Requires a human to remember | Not available (Pro feature) | Included, runs automatically |
| Branch on conversion signal | Manual CRM check before each send | Conditions available free | Webhook receiver + conditions |
The free version handles steps 1 through 3 with no time limits, no run caps, and no feature locked behind a paywall. The delayed sequence and webhook-based branching in steps 4 and 5 require Pro, which starts at $119 per year for a single site.
How to Personalise Follow-Ups Based on Form Answers
Personalisation at scale means the follow-up email reads as if it was written for that specific person, not for a generic contact. The mechanism is merge tags: variables that pull live data from the form submission into the email at send time.
Every field in every supported form becomes available as a merge tag once the integration is connected. A form with a “Service interested in” dropdown produces a tag you can use in the subject line, the opening paragraph, and the CTA. A form with a budget field produces a tag you can use to route the notification to the right team member.
- Subject line: “Following up on your [Service] enquiry, [First Name]” converts at higher rates than a generic subject
- Body copy: Referencing the specific answer someone gave shows the email was not just auto-sent to a list
- Conditional content: Using branching, you can show an entirely different paragraph based on which option was selected, not just swap a field value
- CTA: Pointing to a resource relevant to the specific answer rather than a generic homepage link
The full merge tags reference documents every tag format and shows examples for each field type, including checkboxes, multi-selects, and file upload fields.
Personalisation is not about using someone’s first name. It is about proving, in the body of the email, that you read what they actually wrote.
Should You Use a Native Plugin or a SaaS Tool Like Zapier?
This question comes up often, and the honest answer depends on where your data can live and what your ongoing budget looks like.
| Decision factor | Krom Automation (self-hosted) | Zapier or similar SaaS |
|---|---|---|
| Where form data is processed | Your own server, never leaves your database | Third-party servers in the US or EU |
| Pricing model | Flat annual fee, no per-task charges | Per-task or per-zap pricing, scales with volume |
| Cost at 200 tasks/day | $119/yr regardless of volume | Zapier Starter is $29.99/mo; Professional is $73.50/mo at that volume |
| WordPress-native triggers | 16 free triggers built for WordPress events | Requires a form plugin that supports Zapier webhooks |
| Execution logs | Full per-step audit trail, stored on your server | Log retention varies by plan, typically 7 to 30 days |
| AI actions | Included free, bring your own API key | Requires separate Zapier AI add-on or external step |
For WordPress sites with GDPR obligations, processing form submission data through a third-party SaaS tool adds a data processor relationship that needs to be documented. Self-hosted automation removes that complexity because the data never leaves your server. Our guide on self-hosted versus SaaS automation and data privacy covers this in detail.
Using AI to Write Personalised Follow-Up Emails Automatically
Krom Automation includes three AI actions in the free version: AI Generate Text, AI Content Moderation, and AI Auto-Tag. The AI Generate Text action is the relevant one here. It lets you pass form field values into a prompt and receive a generated email draft as output, which then becomes the body of the Send Email action.
The practical setup looks like this: the trigger fires on form submission, a condition node checks the value of a key field, the AI Generate Text action receives the relevant form fields as merge tags in the prompt, and the generated text flows into the email action. Every submission produces an email written specifically for that person’s answers, not a template with a name swapped in.
- Supported providers: OpenAI GPT-4o and GPT-4o Mini, Google Gemini 2.0 Flash, Gemini 2.5 Flash Preview, Gemini 2.5 Pro Preview, Groq Llama 3.3 70B and Llama 3.1 8B
- You bring your own API key and pay your AI provider directly at standard rates. wpRigel does not charge per AI call and does not mark up tokens.
- The AI Content Moderation action can screen incoming form data before any follow-up is sent, flagging submissions that contain inappropriate content before a team member needs to read them
Our post on AI WordPress automation covers what this approach actually achieves in practice and where the limits are.
Hidden Costs and Honest Limitations
No automation tool is the right answer for every situation. Here is what the marketing pages tend to leave out.
- Delays depend on WordPress Cron. On very low traffic sites where no visitors arrive for hours, WP-Cron fires late. Configure a real server cron job if your follow-up timing matters at the minute level.
- AI actions require your own API key. There is no built-in AI credit pool. You set up an account with OpenAI, Gemini, or Groq and pay them directly. For most sites with moderate form volume, the cost is under $5 per month.
- Branch-on-reply logic requires Pro and some setup thinking. The free version has conditions, but the webhook receiver that catches external conversion signals is a Pro feature. Budget 2 to 3 hours for a properly branched sequence.
- Krom Automation is WordPress-native. If your form and your follow-up destination both live outside WordPress entirely, this is not the right tool. The trigger or the action generally needs to touch your WordPress site.
- Email deliverability is not included. Krom Automation sends emails via WordPress’s standard mail function. For high volume or business-critical follow-ups, route through an SMTP provider such as Postmark, SendGrid, or Mailgun to avoid landing in spam.
Also from wpRigel
Pollify is wpRigel’s Gutenberg-native poll, survey, and quiz plugin. Polls are built as real blocks inside the editor, so there are no shortcodes to paste and no separate interface to configure. If you want to add a short survey to a landing page alongside a contact form, Pollify handles it natively in the block editor.
Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K from anywhere in the admin or frontend, type what you want, and act without clicking through menus. It is the only command palette with genuine WooCommerce order, product, and customer commands, so you can search an order by number, update a status, or email a customer without navigating away from what you were doing.
Our Verdict: Who Should Build This and Who Should Wait
Build it now if your site receives more than 20 form submissions per month and someone is currently reading each one and deciding whether to reply. At 20 submissions per month, a 3-email sequence across a 7-day window is 60 emails you are currently writing or forgetting to write. That is the wrong use of any person’s time.
Start with the free version if your main goal is an immediate personalised confirmation and CRM contact creation. Both are free, both work across all the major form plugins, and both require no developer. Download Krom Automation from the WordPress.org plugin directory and follow the getting-started guide.
Upgrade to Pro if you need the delayed sequence, the visual email builder, or the webhook-based branching on conversion signals. Pro starts at $119 per year for a single site, covers unlimited workflow runs, and carries a 14-day money-back guarantee. At 50 form submissions per month, it pays for itself in the time saved inside the first two weeks.
Wait or look elsewhere if your automation needs involve two external services with no WordPress involvement, or if you already have hundreds of workflows running in a SaaS platform and migration cost outweighs the per-task savings.
Compare all Krom Automation plans and pricing to find the right fit for your site count and budget.
Frequently Asked Questions
Does the free version of Krom Automation support form submission triggers?
Yes. The free version integrates with all the major WordPress form plugins including Gravity Forms, WPForms, Contact Form 7, Fluent Forms, Elementor Forms, and Ninja Forms. The submission trigger, send email action, merge tags, and conditional branching are all available at no cost.
Can I send different follow-up emails depending on which option a user selected?
Yes, using conditional branching. Each branch checks the value of a specific form field and routes the workflow down a Yes or No path. Each path can have its own email action with completely different content, not just a different merge tag value.
How do I stop sending follow-up emails to someone who already replied or booked?
The most reliable method is tag-based suppression: when a conversion event occurs, apply a tag to the contact record. Each delayed email action in the sequence checks for that tag using a condition node before sending.
If the tag exists, the workflow exits without firing. In Krom Automation Pro, the incoming webhook receiver can also catch external signals from booking tools or CRMs to trigger the tag update automatically.
Will automated follow-up emails go to spam?
Deliverability depends on your sending infrastructure, not the automation plugin. Route outgoing mail through a dedicated SMTP service such as Postmark, SendGrid, or Mailgun.
Also ensure your domain has SPF, DKIM, and DMARC records configured correctly. Krom Automation sends via WordPress’s standard mail function, so deliverability is entirely within your control.
How long does it take to set up a three-email follow-up sequence?
A basic sequence with an immediate email, a Day 3 follow-up, and a Day 7 close takes roughly 90 minutes to configure from scratch, including connecting the form plugin and writing the email copy. Adding branching logic for conversion suppression adds another 60 to 90 minutes. The step-by-step workflow guide covers the full build process.