

Entry list with summary cards, filters, and bulk actions.
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
{prefix}nldcf7_entries)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_capabilityRequirements
Does NOT include (outside the scope of the free version)
These may be considered for a future Pro release. The free plugin is designed to be fully useful on its own.
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.
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.
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 )
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.
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.
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.
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.
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.
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.
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.