Choose the right WPForms review record

A WPForms submission can leave several useful records: a notification email, a native entry when the installed edition stores one, and a Sentient Forms review in the Submission Ledger. Trouble starts when staff treats those records as interchangeable.

The original submission and a WPForms AI review do different jobs. Name each record before adding automation, then give staff one repeatable way to match them.

Name the source record before adding AI

Start with the record your site already relies on when a visitor submits the form. For one WPForms site, that may be a stored native entry. For another, it may be a notification email plus an intentional backup or downstream system. Sentient Forms should add a review record, not quietly redefine which copy is authoritative.

Record	What it proves	What it does not prove
WPForms source record	What the visitor submitted in the site’s normal workflow	That an AI Action ran
Notification email	A delivery attempt reached the configured mail path	That the message is the site’s official stored copy
Sentient Forms Submission Ledger	Captured submission context and linked Action runs in the configured ledger path	Native WPForms entry-note parity
Staff decision	What a person approved, corrected, or did next	That the model was correct

Check what the installed WPForms edition stores

WPForms’ own entry guide describes native entry management for paid licenses and points Lite users to Lite Connect for backup and later restore. Its export guide states that WPForms Lite does not enable native entry storage or export.

That edition boundary matters. Do not write a staff procedure that says “open the WPForms entry” until you have confirmed that the site’s installed edition and settings provide that screen for the submissions in scope.

• Record the WPForms edition and version.
• Confirm whether native entries are stored and available to the reviewers who need them.
• Document the notification recipients and the site’s intended backup.
• Keep Lite Connect and other storage choices separate from the Sentient Forms ledger.

Use the Submission Ledger as the review record

The current deployed Sentient Forms integration supports WPForms after-submission work through the Submission Ledger. The ledger can hold the captured submission context and the Action runs tied to it. It is a cross-source review screen, not a claim that Sentient Forms created a native WPForms note.

An Entry Summary can make a long request easier to scan. Missing Information Review can identify gaps for a human follow-up. Staff should still compare the result with the chosen source record before acting.

The broader form handoff checklist explains why the review surface should make the next human decision easier instead of adding another forgotten queue.

Build one modest match key

Staff needs a practical way to tell that a source record, notification, and ledger row belong to the same submission. Use the smallest set of ordinary facts that distinguishes the request without copying unnecessary personal data.

Match clue	Why it helps	Guardrail
Form name or stable form reference	Narrows the source workflow	Update the procedure when forms are duplicated or renamed
Submission time	Separates nearby requests	Allow for clock display and processing delay
Non-secret request reference	Creates a direct lookup when the workflow already has one	Do not invent a customer-visible promise around it
One ordinary contact field needed for follow-up	Helps distinguish otherwise similar requests	Do not add sensitive data merely for matching

Avoid matching on the message body alone. Two visitors can submit similar requests, and copied text may be normalized or summarized differently.

Treat notification mail as delivery, not automatic truth

A notification email is useful, but mail delivery and record storage are separate questions. A message can be delayed, filtered, forwarded, or removed. A stored entry can exist even when a notification fails. The ledger can show an Action run while staff is still looking in the wrong inbox.

Use the entries and alerts audit to reconcile those paths. The goal is a recovery procedure, not a claim that one screen can replace every source.

Test missing pairs before staff depends on them

1. Submit fictional data through the public WPForms form.
2. Record the form reference and submission time.
3. Confirm the site’s normal source record or notification appears.
4. Open the Sentient Forms Submission Ledger and find the matching record.
5. Confirm the expected Action run belongs to that submission.
6. Repeat once with an intentionally failed or disabled review step.
7. Write the recovery path for a source record with no review and a review with no expected source record.

Measure how long a reviewer needs to find the source submission, verify the Action result, and identify a missing pair. A useful workflow should cut lookup time without hiding the original request. Start with one form and one Action before expanding.