Case study

Inquiry routing with spam protection

Forms that store, throttle, and notify — the same ideas used on this portfolio contact flow.

Project: Lead & Inquiry Routing Automation

Overview

Lead automation is more than sending mail(). It is validation, bot resistance, persistence, and optional webhooks to systems sales already checks.

Problem statement

Generic mailto links lose structure; open forms attract spam.

Requirements and constraints

Required fields, consent flag, honeypot, rate limit, database storage, optional owner email when notify settings exist.

Proposed architecture

Single POST endpoint, form request, model create, queued notification.

Database design

Inquiries table with timestamps and read state in admin.

API design and authentication

Optional outbound webhook JSON for CRM integration on client projects.

Security

Throttle by IP. Honeypot field hidden from users. No secret keys in the browser.

Performance

Notification async so the thank-you page returns immediately.

Testing and deployment

Portfolio feature tests cover guest submission and admin visibility rules.

Challenges and lessons

Shared mobile IPs versus aggressive throttling.

Verified results

This site’s contact pipeline follows the same design client sites extend.