Skip to main content
Clever Ops

Case studyReal job

How we built a charter enquiry form that emails the owner

We built a new website for a fishing charter operator, with a page of their charters, a gallery, their booking terms and an enquiry form.

  • Next.jsSite and form route
  • TypeScriptThe site's code
  • Tailwind CSSPage styling
  • React Hook FormChecks in the browser
  • ZodThe form's rules
  • ResendSends both emails

Transcript

This is a made-up enquiry going through a website we built for a fishing charter operator in Australia. The form asks which charter, which day and how many people. The owner gets all of it in one email, and hitting reply answers the customer.

The owner found us through one of our ads, and rang me. They'd put their first website together themselves. We built them a new one from scratch, with a page of their charters, a gallery, their booking terms and an enquiry form.

The form was the part that needed the most thought. A charter quote turns on three things: which trip, which day and how many people. If an enquiry doesn't say, the first reply has to be a question, and the quote waits for the answer.

Here's how it works now. The customer picks a charter from a list, or says they're not sure yet. They can pick a preferred date, then enter how many people, their name, email, phone and a message. If something's missing, the form names the field before anything is sent. On a phone, the fields stack into one column.

Once it's sent, the form clears and says the message went through, and two emails go out. The owner gets the enquiry in two blocks, contact details and charter details, with the customer's own address as the reply-to. The subject line carries the customer's name. The customer gets a thank-you that repeats their charter, date and group size, with a number to ring if it's urgent.

There's no online booking, no payment and no database. The owner reads the email, then replies or rings the customer to quote and book. The booking and the payment happen outside the site.

Now the detail. It's a Next.js site, written in TypeScript and styled with Tailwind. Every charter is one entry in a single data file, and the charter cards are built from it. When the owner later asked for a new kind of charter, that meant a new entry there and a new choice in the form.

The form's rules are one Zod schema: what's required, a valid email address, and a minimum length for the name, phone and message. That schema checks the form in the browser. The server checks it again before any email is built, so a request that skips the page is turned away too.

The form posts to a Next.js route handler on the same site. It builds both emails from the checked details and sends them through Resend's API, with the customer set as the reply-to on the owner's copy. The sending key lives on the server, so it isn't in the page.

It's been live since October 2025, on our monthly hosting plan, and small changes like that new charter sit inside the plan. The site keeps no analytics and no database, so there's no count of enquiries, and no before and after to show you.

If enquiries reach you without what you need to quote, get in touch.

The form asks which charter, which day and how many people, and emails the owner the enquiry with the customer as the reply-to. The customer gets a thank-you that repeats what they asked for. There's no online booking or payment: the owner quotes and books by hand.

How and why they came

The owner found us through one of our ads and rang me. They'd put their first website together themselves. We built them a new one from scratch.

The problem

The part that needed the most thought was the enquiry form. A charter quote turns on three things: which trip, which day and how many people. If an enquiry doesn't say, the first reply has to be a question, and the quote waits for the answer.

What we built

  1. 1

    The site

    A charters page, a gallery, an about page, a contact page and the owner's booking terms on a page of their own. Each kind of charter is one entry in a single data file, and the charter cards are built from it.

  2. 2

    The enquiry form

    Seven fields: name, email, phone, the charter (from a list that includes "not sure yet"), a preferred date, the number of people and a message. The date is optional; the rest are required. If something's missing or doesn't fit, the form names the field before anything is sent. On a phone the fields stack into one column.

  3. 3
    Resend

    The owner's email

    Each enquiry arrives as one email, set out in two blocks: contact details, then charter details, then the message. The subject line carries the customer's name, and the reply-to is the customer's own address, so a reply goes to them.

  4. 4
    Resend

    The customer's thank-you

    The customer gets an email that repeats their charter, preferred date and group size, with the business phone number for anything urgent.

The form and both emails, on sample data

  • The enquiry form, filled in with a made-up enquiry.

    The system's own output. Sample brand and data.

  • Sent empty, the form names each missing field.

    The system's own output. Sample brand and data.

  • The owner's email: contact details, then charter details.

    The system's own output. Sample data.

  • The customer's thank-you email.

    The system's own output. Sample data.

What a person still does

The owner reads each enquiry, then replies or rings the customer to quote and book. Bookings and payment happen outside the site. Changes to the site, like adding a new kind of charter, go through us.

The technical detail

What each tool allowed

Next.js

  • The site runs on Next.js 14 with the App Router.
  • The form posts to a route handler on the same site.
  • Route handlers are custom request handlers for a route, built on the Web Request and Response APIs, and they can be used to handle form submissions.1
  • The sending key is a server environment variable.
  • In Next.js, environment variables without the NEXT_PUBLIC_ prefix are only available on the server and aren't accessible to the browser.2

Zod

  • The form's rules are one Zod schema: which fields are required, a valid email address, and a minimum length for the name, phone and message.
  • In the browser, React Hook Form checks each field against it.
  • On the server, the route checks the same schema with safeParse, which returns a result object holding either the parsed data or the error, instead of throwing.1
  • An enquiry that fails is turned away before any email is built.

Documentation

  1. 1Zod basics

Resend

  • The route sends both emails through Resend's API.
  • Its send call takes a sender, recipients, a subject, the HTML body and a reply-to address.12
  • The owner's copy has the customer's address as its reply-to.

Vendor links checked 15 November 2026.

Design decisions

  • Ask for the three facts a quote needs

    Charter, date and group size have their own fields, so they arrive in the same place in every email. The charter is picked from a list rather than typed.

  • Check twice

    The same schema runs in the browser, where it helps the customer, and on the server, where it stops a request that skips the page.

  • Reply goes to the customer

    The owner answers an enquiry the way they answer any email.

  • One list of charters

    The charter cards come from one data file. When the owner later asked for a new kind of charter, it was a new entry there and a new choice in the form.

Where it stands

Live since

October 2025

  • It's been live since October 2025, on our monthly hosting plan.
  • Small changes, like the new charter, sit inside the plan.

The site keeps no analytics and no database, so there's no count of enquiries and no before and after figure on this page.

Questions

Can a website enquiry form ask for the charter, the date and the group size?

Yes. On this job each has its own field: the charter is picked from a list, the date from a date picker, and the group size is a number. The charter and group size are required; the date is optional.

Do I need online booking on a charter website?

It depends on how you take bookings. This site has none: it collects the enquiry and the owner quotes and books by hand.

How does a website enquiry reach my inbox?

On this job the site's server sends it as an email through Resend, with the customer's address as the reply-to, so replying answers the customer.

Does the customer get a confirmation?

They get a thank-you email that repeats their charter, preferred date and group size. It isn't a booking confirmation: there's no booking on the site.

Can I add a new charter later?

On this site each charter is one entry in a data file, plus a choice in the form's list. Here that kind of change sits inside our monthly hosting plan.

Want enquiries that arrive with what you need to quote?

Book Free Assessment

Product names and logos belong to their owners and are shown to identify the systems connected.