Title: Neutrope Lead Desk for Contact Form 7
Author: Neutrope Inc.
Published: <strong>May 29, 2026</strong>
Last modified: October 26, 2026

---

Search plugins

![](https://ps.w.org/neutrope-lead-desk-for-contact-form-7/assets/banner-772x250.
png?rev=3664838)

![](https://ps.w.org/neutrope-lead-desk-for-contact-form-7/assets/icon-256x256.png?
rev=3553617)

# Neutrope Lead Desk for Contact Form 7

 By [Neutrope Inc.](https://profiles.wordpress.org/neutropeinc/)

[Download](https://downloads.wordpress.org/plugin/neutrope-lead-desk-for-contact-form-7.0.4.0.zip)

 * [Details](https://en-au.wordpress.org/plugins/neutrope-lead-desk-for-contact-form-7/#description)
 * [Reviews](https://en-au.wordpress.org/plugins/neutrope-lead-desk-for-contact-form-7/#reviews)
 *  [Installation](https://en-au.wordpress.org/plugins/neutrope-lead-desk-for-contact-form-7/#installation)
 * [Development](https://en-au.wordpress.org/plugins/neutrope-lead-desk-for-contact-form-7/#developers)

 [Support](https://wordpress.org/support/plugin/neutrope-lead-desk-for-contact-form-7/)

## Description

Neutrope Lead Desk for Contact Form 7 captures every Contact Form 7 submission into
a dedicated database table and provides a simple WordPress admin interface for managing
those submissions as leads.

The free version is intentionally focused: it saves submissions reliably, gives 
you an admin list/detail UI, lets you change status, add internal notes, and export
to CSV. It does this without pulling in external services, trackers, or upsell banners
on unrelated screens.

Version 0.3.0 is mainly a foundation release for add-ons: it adds documented, generic
extension points so other plugins can add columns, filters and detail-screen panels
without forking this one. Nothing in the plugin’s own behaviour changes because 
of them, and no database change is involved. See “Extending the plugin” below.

Since 0.2.0 each entry also keeps an **Activity Timeline** (対応履歴) so you can
see what has already been done about an inquiry — when it arrived, who changed its
status and to what, when notes were added, and when it was moved to trash, restored,
or marked as spam — instead of inferring the handling history from the current status
alone.

**Key features**

 * Automatic capture of every Contact Form 7 submission into a dedicated table (`{
   prefix}nldcf7_entries`)
 * The full submission payload is always stored as JSON, so nothing you asked users
   to type is lost
 * Mapped columns for name, email, phone, and company are extracted automatically
   using a configurable candidate list
 * Admin list screen with filtering by keyword, status, form, and date range, plus
   bulk actions (status change, trash, mark spam)
 * Trash is reversible: trashed entries stay in the database behind a Trash view
   with per-row and bulk Restore, so a mis-click is undone from the admin instead
   of from SQL
 * Detail screen with all submitted fields, submission metadata, status management,
   and internal team notes
 * Per-entry Activity Timeline on the detail screen, recording when the entry was
   received, every status change (from which status to which), internal-note activity,
   Trash and Restore, and spam-state changes — each with the acting user and a timestamp,
   newest first, paginated 50 events at a time
 * For entries captured before 0.2.0, the timeline is reconstructed from what the
   database actually recorded: the original received timestamp and your existing
   internal notes. Status, trash, and spam changes made before the upgrade were 
   never stored anywhere, so they are not invented — the timeline says so plainly
   rather than guessing
 * Your existing notes remain the authoritative record. The timeline links to them;
   it does not replace, rewrite, or duplicate them
 * CSV export (UTF-8 with BOM, CRLF) with date/status/form/spam filters — streamed
   in chunks for large datasets
 * Attachment metadata capture (file name, MIME type, size). The files themselves
   remain with Contact Form 7’s default handling
 * Privacy-friendly defaults: IP capture is OFF by default
 * Opt-in data deletion on uninstall (off by default so accidental deletes don’t
   nuke your leads)
 * Extensibility via action/filter hooks: `nldcf7_after_entry_saved`, `nldcf7_after_note_added`,`
   nldcf7_after_status_changed`, `nldcf7_after_entry_trashed`, `nldcf7_after_entry_restored`,`
   nldcf7_after_spam_changed`, `nldcf7_entry_data_before_insert`, `nldcf7_export_columns`,`
   nldcf7_export_row`, `nldcf7_statuses`, `nldcf7_event_labels`, `nldcf7_event_render`,`
   nldcf7_required_capability`
 * Since 0.3.0, nine further extension points let an add-on place panels on the 
   entry detail screen, add list columns and filter controls, keep its own filter
   state across list actions, and constrain the entries query — all documented under“
   Extending the plugin”

**Requirements**

 * WordPress 6.0 or later
 * PHP 7.4 or later
 * Contact Form 7 plugin installed and active

**Does NOT include (outside the scope of the free version)**

 * Sending external notifications (Slack, Chatwork, email digests)
 * Assignee / team routing
 * Auto-follow-up reminders
 * Analytics dashboards and reports beyond simple counters
 * Storing actual uploaded file contents (only metadata is captured)

These may be considered for a future Pro release. The free plugin is designed to
be fully useful on its own.

### Extending the plugin

Version 0.3.0 adds nine extension points for add-on developers. They are
 generic:
this plugin knows nothing about what an add-on stores. All of them are no-ops when
nothing is listening, so a site with no add-on behaves exactly as it did in 0.2.0.

#### nldcf7_entry_detail_main

Action. Introduced in 0.3.0. Fires on the entry detail screen after this
 plugin’s
own cards in the main column, before the column closes.

    ```
    do_action( 'nldcf7_entry_detail_main', array $entry )

    $entry is the entry row as stored, passed by value. The listener prints its
    ```

own markup, including its own card wrapper, and is responsible for escaping it.

Output is not buffered or altered.

#### nldcf7_entry_detail_sidebar

Action. Introduced in 0.3.0. The same contract, for the sidebar column. Two
 hooks
exist so an add-on can place content in both columns of one screen.

    ```
    do_action( 'nldcf7_entry_detail_sidebar', array $entry )
    ```

#### nldcf7_entry_list_columns

Filter. Introduced in 0.3.0. Adds columns to the entries list.

    ```
    apply_filters( 'nldcf7_entry_list_columns', array $columns )
    ```

Return the column map with your own keys appended; prefix them to avoid
 collisions.
Core columns cannot be removed, renamed or repurposed — every core key is restored
to its own label after the filter runs, and the checkbox column is forced back to
the front. Labels are plain text and are escaped on output.

#### nldcf7_entry_list_column_content

Filter. Introduced in 0.3.0. Renders a cell for a column you added.

    ```
    apply_filters( 'nldcf7_entry_list_column_content', string $html, string $column_name, array $item )
    ```

Return HTML for your own column, or the value you were given for anything else.

Escape your own output; the plugin then passes the result through wp_kses_post()
as a second layer, so ordinary post markup survives while scripts and event handlers
do not. A non-string return renders an empty cell.

#### nldcf7_entry_list_filters

Action. Introduced in 0.3.0. Fires inside the list’s existing GET filter form,
 
before the Filter button, so a plain select or input submits alongside the built-
in filters.

    ```
    do_action( 'nldcf7_entry_list_filters', array $current_args )

    $current_args is this plugin's own sanitized filter state, for reference. You
    ```

own your field names, your values and your escaping. No nonce is involved: the
 
filter bar only reads.

#### nldcf7_entry_list_carried_args

Filter. Introduced in 0.3.0. Keeps your own filter state across the All and
 Trash
views, the row actions, and the redirect after a row or bulk action.

    ```
    apply_filters( 'nldcf7_entry_list_carried_args', array $args, array $core )
    ```

Add your own already-sanitized scalar values. The plugin re-checks the result
 afterwards:
reserved keys (`page`, `paged`, `action`, `action2`, `entry_id`, _wpnonce, `_wp_http_referer`,`
view`, `event_page`, `status_view`) are stripped, keys are normalised, non-scalars
are dropped, and both value length and argument count are capped. Core values always
win. Do not attempt to forward the whole query string.

#### nldcf7_entry_query_args

Filter. Introduced in 0.3.0. Adjusts the entries query using arguments the
 repository
already understands, without writing SQL.

    ```
    apply_filters( 'nldcf7_entry_query_args', array $args )
    ```

The most useful is `ids`, an array of entry IDs to restrict the query to.
 $args[‘
context’] says who is asking: `list` for the entries screen, `export` for CSV, `
default` otherwise. Check it — both callers share the same repository, so an unconditional
constraint would also change what CSV exports.

#### nldcf7_entry_query_clauses

Filter. Introduced in 0.3.0. Constrains the entries query using a table of your

own, resolved by the database rather than by loading matching IDs into PHP.

    ```
    apply_filters( 'nldcf7_entry_query_clauses', array $parts, array $args )

    $parts has four keys:
    ```

 * `join` — a JOIN clause string.
 * `where` — an array of condition strings, each using `%s` or `%d` placeholders.
 * `prepare_args` — the values for those placeholders, in order.
 * `distinct` — boolean, default false.

Values must go in `prepare_args`, never inside the condition strings; the plugin

passes them to `$wpdb->prepare()`. A single pre-built SQL string is not accepted.
If the placeholder count and the value count disagree, the whole contribution is
discarded. Table and column identifiers inside `join` are your responsibility. Set`
distinct` when your JOIN can match a row more than once: it is applied to the row
query and the count together, so the list total and pagination stay correct. `$args['
context']` applies here too.

#### nldcf7_entry_list_items_prepared

Action. Introduced in 0.3.0. Fires once per list page after the rows are known
 
and before any cell is rendered.

    ```
    do_action( 'nldcf7_entry_list_items_prepared', array $items )

    $items is the current page's rows only -- never the whole result set. Use it
    ```

to load everything your columns need in one query and keep it in a
 request-local
cache, instead of querying once per cell. It is read-only, has no return value, 
and fires with an empty array when the page has no rows. It belongs to the entries
screen only and never fires during CSV export.

## Screenshots

[⌊Entry list with summary cards, filters, and bulk actions.⌉⌊Entry list with summary
cards, filters, and bulk actions.⌉[

Entry list with summary cards, filters, and bulk actions.

[⌊Detail view: submission fields, status management, internal notes.⌉⌊Detail view:
submission fields, status management, internal notes.⌉[

Detail view: submission fields, status management, internal notes.

[⌊Settings page: field mapping, capture toggles, uninstall behaviour.⌉⌊Settings 
page: field mapping, capture toggles, uninstall behaviour.⌉[

Settings page: field mapping, capture toggles, uninstall behaviour.

[⌊CSV export form.⌉⌊CSV export form.⌉[

CSV export form.

[⌊Help screen.⌉⌊Help screen.⌉[

Help screen.

## Installation

 1. Upload the `neutrope-lead-desk-for-contact-form-7` folder to the `/wp-content/plugins/`
    directory, or install it via the Plugins screen in WordPress (“Upload Plugin”).
 2. Ensure Contact Form 7 is installed and activated.
 3. Activate “Neutrope Lead Desk for Contact Form 7” from the Plugins screen.
 4. Review defaults at **お問い合わせ > 設定** (Contact > Settings). The plugin’s screens
    appear underneath the Contact Form 7 menu. In particular, verify the field mapping
    candidates match your form’s field names.
 5. Submit a test entry through one of your Contact Form 7 forms, then open **お問い合わせ
    > 一覧** to confirm it was captured.

## FAQ

### Does this work without Contact Form 7?

No. The plugin depends on Contact Form 7. If CF7 is not active, the plugin will 
not capture submissions and will show a warning banner on its own admin screens (
it does not nag elsewhere in wp-admin).

### Are uploaded files stored?

No — only metadata (file name, MIME type, file size). The actual files remain with
Contact Form 7’s default handling.

### Will this capture IP addresses?

IP capture is disabled by default for privacy. You can enable it under **お問い合わせ
> 設定 > IP 保存**. If you enable it, make sure your site’s privacy policy covers
IP logging.

### How do I export data to CSV?

Open **お問い合わせ > エクスポート**, apply any filters (date range, status, form,
include spam), and click the download button. The CSV is UTF-8 with BOM, so it opens
correctly in Japanese Excel without manual encoding conversion.

### How does field mapping work?

Each of the four mapped columns (name, email, phone, company) has a comma-separated
candidate list. The first field name that exists in the submission wins and its 
value is copied to the mapped column. Unmapped fields still end up in the `raw_payload_json`
column.

### Will deleting the plugin lose my captured leads?

No, by default data is preserved. If you explicitly want a clean uninstall, enable**
設定 > アンインストール時にデータ削除** first, then delete the plugin.

### Does the plugin send data to any external service?

No. Nothing is sent outside your WordPress installation. There is no phone-home,
no analytics, and no tracking.

### What capability is required?

By default `manage_options` is required for all admin screens. The required capability
can be changed via the `nldcf7_required_capability` filter.

### Can I add custom columns to the CSV export?

Yes. Use the `nldcf7_export_columns` filter to add/remove header columns, and `nldcf7_export_row`
to return custom values per row.

### Why is the activity history short for entries I received before updating?

Because it is built only from what was actually recorded at the time. Before 0.2.0
the plugin stored each entry’s received timestamp and your internal notes, but it
did not keep a log of status changes, trash/restore actions, or spam marking. Those
older transitions cannot be recovered, and the plugin will not fabricate them. Entries
received from 0.2.0 onward record the full set of activity as it happens.

### How do I report a bug or request a feature?

Please open an issue on the plugin’s support forum or the project’s issue tracker.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Neutrope Lead Desk for Contact Form 7” is open source software. The following people
have contributed to this plugin.

Contributors

 *   [ Neutrope Inc. ](https://profiles.wordpress.org/neutropeinc/)

“Neutrope Lead Desk for Contact Form 7” has been translated into 1 locale. Thank
you to [the translators](https://translate.wordpress.org/projects/wp-plugins/neutrope-lead-desk-for-contact-form-7/contributors)
for their contributions.

[Translate “Neutrope Lead Desk for Contact Form 7” into your language.](https://translate.wordpress.org/projects/wp-plugins/neutrope-lead-desk-for-contact-form-7)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/neutrope-lead-desk-for-contact-form-7/),
check out the [SVN repository](https://plugins.svn.wordpress.org/neutrope-lead-desk-for-contact-form-7/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/neutrope-lead-desk-for-contact-form-7/)
by [RSS](https://plugins.trac.wordpress.org/log/neutrope-lead-desk-for-contact-form-7/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 0.4.0

 * New: classify enquiries as Sales independently of workflow status, and filter
   the list by classification or quarantine.
 * New: explicitly block an exact sender email address. Future matching submissions
   are saved in quarantine before Contact Form 7 mail and mail_2 notifications are
   suppressed.
 * New: release individual enquiries and unblock senders separately. Neither action
   resends previous notifications; sales enquiries remain readable.
 * New: record classification, release and sender-rule changes in the Activity Timeline;
   include triage fields in CSV exports.
 * Compatibility: preserve existing Contact Form 7 spam decisions and integrate 
   quarantine with Lead Desk Pro 0.2.0 reply protection.
 * Safety: fail intake if a blocked submission cannot be safely stored. Other plugins’
   independent notification transports are outside this suppression scope.

#### 0.3.2

 * Fix: with Contact Form 7 6.2 or later, the Entries, Export, Settings and Help
   screens were missing from the admin menu. Contact Form 7 6.2 moved its top-level
   menu from `wpcf7` to `wpcf7-dashboard`; the screens now attach to whichever Contact
   Form 7 menu is registered, so earlier Contact Form 7 versions keep working as
   before. Screen URLs (`admin.php?page=nldcf7-*`), required capability, data and
   settings are unchanged.
 * Add: if Contact Form 7 is active but its admin menu cannot be found, a notice
   on the Dashboard and Plugins screens explains that the Lead Desk screens are 
   hidden. Submissions are still saved.

#### 0.3.1

 * Add: show a contextual Upgrade to Pro link on the Plugins screen when the Pro
   add-on is not active. The link points to the live purchase page and includes 
   product-specific campaign attribution. No data, settings, or front-end behavior
   changes.

#### 0.3.0

 * Add: generic extension points for the entry detail screen — `nldcf7_entry_detail_main`
   and `nldcf7_entry_detail_sidebar` — so an add-on can place panels in either column
   without modifying this plugin.
 * Add: generic list extension points — `nldcf7_entry_list_columns` for columns 
   and `nldcf7_entry_list_column_content` for their cells. Core columns are protected:
   an add-on cannot remove, rename or repurpose one, and returned cell markup passes
   through `wp_kses_post()`.
 * Add: `nldcf7_entry_list_filters`, which places an add-on’s own controls inside
   the existing filter bar.
 * Add: `nldcf7_entry_list_carried_args`, so an add-on’s own filter stays applied
   across the All and Trash views and after row and bulk actions. Reserved keys 
   such as nonces, action names and entry IDs are refused, non-scalar values are
   dropped, and size and count are capped, so a careless listener cannot put unsafe
   state into a list URL.
 * Add: `nldcf7_entry_query_args` for high-level query constraints, including the
   existing `ids` argument, and `nldcf7_entry_query_clauses` for constraints that
   live in an add-on’s own table. Clauses are structured — a JOIN, conditions with
   placeholders, and their values kept separate — rather than a raw SQL string, 
   and values always go through `$wpdb->prepare()`.
 * Add: optional `distinct` handling for add-on joins that can match a row more 
   than once. It is applied to the row query and the count together, so the list
   and its total can never disagree.
 * Add: query context. The entries screen and the CSV exporter share one repository,
   so each query now says which it is. An add-on constraint meant for the list no
   longer reaches CSV export unless the add-on opts in.
 * Add: `nldcf7_entry_list_items_prepared`, which hands an add-on the current page’s
   rows once, before any cell is rendered, so custom columns can load their data
   in a single query instead of one per cell.
 * Fix: the Activity preparation notice counted processing records (entries plus
   notes) but read as a number of inquiries. It now names the unit; the arithmetic
   is unchanged.
 * Fix: the “history from before this plugin was updated” note no longer appears
   on sites that installed this version fresh and therefore have no earlier history
   to explain.
 * No database change. The schema and database version (1.1.0) are identical to 
   0.2.0, no migration runs, and existing entries, notes, attachments, activity,
   settings, capabilities and URLs are untouched. With no add-on installed the plugin
   behaves exactly as 0.2.0 did.

#### 0.2.0

 * Add: an **Activity Timeline** (対応履歴) on the entry detail screen, showing 
   what has already been done about an inquiry. It records the entry being received,
   status changes (including the previous and new status), internal-note activity,
   Trash and Restore, and spam-state changes — each with the user who performed 
   it and a timestamp, newest first and paginated 50 events at a time.
 * Add: a dedicated activity-event table (`{prefix}nldcf7_entry_events`). The database
   version moves from 1.0.0 to 1.1.0; the table is created on upgrade and on fresh
   activation.
 * Add: existing entries get a historical timeline built in the background from 
   the two things the database already recorded — each entry’s received timestamp
   and its existing internal notes. The backfill runs in batches, is resumable, 
   and shows a progress notice on the plugin’s own screens while it works; you can
   keep using the plugin normally throughout.
 * Historical status changes, trash/restore actions, and spam marking are deliberately
   NOT inferred. Those transitions were never stored before this release, so the
   timeline shows what was genuinely recorded and explains the gap rather than reconstructing
   a plausible-looking history that never happened.
 * Your existing notes stay authoritative: the timeline links to them rather than
   copying or replacing them. Notes are also now rejected if their parent entry 
   does not exist, so an orphaned note can no longer appear in a timeline that belongs
   to nothing.
 * Fix: entry mutations are now transition-aware. Status, trash, restore, and spam
   changes distinguish a real transition from a no-op and from a failed write, so
   the timeline records a change only when the stored value actually changed. Previously
   a no-op update and a failed update were indistinguishable to callers.
 * Fix: the entries list now keeps your keyword, status, form, date range, spam 
   toggle, and sort order after a row or bulk action, instead of dropping you back
   into an unfiltered list after every single action.
 * Housekeeping: resolved the remaining Plugin Check warning (`WordPress.Security.
   ValidatedSanitizedInput.InputNotSanitized`) by restructuring how list-filter 
   input is read, not by suppressing the check. Plugin Check reports 0 errors and
   0 warnings.
 * No change to how submissions are captured or to what is stored for them: existing
   entries, notes, attachments, statuses, settings, option names, page slugs, capabilities,
   and existing hooks are all unchanged. Adds the actions `nldcf7_after_entry_trashed`,`
   nldcf7_after_entry_restored`, and `nldcf7_after_spam_changed`, and the filter`
   nldcf7_event_render`.

#### 0.1.5

 * Add: the entries list now has a **Trash** view alongside **All**, with a per-
   row “Restore” action and a “Restore” bulk action. Trashing an entry has always
   been a soft delete (an `is_deleted` flag, never a row deletion), but until now
   nothing in the admin could list or restore those entries, so recovering from 
   an accidental Trash click meant editing the database by hand. v0.1.4 deliberately
   removed the `confirm()` gate from the row-level Trash link because that gate 
   silently cancelled the click in browsers that suppress dialogs; this release 
   supplies the recoverability that makes a one-click, unconfirmed Trash safe — 
   the same trade WordPress core makes with “Move to Trash”.
 * The Trash view keeps the active keyword / status / form / date filters and the“
   Show spam” toggle when you switch views, and the All / Trash counts show how 
   many entries are in each bucket. Restoring from the Trash view leaves you in 
   the Trash view instead of bouncing you back to All. The Trash link stays hidden
   while the trash is empty, matching core list screens.
 * Restore is a plain nonce-protected link with no `confirm()` gate, for exactly
   the reason given in the v0.1.4 entry below.
 * No database schema change: restore simply clears the existing `is_deleted` flag,
   and status, spam flag, notes, and attachments all survive a trash/restore round
   trip. Adds the nonce action `nldcf7_restore_<id>` and the query var `status_view`;
   existing `?page=nldcf7-*` URLs, option names, page slugs, capabilities, and hooks
   are unchanged, and the Export screen’s “Include entries moved to trash” option
   behaves exactly as before.

#### 0.1.4

 * Fix: the row-level “Trash” link on the entries list did nothing when clicked —
   no confirmation, no notice, and the entry was not moved to trash. The link carried
   an `onclick="return confirm(...)"` gate; because `confirm()` returns false whenever
   the browser suppresses the dialog (Chrome’s “Prevent this page from creating 
   additional dialogs”, embedded webviews, dialog-blocking extensions), the anchor’s
   navigation was cancelled and no HTTP request was ever sent. The server-side GET
   route was therefore never reached, which is why bulk actions — plain form posts
   with no `confirm()` — kept working. The Trash row action is now a plain nonce-
   protected link, matching WordPress core’s own “Move to Trash” row action.
 * No database, option, page slug, capability, or hook contract changes. The GET
   trash route, its nonce action (`nldcf7_trash_<id>`), capability check, and redirect
   target are unchanged.

#### 0.1.3

 * Fix: the entry detail screen did not surface flash notices after status updates
   or note additions. v0.1.2 had added the same per-user transient flash mechanism
   to the Settings page, but the detail screen still discarded notices because `
   NLDCF7_Entry_Detail_Page::render()` did not accept the consumed transient and
   its view template had no notice block. `render()` now mirrors `NLDCF7_Settings_Page::
   render()` and accepts an optional `$notice`; the detail view renders the standard`
   notice notice-success / notice-error is-dismissible` banner; and `NLDCF7_Admin_Menu::
   render_entries_route()` passes the consumed transient when routing to the detail
   screen.
 * No database, option, page slug, capability, or hook contract changes.

#### 0.1.2

 * Fix: the “Settings saved.” confirmation notice did not appear after saving on
   the Settings page (admin menu moved under Contact Form 7 in 0.1.1 changed the
   form’s effective post target in some setups, suppressing the post-save redirect
   and notice flag). The settings form now posts to an explicit URL and the success
   notice is delivered via the same per-user transient flash mechanism the entries
   list uses, so the confirmation reliably appears on the next page render.
 * No database, option, page slug, capability, or hook contract changes.

#### 0.1.1

 * Admin menu relocated: the four screens (Entries / Export / Settings / Help) now
   appear as submenus directly under the existing Contact Form 7 menu (“お問い合わせ”
   in Japanese), instead of as a standalone top-level menu.
 * When Contact Form 7 is not active, no plugin submenu is registered (no broken/
   orphan menu is produced). The missing-dependency warning is now also shown on
   the Dashboard and the Plugins screen, in addition to deep-link hits to plugin
   pages.
 * Help screen: navigation hint updated to match the new location (“Contact > Entries”/「
   お問い合わせ > 一覧」).
 * No database, option, page slug, or capability changes. Existing `?page=nldcf7-*`
   URLs continue to resolve unchanged.

#### 0.1.0

 * Initial release.
 * Automatic capture of Contact Form 7 submissions into a dedicated DB table.
 * Raw payload stored as JSON plus mapped columns for name/email/phone/company.
 * Admin list screen (search, status/form/date filtering, bulk actions).
 * Detail screen with status management and internal notes.
 * CSV export with date/status/form/spam filters (UTF-8 + BOM, chunked streaming).
 * Attachment metadata capture.
 * Privacy-friendly defaults (IP capture off).
 * Opt-in data deletion on uninstall.
 * Extensibility hooks for future Pro integrations.

## Meta

 *  Version **0.4.0**
 *  Last updated **3 weeks ago**
 *  Active installations **10+**
 *  WordPress Version ** 6.0 or higher **
 *  Tested up to **7.1.4**
 *  PHP Version ** 7.4 or higher **
 *  Languages
 * [English (US)](https://wordpress.org/plugins/neutrope-lead-desk-for-contact-form-7/)
   and [Japanese](https://ja.wordpress.org/plugins/neutrope-lead-desk-for-contact-form-7/).
 *  [Translate into your language](https://translate.wordpress.org/projects/wp-plugins/neutrope-lead-desk-for-contact-form-7)
 * Tags
 * [cf7](https://en-au.wordpress.org/plugins/tags/cf7/)[contact form 7](https://en-au.wordpress.org/plugins/tags/contact-form-7/)
   [inquiries](https://en-au.wordpress.org/plugins/tags/inquiries/)[lead management](https://en-au.wordpress.org/plugins/tags/lead-management/)
   [leads](https://en-au.wordpress.org/plugins/tags/leads/)
 *  [Advanced View](https://en-au.wordpress.org/plugins/neutrope-lead-desk-for-contact-form-7/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/neutrope-lead-desk-for-contact-form-7/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/neutrope-lead-desk-for-contact-form-7/reviews/)

## Contributors

 *   [ Neutrope Inc. ](https://profiles.wordpress.org/neutropeinc/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/neutrope-lead-desk-for-contact-form-7/)