SENRIKO is now in early access - monitor your first website free. Explore SENRIKO
A form check proves your form still sends leads by sending one, so a real enquiry arrives every time it runs. If you own the code behind your form, the cleanest answer is to discard it there. If you do not - a hosted form builder, a form posting straight to a third party - an inbound rule in your CRM is the lever you have, and it is a settings screen rather than a deploy.
Every check submits as the same made-up person. Any of these identifies it:
Match the domain, not the whole address. The full address contains the check's own id, and deleting a check and setting it up again mints a new one - a rule keyed on the whole address would then quietly stop matching, months later, with nobody looking. Use the full address only if you deliberately want one rule per check.
Four things, in this order. The last two are the ones people forget, and they are the ones that cost somebody an afternoon.
Do not delete them outright. A monitoring submission that arrives is evidence your form works, and seeing them stop is sometimes how you notice a problem before we report it.
Each one names the place the rule lives and the trap that is particular to it - the thing that makes a correct-looking rule fail there and nowhere else.
Settings > Digital Pipeline, or a Salesbot triggered on incoming leads. Condition on the contact email containing checks.senriko.com.
Digital Pipeline actions run in stage order, so put the move-and-tag stage at the front - a notification stage placed before it still fires.
Official documentationCRM > Settings > Automation rules on the Lead entity: condition on the email field, actions Change stage and Add tag.
Automation rules fire per stage. Add yours to the first stage a web form lands in, or a lead that skips that stage skips the rule with it.
Official documentationWorkflows > Contact-based, enrolment trigger: Email contains checks.senriko.com. Actions: set a Lifecycle stage of your own and add to a static list.
Enrolment is once by default. Turn on re-enrolment or only the first check ever gets filed - every later one arrives untagged.
Official documentationAutomations > Deal created, condition on the person's email, actions Move to a Monitoring pipeline and Update a custom field.
Automations do not run on deals created by other automations. If a webhook or Zap creates the deal, filter at that step instead.
Official documentationSetup > Automation > Workflow Rules on Leads, executed on Create, criteria Email contains checks.senriko.com.
Assignment rules run before workflow rules, so the lead is routed to a human owner first. Reassign inside the workflow, or exclude the address from assignment.
Official documentationA record-triggered Flow on Lead, entry condition Email contains checks.senriko.com, updating Lead Source and Owner.
Web-to-Lead assignment rules fire before flows. Either exclude the address there or let the flow reassign afterwards - both work, doing neither does not.
Official documentationAutomations on the Leads board: When an item is created and email contains checks.senriko.com, move it to a Monitoring group and set a status.
Board automations do not run on items created by an integration by default - check the integration's own settings if leads arrive that way.
Official documentationSettings > Automations, or a Smart List filtered on Email contains checks.senriko.com with a tag applied on entry.
Smart Lists filter what you see and change nothing about routing. Pair it with an automation, or the lead is still assigned and still notified.
Official documentationAdmin Settings > Workflows on Contact created, condition Email contains checks.senriko.com, actions Add tag and Update lifecycle stage.
Workflows evaluate after lead scoring, so the record may already have been scored and surfaced before it is tagged. Score exclusion is a separate rule.
Official documentationPower Automate, When a row is added to Leads, condition on emailaddress1, then update ownerid and statuscode.
Business process flows can override a status set by a flow. If the stage bounces back, set it through the process step rather than the field.
Official documentationIf leads land in a mailbox or a sheet rather than a CRM: a mail filter on the sender domain checks.senriko.com, or a formula that flags rows whose message begins with [SENRIKO TEST.
Filter to a folder rather than to the bin. A check you can never find again is a check you cannot use as evidence when something breaks.
If the form posts to code you control, you do not need a CRM rule at all: read our header and answer normally without storing anything.
That is the strongest option available, and it also lifts the once-a-day ceiling on form checks. The header page has the four lines it takes.
The pattern is the same everywhere: a rule on incoming records, matching the sender's domain, that tags the record, moves it out of the working queue, leaves it unassigned and suppresses automations. Any CRM that can route by lead source can do this.