Contact Form 7 usually gives staff an email, not a native WordPress entry. A Sentient Forms AI review lives in a different place: the Submission Ledger. If those records cannot be matched quickly, the review becomes another inbox to search instead of a useful handoff.
The current released integration supports Contact Form 7 AI review after submission through the Submission Ledger. Contact Form 7 does not give Sentient Forms a native place to write entries or notes, so this workflow keeps the form message and AI review as separate records.
Name the three records
The official Flamingo listing on WordPress.org explains that Contact Form 7 does not save submitted messages by default. Many sites use configured mail, while some add separate storage such as Flamingo. Sentient Forms adds a review record; it does not turn Contact Form 7 into a native entry system.
| Record | Job | Owner |
|---|---|---|
| Contact Form 7 mail | Delivers the submitted message | Site mail configuration |
| Optional message storage | Keeps a site-controlled copy | Storage plugin and site policy |
| Submission Ledger | Keeps the Sentient Forms submission and action run | Sentient Forms in WordPress |
Write those names into the staff procedure. “The form entry” is too vague when each person may mean a different record.
Choose a match key before launch
Staff need a small set of visible facts that can connect the mail to the ledger record. Good candidates are the form name, submission time, a non-secret reference, and one ordinary contact field already needed for follow-up. Do not create a matching scheme from payment data, passwords, uploaded documents, or unrelated personal details.
- Use the same form label in mail and the WordPress action mapping.
- Keep timestamps in one timezone for staff-facing checks.
- Include only the fields needed to tell two nearby submissions apart.
- Document what staff should do when no safe match exists.
The field-minimization guide helps remove context that does not support the review.
Run one fictional message end to end
- Map one focused action in the WordPress admin.
- Submit fictional data through the public Contact Form 7 form.
- Confirm the visitor sees the normal Contact Form 7 response.
- Open the delivered mail or site-controlled message record.
- Open the Submission Ledger and locate the same test.
- Compare the original message, action result, match key, and expected staff decision.
Capture the form ID, test time, action, expected result, observed result, and screenshot. The guide to retesting forms after plugin updates uses the same real-path discipline after maintenance.
Make the daily check one screen wide
A WebMaster should be able to answer four questions without opening raw payloads: Did mail arrive? Did the ledger record appear? Did the action finish? Can a reviewer match the result to the source message?
| Ledger | Meaning | Next step | |
|---|---|---|---|
| Found | Found | Normal pair | Review the result against the message |
| Found | Missing | Review did not create a visible pair | Keep mail as source; investigate the action |
| Missing | Found | Delivery or storage path is incomplete | Do not use the review as a substitute for the source |
| Missing | Missing | No usable record | Retest the public form and delivery path |
Treat missing pairs as exceptions
Do not ask staff to search indefinitely. Give one person ownership, a review interval, and a short exception record: form, time, which side is missing, action, and what was checked. Preserve the source that exists.
The AI review audit-trail guide explains how to keep the source, action result, and human correction distinct. That separation matters most when the pair is incomplete.
Keep the human decision separate
The ledger result is a review aid. Staff should compare it with the original message, record corrections, and own any consequential next step. A confident model result does not repair missing mail, prove that records match, or replace a person’s judgment.
Measure mismatches before speed
Count mail messages with no matching ledger record, ledger records with no usable source, action failures, and results staff correct. Then measure how long a normal pair takes to review. Those numbers can reveal handoff friction. They do not prove conversion, ranking, revenue, or deliverability gains.
The current released Sentient Forms integration records supported after-submission context and action runs in the Submission Ledger. It does not promise a native Contact Form 7 entry or note.
Use a small, documented match key such as form name, submission time, a non-secret reference, and one ordinary contact field needed for follow-up. Test the pair with fictional data before staff rely on it.
No. Treat Contact Form 7 mail or site-controlled message storage as the source record and the Submission Ledger as the Sentient Forms review record. Test both paths with fictional data.
