=== InboxMend – Form Submission Inbox & Email Log ===
Contributors: phpner
Tags: contact forms, form submissions, email log, form entries, smtp
Requires at least: 6.0
Tested up to: 7.0
Requires PHP: 7.4
Stable tag: 1.1.3
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Save WordPress form submissions first, then review Email Health, Email Log, SMTP events and auto-replies in one inbox.

== Description ==

InboxMend is a local-first WordPress form submission inbox and Email Log plugin. It saves form entries inside your WordPress dashboard first, then helps you review related Email Health and Email Log events.

Many WordPress contact forms rely only on notification emails. If a notification email fails, is blocked, is misconfigured, or is never generated, the website owner may lose the enquiry without knowing it.

InboxMend reduces that risk by storing form submissions in WordPress before email delivery becomes a problem. You can review saved leads, check Email Health, view the Email Log, configure SMTP sending, send visitor auto-replies, and optionally connect InboxMend Cloud for multi-site monitoring.

Use InboxMend with built-in lead forms, or keep using supported form plugins such as Contact Form 7, WPForms, Fluent Forms, Forminator and Ninja Forms.

Gravity Forms compatibility is planned.

Learn more at [InboxMend.com](https://inboxmend.com/).

= Save form submissions before notification emails fail =

A visitor can submit a contact form, but the notification email might not arrive.

This can happen because of SMTP issues, incorrect sender settings, hosting mail restrictions, plugin conflicts, spam filtering, or a form that did not generate an email event.

InboxMend is built around a simple idea: the form submission should be saved first, so the lead is not lost just because the email notification failed.

= One workflow instead of separate plugins =

Many WordPress sites use one plugin for forms, another plugin for saving entries, another plugin for SMTP, and another plugin for email logs.

InboxMend brings the form submission workflow together: save the lead first, review related email activity, manage basic follow-up, and keep everything visible inside WordPress.

= What you can do with InboxMend =

With InboxMend you can:

* Save WordPress form submissions in a local inbox.
* Capture entries from supported form plugins.
* Review leads, submitted fields, source forms, and lead details.
* Search, filter, and export saved submissions to CSV.
* Check Email Health for generated, failed, missing, or unknown notification events.
* View WordPress email events in the Email Log.
* Configure SMTP sending for WordPress notification emails.
* Create simple built-in lead forms and publish them with shortcodes.
* Send visitor auto-replies with reusable templates and form rules.
* Protect built-in forms with Google reCAPTCHA v3.
* Configure retention and privacy settings.
* Optionally connect InboxMend Cloud for multi-site visibility and monitoring.

= Works with popular form plugins =

You do not have to replace your existing form plugin.

InboxMend can capture submissions from supported form plugins and show them in one lead inbox.

Currently supported integrations include:

* Contact Form 7
* WPForms
* Fluent Forms
* Forminator
* Ninja Forms

Planned integration:

* Gravity Forms

When a supported integration is enabled and the related form plugin is active, InboxMend can store captured submissions and help you review related email activity.

= Built-in lead forms =

InboxMend includes simple built-in forms for common lead capture use cases.

You can create a form, configure its fields, copy the shortcode, and place it on a page. Submissions are saved in the Inbox, and related notification email activity can be reviewed from the Email Health and Email Log screens.

Built-in forms are useful when you need a simple contact form, enquiry form, callback request, service request, or basic lead capture form without installing a larger form builder.

= Email Health and Email Log =

InboxMend helps explain what happened after a form submission.

The Email Health dashboard groups related email activity into clearer statuses, such as:

* Sent by WordPress
* Failed
* No email generated
* Unknown

This makes it easier to find leads where the submission was saved, but the related notification email may not have worked as expected.

The Email Log helps site owners and admins review WordPress email events and sending attempts, including form notifications, WordPress system emails, and other email events generated through WordPress.

= SMTP sending settings =

InboxMend includes SMTP settings for WordPress notification emails.

You can configure SMTP host, port, encryption, authentication, username, password, From email, and From name.

Using SMTP can help avoid common hosting mail issues where WordPress tries to send email through the default PHP mail function.

InboxMend logs WordPress email events and sending attempts, but it does not guarantee inbox delivery.

= Visitor auto-replies =

InboxMend includes visitor auto-reply templates and rules.

You can create reusable auto-reply templates and connect them to specific forms and visitor email fields.

This is useful when you want visitors to receive a confirmation email after submitting a form, while still keeping the original lead saved in your WordPress dashboard.

= Google reCAPTCHA v3 for built-in forms =

Built-in forms can be protected with Google reCAPTCHA v3.

This helps reduce automated spam submissions while keeping the form experience simple for real visitors.

= Optional InboxMend Cloud sync =

InboxMend can optionally connect to InboxMend Cloud at [https://inboxmend.com/](https://inboxmend.com/) when you want visibility across one or many connected WordPress sites.

Cloud sync is designed for agencies, freelancers, WordPress admins, and teams that need a wider operational view across sites. Depending on the selected sync mode, Cloud can help monitor connection health, polling freshness, saved submission activity, Email Health signals, Email Log status, and issue trends.

Cloud sync is optional. The plugin can still save submissions, review leads, and show Email Health inside WordPress without connecting to InboxMend Cloud.

= Best for =

InboxMend is useful for:

* Small business websites that rely on contact forms.
* Agencies managing client WordPress sites.
* Site owners who do not want to lose enquiries.
* WordPress admins who need saved form submissions.
* Freelancers who want a simple lead inbox for client sites.
* Websites that need basic form storage without a full CRM.
* Sites where email notification problems need to be easier to review.

= Privacy and data control =

InboxMend stores form submissions inside your WordPress database.

You control your own data from your WordPress admin area. The plugin also includes CSV export, retention, and privacy settings to help manage saved submissions responsibly.

= External services =

InboxMend can connect to InboxMend Cloud when Cloud Sync is enabled in the plugin settings.

Service URL: [https://inboxmend.com/](https://inboxmend.com/)
Privacy Policy: [https://inboxmend.com/privacy](https://inboxmend.com/privacy)
Terms of Service: [https://inboxmend.com/terms](https://inboxmend.com/terms)

Cloud Sync is used to connect this WordPress site to an InboxMend Cloud site record, check connection health, and synchronize selected operational data according to the configured sync mode.

Depending on the selected sync mode and consent settings, the plugin may send site identity, site URL, plugin version, WordPress version, PHP version, connection status, Email Health summaries, Email Log status, lead summaries, and, only when Full lead data is explicitly enabled, lead details such as names, email addresses, phone numbers, message text, source URLs, workflow status, notes, and submitted fields. Sensitive fields are redacted before Cloud sync.

Cloud Sync requests are sent to InboxMend Cloud API endpoints under `https://inboxmend.com/api/v1/plugin`. Protected requests use a site token issued during the connection flow.

Cloud Sync is optional and can be disconnected from the plugin settings.

= What InboxMend does not do =

InboxMend does not guarantee that an email reached the recipient's inbox.

It also does not confirm whether a recipient opened or read an email.

The plugin logs WordPress email events and sending attempts, so you can see whether an email was generated, sent by WordPress, failed, not generated, or unknown.

== Installation ==

1. Upload the plugin folder to `/wp-content/plugins/`.
2. Activate InboxMend from the WordPress Plugins screen.
3. Open InboxMend in the WordPress admin menu.
4. Optional: configure Settings -> Sending if you want to use SMTP.
5. Create a form, copy its shortcode, and publish it on a page, or enable one of the supported form plugin integrations.

== Frequently Asked Questions ==

= Will submissions be saved if email notifications fail? =

Yes. InboxMend is built around saving form submissions in your WordPress dashboard, so leads can remain available even when a related notification email fails or is not generated.

= Does InboxMend work without Cloud? =

Yes. InboxMend works locally by default. You can save submissions, review leads, use Email Health, and view the Email Log inside WordPress without connecting to InboxMend Cloud.

= Does InboxMend guarantee email delivery? =

No. InboxMend logs WordPress email events and sending attempts, but it cannot guarantee inbox delivery, confirm that a recipient received an email, or confirm that a recipient opened or read an email.

= Which form plugins are supported? =

Supported integrations include Contact Form 7, WPForms, Fluent Forms, Forminator and Ninja Forms. InboxMend also includes built-in lead forms.

= Is Gravity Forms supported? =

Gravity Forms compatibility is planned, but it is not available in the current plugin build.

= Does InboxMend replace Contact Form 7 / WPForms / Fluent Forms? =

No. InboxMend can capture submissions from supported form plugins and show them in a lead inbox. You can keep using Contact Form 7, WPForms, Fluent Forms, Forminator or Ninja Forms when the related integration is enabled and the form plugin is active.

= Where are submissions stored? =

Submissions are stored in your WordPress database first. The local WordPress inbox remains available without Cloud. Cloud Sync is optional and sends selected operational data only when you enable it.

= What does "Sent by WordPress" mean? =

"Sent by WordPress" means WordPress reported that it attempted to send the related notification email successfully. It does not prove inbox placement, recipient delivery, or that the email was opened or read.

= Can I use my own SMTP settings? =

Yes. InboxMend includes SMTP sending settings for WordPress notification emails, including host, port, encryption, authentication, from name, and from email.

= Can I export submissions? =

Yes. Saved leads can be exported as CSV from InboxMend.

= What data is sent to InboxMend Cloud? =

Only when Cloud Sync is enabled. Depending on the selected sync mode, InboxMend may send site identity, site URL, plugin and WordPress version, connection health, Email Health summaries, Email Log status, lead summaries, and, only with explicit Full lead data consent, lead details. Sensitive fields are redacted before Cloud sync.

= Does it support auto-replies? =

Yes. You can create reusable visitor auto-reply templates and connect them to specific forms and visitor email fields with auto-reply rules.

= Does it store sensitive SMTP passwords safely? =

SMTP passwords and sensitive technical data should not be exposed in admin logs or Email Health screens.

= Can I create forms with this plugin? =

Yes. The plugin includes built-in lead forms that can be published with a shortcode.

== Screenshots ==

1. Inbox dashboard with saved form submissions and lead details.
2. Forms overview with built-in forms and connected integrations.
3. Email Health dashboard showing generated, failed, and missing notification events.
4. Email Log with related WordPress email events.
5. Auto-reply rules for connecting forms, visitor email fields, and templates.
6. Visitor email templates for reusable auto-replies.
7. SMTP settings for WordPress notification emails.

== Upgrade Notice ==

= 1.1.3 =
InboxMend 1.1.3 improves Auto-replies by managing sending rules from the template editor and showing clearer admin notices.

== Changelog ==

= 1.1.3 =
* Moved Auto-reply sending settings into the template editor so each template can manage its attached forms in one place.
* Improved the Auto-replies admin flow with clearer labels, menu highlighting, editor headers, and template usage details.
* Added plugin-owned admin notices for Auto-replies and settings messages so success and error feedback remains visible after redirects.
* Improved Auto-reply sending rule layout and validation behavior, including clearer visitor email field selection.

= 1.1.2 =
* Improved the Inbox and Lead detail screen layouts for a clearer review workflow.
* Fixed required field handling so form fields can become optional when required validation is disabled.
* Added editing and deleting support for Internal notes.

= 1.1.1 =
* Improved the form editor inspector so selected elements show their default element styles instead of empty controls.
* Automatically switches the right panel to Inspector when an element is selected.
* Improved Layout inspector sync after resize, including Width and individual margin controls.

= 1.1.0 =
* Rebranded the visible plugin identity to InboxMend while keeping the existing WordPress.org slug and text domain.
* Added InboxMend.com links, Plugin URI, Author URI, and Cloud Sync external service disclosure.
* Added optional InboxMend Cloud polling support for connected sites.
* Added Cloud sync payloads for lead snapshots, Email Log snapshots, Email Health summaries, and source breakdowns.
* Aligned the plugin Cloud connection check with the InboxMend Cloud API by using the existing heartbeat endpoint.
* Improved Cloud Sync settings with a clearer status overview, data sharing controls, diagnostics section, and persistent action notices.
* Improved Cloud connection security by requiring HTTPS for non-local Cloud endpoints and signed protected Cloud API requests.
* Hardened Cloud sync data handling by defaulting to Lead summary mode, redacting sensitive submitted fields, and masking technical error secrets before sync.
* Renamed Email Status surfaces to Email Health in the admin experience.
* Refined the lead detail screen layout by moving secondary source, notes, and activity information out of the long right sidebar.
* Updated WordPress.org assets, screenshots, banners, and readme content to match the InboxMend branding and product positioning.
* Kept Cloud Sync optional; local Inbox, Email Health, Email Log, forms, SMTP, auto-replies, export, retention, and privacy settings continue to work without Cloud.

= 1.0.0 =
* Improved the WordPress.org readme description and short description.
* Added WPForms lead capture compatibility.
* Added Fluent Forms lead capture compatibility.
* Added Forminator lead capture compatibility.
* Added Ninja Forms lead capture compatibility.
* Added auto-reply rules so templates can be assigned to specific supported forms and visitor email fields.
* Added Google reCAPTCHA v3 protection for built-in forms.
* Improved the Auto-replies admin experience, including rule validation, clearer field-level errors, and better form state preservation after validation errors.
* Improved admin screen styling by splitting page-specific CSS for Inbox, Forms, Email, Settings, and Auto-replies.
* Improved Email Log and Email Health handling for supported form integrations.
* Removed email open and click tracking endpoints because engagement tracking is not included in this release.
* Confirmed compatibility with WordPress 7.0.

= 0.1.0 =
* Initial release.
* Added built-in lead forms.
* Added Inbox for saved form submissions.
* Added SMTP sending settings.
* Added Email Log.
* Added Email Health dashboard.
* Added visitor auto-reply templates.
* Added Contact Form 7 compatibility.
* Added CSV export, retention, and privacy settings.
