Case studyReal job
How we built booking requests for a holiday stay site
We built a website where guests choose a stay, see which nights are free and send a booking request.
- Next.jsThe site and routes
VercelHosts the site
NeonStays and blocked nights- ClerkOwner's sign-in
ResendRequest emails- date-fnsDate maths
Transcript
This is a made-up guest asking for a stay, on a booking request flow we built for a holiday accommodation property in Australia. The calendar greys out the nights the owner has blocked. When the guest sends the request, it goes to the owner by email, and nothing is booked until the owner says yes.
They saw one of our ads and rang me. What they bought was a launch: a website, a Google listing, social pages and a video shoot. Along the way came a new domain and a mailbox as well. This film is about the website's booking side.
The website was meant to be a single landing page. It grew into a full site, with a page for each stay and a way for guests to ask for dates.
The owner runs the stays themselves, so what they needed was easy to say. Guests should see which nights are free and ask for the nights they want. Then the owner decides, confirms the stay and bills the guest themselves.
So this is a booking request, not an instant booking. The site takes no payment, and it doesn't confirm anything on its own.
Here's how it works. There are four steps: choose a stay, pick dates, add guest details, then review and send. On the dates step, the calendar loads that stay's blocked nights and greys them out. It holds the minimum stay too, and tells the guest why if they pick too few nights. On a phone, the same steps show as a progress bar.
When the guest sends it, two emails go out through the site. The owner gets the request, with the guest's details, the stay, the dates and the number of nights. The guest gets a note saying it's been received. The site doesn't save the request to its database. It lives in the owner's inbox.
Then a person takes over. A reply to that email goes straight to the guest, so the owner confirms or declines from their own inbox and arranges payment. To keep the calendar right, they sign in to a private page, click the nights that are taken, and save. Clicking a blocked night again frees it up. The next guest sees those nights greyed out.
Now the detail. It's a Next.js site hosted on Vercel, and the blocked nights sit in a Postgres database on Neon. The emails go out through Resend, and date-fns does the date maths. The owner's page sits behind Clerk sign-in, and the route that saves blocked nights checks for a signed-in user itself.
The biggest call was what to leave out. We first built a fuller dashboard, with bookings, enquiries and pricing. Then we cut it back to one screen for blocking dates, and let requests travel by email. One owner looking after their own stays didn't need another system to manage.
The calendar gets its blocked nights from a public route. That route returns dates and nothing else: no guest names, and no reason a night is blocked. Blocked nights can show when a place is empty or closed, so it's best that the route says nothing more.
Nightly prices come from the database too, with defaults built in if it has none. So the review step shows an estimated total, and the owner arranges the real payment when they reply.
Dates get careful handling. Each blocked night is stored as a plain date for one stay, with no time of day. The request sends plain dates as well, and the server counts nights in calendar days. So the owner's email shows the dates the guest picked, whatever time zone the guest is in.
It's been live since September 2025, and we still host it. The site doesn't save requests, so there's no count of them, and we didn't measure bookings before it went live. So there's no before and after to show you.
If you run your own stays and you want guests asking for dates on your own website, get in touch.
The request goes to the owner by email, and nothing is booked until the owner replies. The owner keeps the calendar right from one private page where they block and unblock nights. The site takes no payment.
How and why they came
They saw one of our ads and rang me. What they bought was a launch: a website, a Google listing, social pages and a video shoot, and along the way a new domain and mailbox. This page is about the website's booking side.
The website was meant to be a single landing page. It grew into a full site, with a page for each stay and a four-step booking request flow.
The problem
The owner runs the stays themselves. They needed guests to see which nights are free and ask for the nights they want. Then the owner decides, confirms the stay and bills the guest themselves.
So the site had to take requests, not payments, and leave every yes or no with the owner.
What we built
- 1
A four-step request flow
Choose a stay, pick dates, add guest details, then review and send. On a phone the steps show as a progress bar.
- 2

A calendar of free nights
The dates step loads that stay's blocked nights and greys them out. It holds each stay's minimum stay and tells the guest why when they pick too few nights.
- 3

