Test mode

Payments use Stripe test mode. No real payment is collected.

Understand email delivery.

Start with WordPress mail in Free. Add SMTP, Resend or Mailtrap in Pro and review recipient-level provider evidence when tracking is configured.

How it works

Test the message and the route separately

Free includes one main notification, a sample email preview, a real test-email action and a staging test inbox. Accepted entries are stored before background notification sending begins.

  • A sample preview sends no email
  • Test delivery replaces real recipients with the chosen test inbox
  • Known sending failures and uncertain outcomes are recorded differently

Choose a dedicated form sender with Pro

Pro supports your SMTP server, the Resend API and the Mailtrap Email Sending API. The selected route handles form notifications, visitor receipts, replies and test emails; unrelated WordPress mail keeps its normal route.

  • Use your own provider account, credentials and verified sender
  • Add named conditional notifications, formatted messages and Bcc
  • Visitor receipts are limited and do not repeat submitted answers

Read delivery evidence for each recipient

Configured Resend and Mailtrap callbacks track new API emails per To, Cc and Bcc recipient. Delivery, delay, bounce, rejection and an unconfirmed outcome remain separate states.

  • Delivery tracking needs a public HTTPS callback and its signing secret
  • Delivered means the recipient mail server accepted the email, not inbox placement
  • Review the Email delivery history and Needs attention view

Use the missing-confirmation backup deliberately

When API tracking is configured and the WordPress retry is enabled, a scheduled check can send one backup after fifteen minutes without confirmation. It skips recipients with delivery, a known delay or a terminal event.

  • The original provider result and the WordPress retry remain separate
  • A missing callback can mean the first email arrived, so duplicates are possible
  • Background scheduling must run; the retry is not an exact wall-clock guarantee

Investigate a notification someone cannot find

Use the evidence in order rather than repeatedly sending the same form.

  1. Confirm the entry

    Find the stored response in WordPress. A missing email does not mean the accepted entry is missing.

  2. Inspect the sending attempt

    Check the selected route, recorded acceptance or failure, and provider reference when available.

  3. Check the recipient outcome

    With configured Pro tracking, review delivery events or an unconfirmed result. Inspect the real mailbox and provider logs as well.

An example workflow. Configure and test it in your own WordPress site.

Free and Pro for this workflow

Feature reference: Free 1.4.0 and Pro 1.3.2. Check published downloads for the version you can install.

Included in Free

  • A main notification using the site's WordPress mail setup
  • Sample previews, test email and staging recipient isolation
  • Background notifications, recorded attempts and bounded retries

With Pro

  • SMTP, Resend and Mailtrap Email Sending transports
  • Conditional notifications, receipts, formatting, Bcc and replies
  • Configured recipient tracking and an optional fifteen-minute backup
See the complete comparison

Plan your setup

  • No provider or plugin can promise inbox placement. Check the real mailbox as well as recorded acceptance.
  • SMTP fallback after a definite failure and the API missing-confirmation backup are different mechanisms. Each needs its own setup and testing.
  • Provider credentials, verification, callback delivery and WordPress scheduling are part of a working setup. They are not supplied by buying the plugin.
Follow the practical guide

Common questions

Does Free work with an existing WordPress SMTP plugin?

Free uses the site's normal WordPress mail route, which can already be configured by your host or another mail plugin.

Does the backup resend every unconfirmed email?

Only eligible new tracked API emails with a temporary retry copy and the retry setting enabled. Known recipient events can stop it; existing older records without a retry copy are not resent.

Browse all questions