Why I Use Formgrid for Every Client Website I Build

Thu, 18 Jun 2026 16:49:24 +0000

A few months ago, I was building a website for my web design agency at leadsgrid.co.

I had the homepage done. The services page was looking good. The industry landing pages were ready. Everything was working.

Then I got to the contact form.

The Problem Every Web Developer Hits

I needed a lead capture form on the site. Not just a contact form that sends me an email. A proper form that would:

Notify me immediately when someone enquires. Store every submission somewhere I could track it. Let me see which enquiries I had followed up on and which ones I had not. Tell me which marketing channel sent each lead.

I had built this before. I knew what it involved.

A PHP backend to receive the POST request. An email sending library to format and deliver the notification. A database to store submissions. A dashboard to view them. Spam protection so bots do not flood the inbox. Something to track UTM parameters.

I looked at my shared hosting on Namecheap. cPanel. PHP 8. MySQL.

I thought: I could build this.

Then I thought: I already built this. It is called Formgrid.

Why I Almost Did Not Use My Own Tool

Here is the thing about building a product. You spend so much time inside it, thinking about edge cases and user flows and feature gaps, that you sometimes forget to step back and see what it actually does.

I almost went down the cPanel route out of habit. The same habit that makes developers spin up a Node.js backend and configure Nodemailer for a contact form when a better option already exists.

What stopped me was a simple question:

If I were not the founder of Formgrid and I needed a form backend for a static agency site right now, what would I use?

The answer was obvious.

What I Actually Did

I pointed the enquiry form on leadsgrid.co at a Formgrid endpoint.

<form action="https://formgrid.dev/api/f/your-form-id" method="POST">
  <input type="text" name="name" placeholder="Your Name" required />
  <input type="email" name="email" placeholder="Your Email" required />
  <select name="package">
    <option value="">Choose a package</option>
    <option value="Lead Starter">Lead Starter $500</option>
    <option value="Lead Engine">Lead Engine $950</option>
    <option value="Lead Machine">Lead Machine $1,500</option>
  </select>
  <textarea name="message" placeholder="Tell me about your business">

Send Contact Form Leads to WhatsApp—No Backend Needed

Mon, 23 Feb 2026 19:37:18 +0000

The Problem

Many websites use contact forms. Most send submissions to email. But email isn’t always reliable—messages get lost in spam, delayed, or buried under marketing clutter. For trades and service businesses, every minute counts when a lead comes in.

If you want contact form submissions delivered instantly to WhatsApp, you normally need backend logic or third-party APIs. That’s a big ask if you want something quick and simple.

Why Email Delivery Is Fragile

SMTP configuration is fiddly and easy to misconfigure
Shared hosting often means bad mail reputation
Spam filters can eat legit messages
Business owners don’t check their inboxes constantly
Important leads get buried under newsletters and promos

It’s not about scaring anyone—just reality for small teams.

The Traditional Way (Technical Explanation)

Normally, to send form data to WhatsApp, you’d need:

A server-side form handler (PHP, Node, Django, etc.)
WhatsApp Business API setup (not trivial)
Webhooks and API tokens
Hosting configuration to keep things secure

It’s not as simple as adding a form action. There’s real backend work involved—especially if you want delivery guarantees.

The Lightweight Approach

There’s a simpler way: use a form endpoint service.

Your HTML form posts to an external endpoint
The service does all the validation and delivery
No server code required on your end

For example, Web2Phone:

Accepts standard HTML form submissions
Delivers to WhatsApp (with optional email fallback)
Lets you set up domain allow-listing and rate limits
Automatically deletes successful submissions for privacy

No hype—just a practical option.

Practical Example

Here’s what it looks like in practice:

<form action="https://web2phone.co.uk/api/v1/submit/" method="POST">
  <input type="hidden" name="public_key" value="YOUR_PUBLIC_KEY">
  <input name="name" required>
  <input type="email" name="email" required>
  <textarea name="message" required></textarea>
  <button type="submit">Send</button>
</form>

The public_key links the form to your account (no secrets in the browser)
On submission, the service validates and delivers the message
Delivery is tracked—if WhatsApp fails, fallback to email

WhatsApp + Email Fallback

You can choose WhatsApp only, email only, or both. If WhatsApp delivery fails, it automatically sends via email. This keeps things reliable without extra logic on your end.

Who This Is For

Static site owners
Agencies and freelancers
Service businesses
Trades who need to respond fast to emergency enquiries
Basically, anyone who wants instant lead alerts without backend hassle.

Security & Spam Protection

Domain allow-listing (only your sites can submit)
Rate limiting to prevent abuse
Honeypot and validation checks
GDPR: successful submissions auto-deleted after delivery

Conclusion

If you want to keep things simple and respond faster, this approach is worth a look. No backend headaches, just instant notifications where you’ll actually see them.
If you want to test this, you can create a free account and generate a public key in under a minute.

Coder Legion - Recent posts tagged contactform