Forget about contact form spam

Every public contact form gets discovered by bots sooner or later. The usual answers are both bad: drown in junk, or put a captcha between you and the people who want to talk to you.

Spam matters even more when requests become GitHub issues, because every issue notifies your team. That is why spam protection is not an add-on in OctoDesk. It is built into every form and every inbox from the start.

No captchas

OctoDesk’s form integrations tell people and bots apart without asking your visitors to do anything. They combine signals that are invisible to humans: hidden trap fields that only bots fill in, the time it takes to complete a form, and a small computational challenge that a browser solves in the background but that makes mass submissions expensive.

Several layers, no configuration

• Origin checks. Submissions are only accepted from the websites you have registered for your project.
• Rate limiting. Floods from a single source are slowed down and stopped.
• Content checks. Messages and emails are scored for typical spam patterns. For email, sender authentication results are taken into account as well.

All of this is switched on by default. There is nothing to set up.

When in doubt, held for review

A message that looks suspicious is never silently deleted. Instead of creating an issue and pinging your team, it is held for review in your OctoDesk dashboard, where you can release it or discard it with one click. Real customers do not get lost, and junk does not reach your repository.