Standing service crm-junk-form-leads-hold-rules-checked-monthly · revised 12 October 2026
Standing service
Keep your bot-lead hold rules tested every month, with the held list reviewed
Each month the seeded set is re-run, the held list and a sample of routed leads are checked, the release rate is reported, and rule changes wait for your approval.
This starts a conversation by email. Nothing is charged, and nothing is run on your data, until we have agreed scope, access and terms with you in writing.
The responsibility you hand over
Junk-lead rules go stale as bots change. A rule that held 28 of 30 junk submissions in month one may let far more through by month four, and nobody checks. The fixed set shows whether the rules and the form still work; a sample of routed leads shows whether new bot patterns get past, and held leads that nobody reads are lost leads.
Who it’s for: Marketing manager or agency who has junk leads held for review and wants the rules to keep working.
Usually starts when: Bots change their pattern and the hold rules from the one-off job slowly stop fitting.
The result: Every month the seeded junk and genuine set is re-run, a sample of the held list and a sample of routed leads are checked by your reviewer, and the release rate and the junk that got past are reported. Proposed rule changes wait for your approval.
What stays true, and what we do about it
No response-time guarantee is published for this new service. A target for delivering each list or record is agreed in writing before it starts, set to what a service at this stage can actually keep.
Hours are agreed in writing before the service starts. At launch the service is not staffed round the clock and runs on the cycle named here.
What must remain true
- The seeded junk and genuine set still gives the agreed result each month
- We report each month whether the held list was read and how long any genuine lead sat in it
What we watch
- The synthetic junk and genuine submissions
- An export of the held list for the month
- A redacted export of the leads routed this month
When something happens
Scroll the table sideways to read it all.
| When | What we do |
|---|---|
| A month closes. | We re-run the seeded set and report the held and released counts. |
| The seeded run holds fewer junk items than the pass mark. | We propose rule changes and re-run them on the test portal before you approve. Linked job: Bot form leads held for review |
| A genuine lead is found in the held list for more than the agreed time. | We flag it first in the summary and propose a rule change. |
| The held list was not read this month. | We say so in the summary and ask who will read it. |
We do on our own
- Re-run the seeded set on the test portal
- Prepare the report and the proposed rule changes
- Offer a fixed job as a next step
We ask you first
- Any change to a rule, a threshold or the data covered
- Any request for wider access to a system
- Starting any fix, merge, send or write
We escalate to you when
- The seeded run fails the genuine-lead check
- The held list grows for two months with nobody reading it
- The form changes so the hold no longer works
How you know it held. Each month the seeded results can be re-run by you from the test set, and the summary reports held, released and mistaken counts and the junk found in the routed sample.
How we keep it true
This service is never finished. Each period's record shows whether the thing it watches stayed true, and it continues until you end it.
Hold bot leads from your web forms for review, without deleting any of them Job Optional
Submissions that match junk rules you approve are held in a review view, not routed or counted. A test of 30 junk and 30 genuine invented submissions checks that no genuine one is lost.
Bought separately; not part of the monthly fee
Needed first, priced on its own page: the one-off hold job that sets the rules.
What is included, and what is not
- The monthly re-run results
- The held and released counts
- The proposed rule changes
- The summary
Included
- The one form path and CRM portal from the one-off job
- A monthly re-run of the seeded 30 junk and 30 genuine synthetic submissions
- A report of items held, released, and genuine ones among the released
- A random sample of 30 leads routed this month from a redacted export, marked by your reviewer for junk that got past the hold, with the count reported next to last month's
- Proposed rule changes for you to approve
- A reminder when the held list has not been read
Not included
- Deleting submissions
- Blocking at the form or server
- Switching rules on without your approval
- Real-time defence against an attack
- A promise that every bot is caught
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
The monthly re-run holds at least the agreed number of the seeded junk items and loses 0 seeded genuine leads. The set is the same each month, so this shows whether the rules and the form still work, not whether new bot patterns get past.
Evidence: The re-run table.
The held, released and mistaken counts equal the rows in the held-list export.
Evidence: The count reconciliation.
No rule change goes live without your written approval.
Evidence: The approval record.
Your reviewer marks 30 randomly drawn routed leads, and the number that are junk is reported next to last month's number.
Evidence: The marked sample and both counts.
Sign-off. You read each monthly re-run and report and tell us whether the rules, thresholds and test set still suit you. A period counts as delivered when you have received the record.
If it fails. If we cannot complete a period because an input is missing or has changed shape, we say so, explain what we need and do not guess. 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
- The one-off hold job has been run, or is bought with this service
- A named reviewer reads the held list at least weekly
- Real records are read only after a written agreement that covers how your records are processed and a separate access step you control; until then we test on invented or redacted data.
We stop and tell you if
- Nobody reads the held list
- You want junk deleted automatically
- The form or CRM changes so the hold no longer works
What could go wrong
The service only tests and reports. Any rule change is yours to switch on or off.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A rule change lets junk through or holds real leads | Each change is tested on the seeded set first and applied only on your approval. |
| The held list is never read | The summary says when it was not read and escalates after two months. |
| A seeded set no longer looks like real bots | The seeded set is refreshed with new patterns you report, and its date is shown. |
A separate automated reviewer checks each monthly re-run and report before it is sent, and no person on our side reviews unless your agreement names one. Your named reviewer reads the held list and approves every rule change. At launch the work is largely automated, and we say so.
Stays with a person
- You approve every rule change
- Your reviewer releases or keeps each held item
Access we would need
- A test portal with notifications off
- A read-only export of the held list
Questions
Does it delete junk?
No. Held items stay in a review view until a person decides.
What does it check each month?
It re-runs the seeded set, reports the held list counts and reports how many of 30 routed leads your reviewer marks as junk that got past.
Do I need the one-off job?
Yes, it sets the rules and the hold. It can be bought with this service.
Also part of
Send an enquiry
Send us
- Any change to the form, the CRM or the campaigns last month
- How many leads were released and how many removed
- Who reads the held list
Later, once you agree
- The held-list export for the month, with notifications off in tests
- A redacted export of the month's routed leads, with notifications off in tests
- The approved rule sheet
- A secure handoff route agreed before any record is shared
You keep the CRM and the form. We re-run synthetic submissions on a test portal and read an export of the held list and a redacted export of the leads routed that month. Which service reads your records is agreed in writing before any real record is shared.
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 “crm-junk-form-leads-hold-rules-checked-monthly” as the subject.