← All articles

Guides

How to filter contact form spam without losing genuine inquiries

A contact form is often the start of a customer relationship. Spam filtering should help you find those conversations, not make visitors prove they deserve a reply.

The difficult part is that genuine inquiries can resemble unwanted messages. A customer might paste a long request, include several links, write in another language, or ask a very short question. None of those details, on its own, tells you whether the message belongs in spam.

Start with the purpose of the form

A sales proposal sent to a support form is different from a proposal sent to a page inviting business partnerships. A message about a broken login is useful to a support team even though it contains words such as “password” and “account.”

Give your spam filter a short description of your website and the messages each form is meant to receive. Useful context includes whether you expect quote requests, support questions, job applications or partnership proposals. This helps the filter judge the request rather than rely on isolated words.

Use signals as evidence, not a verdict

Link counts, repeated phrases and submission timing can help identify patterns. They also appear in legitimate messages. Someone reporting a broken website may include several URLs. A visitor using autofill can submit quickly. A person asking about a scam may quote the scam itself.

Spamadin combines these signals with contextual classification. Fast submission, pasted text, language and missing browser interactions alone do not establish spam. The goal is to distinguish a genuine conversation from clear unsolicited promotion, deceptive requests or manipulative link placement.

Preserve messages when a check cannot complete

Your integration should distinguish three outcomes: allow, spam and review. A review result means the submission needs another decision; it is not permission to delete it. Network failures also need a recovery path.

Our WordPress plugin uses the existing comment moderation queues and a private local recovery inbox for supported contact forms. Held form messages stay in your WordPress database for up to 30 days. Check the inbox regularly and contact genuine senders directly; marking a message legitimate does not replay form notifications or other actions.

For a custom integration, save the submission in your own system before calling the API, then handle each outcome explicitly. Keep API keys on your server. The browser can collect optional interaction evidence without receiving your service key.

Correct mistakes without sharing message bodies

When you find a wrong decision, send its check reference and the corrected label. This provides feedback without sending the message body again. Sharing an example for further spam improvement is a separate opt-in feature; routine checks do not retain message bodies on Spamadin.

No spam filter can promise perfect decisions. Start with accurate website context, preserve uncertain messages, and review mistakes so you can adjust the protection to your use case.

Read the integration guide for request examples, verdicts and feedback endpoints.