Standing service wordpress-form-delivery-checked-every-month · revised 11 October 2026
Standing service
Check that every form on your WordPress site still delivers, month after month
Each month we submit a marked test through every form you name, check it reaches the agreed mailbox, and report the sender checks in the original message and what we saw.
This starts a conversation by email. Nothing is charged, and no test is submitted, until we have agreed scope, terms and your written authorisation.
The responsibility you hand over
A form shows a thank-you message whether or not the notification reaches anyone. A plugin update, a changed mail setting, an expired sending password or a new spam rule can break delivery with no error on the page, and the first sign is a customer asking why nobody replied.
Who it’s for: Owner of a WordPress site that lives on enquiries, bookings or quote requests that arrive by form.
Usually starts when: A form quietly stopped sending once before and nobody noticed for weeks, or the site changes often enough that a form could break unseen.
The result: Each month every form you name has been tested end to end, you hold a report showing whether the marked test arrived and what the sender checks in the original message said, and any failure is explained with the evidence.
What stays true, and what we do about it
No response-time guarantee is published for this new service. The test day and the time we tell you about a failure are agreed in writing before it starts. Between tests we do not watch the forms.
Hours are agreed in writing before the service starts. The service is not staffed round the clock and tests run on the agreed day each month.
What must remain true
- Every named form was tested end to end once in the month
- You hold the results, with any failure explained
What we watch
- The monthly marked test submissions through the public forms
- The original messages received in your agreed mailbox, as the saved files or copied source you send us
- Changes to the site that you report to us
When something happens
Scroll the table sideways to read it all.
| When | What we do |
|---|---|
| A month's test day arrives. | We submit a marked test through each named form with the agreed identity, wait for the notification and read the sender checks in the original message you send. |
| A test does not arrive within the agreed window or fails a sender check. | We tell your named contact with the evidence and the likely layer. If the cause is the form's sending path, we offer the form-notification job. Priced as: WordPress form emails not arriving |
| You tell us a form, plugin or mail setting changed. | We run an extra test of the affected form and add it to the report. |
| A month ends. | We send the report: each form's result and how it compares with last month. |
We do on our own
- Submit marked tests through the public forms with the agreed identity
- Read the original messages you send us
- Report results
We ask you first
- Any test that triggers a payment, a CRM record, an autoresponder, a list sign-up or any other action beyond the notification and an automatic reply to the marked address
- Any change to the site, the form or the mail setup
- Adding a form beyond the five
We escalate to you when
- Two tests in a row fail for the same form
- A sender check starts failing for a domain that passed before
- The form accepts submissions but no entry is saved
How you know it held. Each month the report shows, for every form, whether the marked test arrived, how long it took and what the sender checks in the original message said. It shows the state on the test day only.
How we keep it true
This service is never finished. Each month's report shows whether every named form delivered, and it continues until you end it.
Make your WordPress form notification emails arrive, through authenticated sending Job Each time it fires
Set up authenticated sending for up to three forms on one WordPress site, so notification emails come from your domain, and prove each one reaches the agreed mailbox.
Quoted per fix, if you buy it
The same job you can buy on its own, offered when a monthly test shows a sending fault.
What is included, and what is not
- A monthly report: for each form the time sent, the time received, the placement and the sender-check results
- Evidence of any failure, with the likely layer: the form, the site's sending, the mail service or the receiving mailbox
- A note of any form whose settings changed
- The marked test entries listed by time and marker, so your team can delete them
Included
- Up to five named forms on one single WordPress site, each confirmed in writing to trigger nothing but its notification to the agreed mailbox and, at most, an automatic reply to the marked test address
- A marked test submission through each form once a month, using the same marked test identity every month: a name starting "ZZ SI Test", an email address at a domain Synthetic Industry controls (so any automatic reply comes back to us and never reaches a third party), a telephone number from the range Ofcom reserves for drama (07700 900000 to 07700 900999) and the message "Monthly delivery test, no reply needed"
- Checking that the notification reaches the agreed mailbox and reading the sender-check results in the original message you send us
- Noting whether the message landed in the inbox or in junk
- A monthly report comparing this month with last month and listing recent site changes you tell us about
Not included
- Watching the forms between monthly tests or any alert the moment one fails
- Repairing the cause beyond naming it, unless you buy the form-notification job
- Spam submissions and spam filtering
- Any form whose submission does more than send its notification to the agreed mailbox (and, at most, an automatic reply to the marked test address), such as adding the sender to a newsletter or marketing list, sending a text, chat or ticket alert, routing the lead to a salesperson, calling a webhook or automation tool, or taking a payment or writing to a CRM or customer database, unless a safe test route for that action is agreed in writing
- Cover outside the agreed hours
- Multisite networks
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
Each month every named form has a recorded marked test using the agreed identity, with the time sent, the time received (or not received) and the placement
Evidence: The monthly report compared with your mailbox
Each received test has its sender-check results recorded from the original message you saved, not from a forward
Evidence: The header lines quoted in the report, with personal details removed, and a note of which form of the message each came from
Each failed test has a stated likely layer and the evidence behind it
Evidence: The failure section of the report
Every test entry is listed with its time and marker so that your team can find and delete it
Evidence: The list of test entries in the report, compared with the entries in your form plugin
Sign-off. You read each monthly report. A month counts as delivered when you accept it.
If it fails. If we cannot complete a month's tests, we say so and it does not count as delivered. If the service is not working for you, you can end it at the end of any month.
When it fits, and when we stop
It fits when
- Each named form accepts a marked test submission, with any spam protection set to allow it by an agreed rule. We do not try to get round a CAPTCHA or other spam protection
- You authorise us in writing to submit automated test entries through the named live forms on the agreed day each month, and you tell your staff the test day and the marked identity so nobody replies to or acts on a test
- For each named form you confirm in writing everything a submission triggers: the notification, any automatic reply, list sign-up, text, chat or ticket alert, lead routing, webhook or automation tool, and analytics or advertising conversion. Anything beyond the notification to the agreed mailbox and, at most, an automatic reply to the marked test address is excluded unless a safe test route is agreed in writing. Any opt-in box is left unticked, and you either exclude the marked identity from your analytics or accept that each test is counted
- A mailbox you control receives the notifications, and a named person can save the original of each received test message as a file, or copy its source, and send it to us with your own address blanked out. A normal forward does not work, because the forward is a new message and its sender checks describe the forward, not your mailbox's receipt
We stop and tell you if
- Spam protection blocks every automated or test submission and cannot be adjusted
- Notifications go to many recipients or a shared inbox that we cannot check
- Most failures come from the receiving mailbox's own filters, which you cannot change
- The forms trigger live payments or irreversible actions on submission
- A form triggers a list sign-up, text or chat alert, lead routing, webhook or conversion that you cannot confirm in writing, switch off or exclude for the test
- Only a normal forward of the received message is possible, so the original message cannot be read
What could go wrong
We make no change to your site. Ending the service stops the tests. Marked test entries are listed by time and marker so your team can delete them.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| Test entries pollute your records or trigger a follow-up message, call, list sign-up or conversion for a real person | Tests use one marked identity that points only at us or at a reserved number, forms with other actions are excluded unless a safe route is agreed in writing, opt-in boxes stay unticked, and entries are listed for deletion. |
| Spam protection is loosened to let tests through | We only ask for a narrow allow rule for the marked test, and you decide whether to grant it. We do not try to get round a CAPTCHA. |
| The sender checks are read from a forwarded copy and describe the forward, not your mailbox's receipt of the test | We ask for the original message saved as a file or its copied source, not a normal forward, and the report says which form of the message each result came from. |
| A monthly test misses a failure in between | The report says it shows the test day only, and the service does not claim continuous monitoring. |
Each report is checked by a reviewer separate from the work that produced it before it is sent. No human supervisor is included unless your agreement names one. At launch the work is largely automated, and we say so.
Stays with a person
- You authorise the automated monthly test entries in writing
- You approve any test that touches a CRM, a payment, an autoresponder or any other action beyond the one notification
- You approve any change to the forms or mail setup
Access we would need
- No access to your site or mailbox: public form submissions and the original messages you send us only
Questions
Will this alert me the moment a form breaks?
No. It tests once a month, so it finds a failure at the next monthly test, up to about a month later, not in between.
Do you need access to my site or mailbox?
No. We submit through the public forms and read the original messages you save and send us. We never log in.
What identity do the tests use?
The same marked one every month: a name starting "ZZ SI Test", an address at a domain we control, a telephone number from the range reserved for drama and a message saying it is a test. You tell your staff in advance so nobody replies or acts on it.
Why can I not just forward the message?
A normal forward is a new message sent by your mail program. Its sender checks describe that forward, not the moment your mailbox received the test, so we ask for the original saved as a file or its source copied.
What about forms that join a mailing list or alert my sales team?
They are excluded unless a safe test route is agreed in writing, because a test must not add anyone to a list, send a text or chat alert, route a lead or count as a conversion.
What if a form is broken?
We tell you the likely layer and the evidence. Repair is the separate form-notification job.
Also part of
Send an enquiry
Send us
- The addresses of up to five forms and the form plugin used
- The mailbox that receives each notification
- Everything each form triggers after a submission: the notification, any automatic reply, list sign-up, text or chat alert, lead routing, webhook or automation tool, analytics or advertising conversion
- What changed on the site recently and how often it changes
- Who should be told when a test fails
Later, once you agree
- Your written authorisation for the monthly automated test entries, and your written list of what each form triggers
- The marked test identity as agreed, and any allow rule for spam protection
- For each received test, the original message saved as a file or its source copied, with your own mailbox address blanked out, sent to the agreed address. Not a normal forward
- A named contact for failures
- A company-controlled secure handoff agreed before access: no live passwords, keys, private code or customer records by ordinary email.
You keep the site, hosting and mailboxes. We submit marked tests through the public forms and read the original messages you send us. We do not log in to your site or mailbox.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “wordpress-form-delivery-checked-every-month” as the subject.