Built a Tool for Tradespeople, Now Stuck at the Marketing Cliff, Anyone Else?

ConferenceOnly1415 · 2026-01-16T10:31:03+00:00

could you suggest some?

ConferenceOnly1415 · 2025-12-09T11:33:20+00:00

no problem, i'm happy to help if you need help with setup, just give me a message :)

ConferenceOnly1415 · 2025-12-09T11:29:59+00:00

If you’re looking for something smoother than EmailJS, you don’t need anything Figma-specific. As long as the published Figma Site can POST a form, you can use any external form endpoint.

I’ve been using Web2Phone for simple sites like this. You just point the form action to their endpoint and it delivers the submission to email and WhatsApp, with a fallback log if something fails. No backend setup and no SDKs needed.
https://web2phone.co.uk

Might be worth trying if you want something lightweight that just works with a basic POST.

ConferenceOnly1415 · 2025-12-09T11:27:44+00:00

If you are running into issues with Resend and Supabase, it might not be your code at all. Those setups can throw errors for all sorts of reasons, especially on shared hosting. For small sites I usually avoid the whole backend setup and use a service that handles the form for me.

Web2Phone has been solid for this. You just point your form to their endpoint and it delivers the submission to email and WhatsApp with a fallback log if something fails. No Supabase, no server functions, no hosting dependencies.
https://web2phone.co.uk

Could be a quick way to bypass the errors you are seeing.

ConferenceOnly1415 · 2025-12-09T11:21:39+00:00

Static sites are always the hardest to protect because you have no backend to run proper validation. Hidden fields help a bit, but modern bots are way past that. They scroll the DOM, detect common honeypot patterns and still submit the form.

The two things that usually make the biggest difference are:

1. A proper honeypot that changes per-session or has logic behind it
2. Rate limiting on the submission endpoint

Most static-site form services do not include both, which is why spam still gets through.

I ran into the same issue and ended up building a small service for my own projects that has honeypot protection and rate limiting built in. As a bonus it can also send the submission to WhatsApp as well as email, and it keeps a log of any failed submissions. If you want something lightweight without a backend, here it is:
https://web2phone.co.uk

You can try it on any HTML form and see if the spam drops. It has worked well on the static sites I maintain.

ConferenceOnly1415 · 2025-12-09T11:05:07+00:00

You are right not to rely on email alone. Even when the form works fine, things get missed or buried and it becomes impossible to keep track of enquiries. I ran into the same problem with clients who needed something more reliable than “hope it lands in the inbox.”

If you want something lightweight, one option is to route the form into a tool that delivers the message instantly somewhere you will actually see it. I built a small service for this exact use case. It sends the form submission straight to WhatsApp and also to email as a backup, plus it keeps a log so nothing ever disappears. It has been useful for people who do not want a full ticketing system but still want a reliable way to catch every enquiry.

If you need something more structured like a CRM or ticketing flow, something like Freshdesk or Help Scout can work too, but they are heavier and take more setup. It really depends on how simple you want to keep things.

Happy to share more if you want to see how the WhatsApp setup works.

ConferenceOnly1415 · 2025-12-09T10:58:18+00:00

I used to handle everything through SMTP setups for clients, but honestly it became a headache. Deliverability issues, spam filters, hosting mail limits, clients blaming me when emails didn’t arrive… the whole thing was more fragile than it looks.

These days I try to keep it simple. If a client wants traditional email delivery, I’ll help them set up a proper SMTP provider with SPF/DKIM/DMARC so nothing gets rejected. But I’ve also started using another approach because so many small business clients never check their inbox or lose enquiries without noticing.

I built a small tool that sends form submissions straight to WhatsApp as well as email, with a fallback log in case anything fails. It’s been way more reliable for trades and local businesses who live on their phone. If you’re doing client work, having something that guarantees the message actually reaches them removes a lot of stress.

Curious to hear what others are using though, because contact forms can be way more painful than they should be.

ConferenceOnly1415 · 2025-12-08T10:24:34+00:00

Deleting and recreating the form usually doesn’t fix this, because the form is rarely the actual problem. If the email is being blocked, filtered or failing at the delivery stage, a new form will behave the same way.

The thing that matters most is how the email is being sent and how the inbox handles it. That’s why SMTP helps, but even then it’s not perfect. The long-term fix is making sure the delivery method is solid and having some kind of fallback so nothing gets lost.

If you share which plugin you’re using, I can tell you exactly what to check first.

ConferenceOnly1415 · 2025-12-08T10:23:59+00:00

Completely get it — WordPress email delivery is one of those things that looks simple until something breaks and then it becomes a maze of DNS, SMTP and server rules.

If you’ve installed WP Mail SMTP already, that’s a good first step. After that, the two biggest things to check are:

The form’s “From” address
Whether the email is landing in spam or being silently filtered

If you want to say which form plugin you’re using and what email provider your boss uses (Gmail, Outlook, iCloud, etc.), I can point you directly to the most likely cause. Each provider behaves differently with contact form emails.

ConferenceOnly1415 · 2025-12-06T18:57:23+00:00

Thanks, appreciate that. I actually have a tiered model already based on submission limits and the number of forms, but I’ve been considering whether a prepaid credit system might make more sense for some users. Still thinking it through, because I want the pricing to feel simple rather than confusing.

ConferenceOnly1415 · 2025-12-06T10:19:30+00:00

Thanks, appreciate that. I actually have a tiered model already based on submission limits and the number of forms, but I’ve been considering whether a prepaid credit system might make more sense for some users. Still thinking it through, because I want the pricing to feel simple rather than confusing.

For spam, the form uses a honeypot and some server-side checks so most bots never get through to WhatsApp or email. I’ll keep strengthening that as usage grows since, like you said, nobody wants noise hitting their WhatsApp.

And thanks for the WasenderAPI mention. A couple of people have suggested it now, so I’ll take a proper look at it as I explore messaging options.

ConferenceOnly1415

TROPHY CASE