Insight / Software development
Published
Why we use Resend for website enquiries
How Resend helps us deliver website enquiries, why we recommend it for suitable projects, and how to get started.
An enquiry only helps a business if someone receives it and can respond. When a visitor submits a website form, Netlify Forms verifies and stores the submission. A server-side handler sends a styled notification with a plain-text alternative through Resend. That gives us a record of the enquiry in Netlify and a separate path for the alert.
We have tested that Netlify stores a verified submission and that Resend accepts the corresponding notification. The visitor’s address is set as Reply-To, so a team member can answer the person without making their address the sender of a message they did not send. We can follow each handoff when an enquiry needs attention.
Why it works for us
Resend does one important job in this flow: it accepts a notification from our server and delivers it as email. The API key stays in the server environment, and the website has no public endpoint that lets a browser send arbitrary messages through our account. Netlify checks and stores the form submission before our function prepares the email.
The Resend dashboard also gives us a way to investigate delivery. An API response tells us that Resend accepted a message; the delivery log tells us what happened next. That distinction matters when a visitor says they submitted a form but we cannot see an alert. We can check the form record, function log and email event rather than guessing where the message went. Resend documents its email event webhooks for teams that need to automate that monitoring.
A verified domain authenticates the notifications we send. Resend recommends a sending subdomain for automated mail, and its domain setup walks through the DNS records needed to authenticate it. Those records support sending; receiving mail at an address such as hello@ requires a separate receiving setup. Resend Inboxes can provide a shared address with conversation threads and replies once receiving is enabled and tested.
Why we recommend it
For a small site or application that needs to send contact alerts, receipts or other transactional messages, Resend has a focused API, clear domain setup and useful delivery visibility. It fits well when a developer can make the send from a trusted server function or backend. We like that we can start with one carefully tested workflow and add more only when there is a real need.
Each project still needs its own form verification, record retention and response process. If the requirement is a team mailbox, we would test Inboxes, reply handling, access and data retention before using it as the sole home for client correspondence.
How to get started with Resend
- Create a Resend account and add a domain you own. For automated mail, consider a purpose-specific subdomain such as
notify.example.com. - Copy the exact DNS records shown in your domain’s Resend dashboard, add them at your DNS provider, and wait for verification. Resend’s domain guide explains the process.
- Create an API key with the access your application needs. Store it in your server or hosting environment, never in client-side code or a public repository.
- Send a small test message from a server function or backend. Check the response and delivery events, then send a real test to an inbox you control. Resend’s sending guide gives a straightforward example.
- If you also need a human-facing address, follow the custom-domain receiving guide, create an Inbox, and test both an incoming message and a reply. Receiving uses an additional MX record; a working sending domain by itself does not create an inbox.
Start with the message that matters most to your business. For us, that was making sure a website enquiry reached a person who could answer it.