Two emails per request
The owner gets a "New Booking Request" with the guest's details, the stay, the dates and the number of nights. The guest gets a "Booking Request Received" note. The site doesn't save the request to its database.
- 4

One private page for the owner
After signing in, the owner picks a stay, clicks nights to block or unblock them, and saves. Blocked nights show greyed out to the next guest.
The request flow on a local copy, with sample data
The dates step: the chosen nights, and blocked nights greyed out.
The site we built, run locally. Sample data.
What the guest sees after sending a request.
The site we built, run locally. Sample data.
The owner's email for the request, with Reply-To set to the guest.
The system's own output. Sample data. Not sent.
The owner's page after blocking two nights and saving.
The owner's page, run locally. Sample data.
What a person still does
The owner reads each request, replies to the guest (a reply to the request email goes straight to the guest), confirms or declines, and arranges payment. They block the nights that are taken so the calendar stays right.
The technical detail
What each tool does here
Next.js on Vercel
- The site, the request flow and three small routes: one returns a stay's blocked nights, one returns nightly prices, and one sends the request emails.
Postgres on Neon, through Prisma
Resend
- The submit route sends two emails through Resend's emails.send().
- The owner's email sets replyTo to the guest's address, so a reply goes straight to the guest.1
- Resend's own guide uses the same pattern for a contact form: with replyTo set to the visitor's address, replies "go to the reply-to address instead of the form's sending address".2
Documentation
Clerk
- The owner's page sits behind Clerk sign-in.
- The route that saves blocked nights also checks for a signed-in user itself and refuses the request if there isn't one.
- Clerk's guidance is to "protect access as close to the resource as possible".1
Documentation
date-fns
- The server counts nights with differenceInCalendarDays.
- Its documentation says "the times are removed from the dates and then the difference in days is calculated".1
Documentation
Vendor links checked 16 November 2026.
Design decisions
One screen for the owner
We first built a fuller dashboard with bookings, enquiries and pricing. We cut it back to one screen for blocking dates and let requests travel by email. One owner looking after their own stays didn't need another system to manage.
The public route gives out dates only
The calendar's availability route returns a list of blocked dates for a stay: no guest names and no reason a night is blocked. Blocked nights can show when a place is empty or closed, so it's best that the route says nothing more.
An estimate, not a charge
Nightly prices come from the database, with defaults built in if it has none. The review step shows an estimated total, and the owner arranges the real payment when they reply.
How dates are handled
A blocked night is stored as a plain date for one stay, with no time of day. The guest's browser sends the check-in and check-out as plain dates (year, month, day), and the server counts the nights in calendar days. So the owner's email shows the dates the guest picked, whatever time zone the guest is in.
Where it stands
Live since
September 2025
- It's been live since September 2025, and we still host it.
- Guests use the request flow.
The site doesn't save requests, so there's no count of them, and we didn't measure bookings before it went live. There's no before and after figure on this page.
Questions
Can a holiday rental website take booking requests instead of instant bookings?
Yes. This one does. A guest picks a stay and dates and sends a request. The owner gets it by email and confirms or declines it. Nothing is booked or charged by the site.
How do I block dates on my own accommodation website?
On this site, the owner signs in to a private page, picks a stay, clicks the nights to block and saves. Those nights then show greyed out on the guest calendar for that stay.
Do guests get an email when they send a booking request?
Yes. The guest gets a "Booking Request Received" email with their stay, dates, nights and an estimated total, and the owner gets the full request.
Does a booking request site take payment?
Not this one. The review step shows an estimated total, and the owner arranges payment with the guest after confirming.
Why not use a full property management system?
On this job, one owner runs their own stays and decides each request. We built a fuller dashboard first, then cut it back to one screen for blocking dates. If you run many stays or need instant booking, the answer may be different, and we'd talk it through with you.
Run your own stays and want guests asking for dates on your own website?
Book Free AssessmentProduct names and logos belong to their owners and are shown to identify the systems connected.