Is it for me? · Venues and spaces
Enquiries and dates
in one place.
Enquiry forms on your own site, every request naming which room, and the whole thread sitting against a record you can still find next year. No commission on a date you filled yourself.
Example spaces — three rooms, one inbox
In this dashboard
A June week
Nothing here is a feature. It is the week the diary fills.
Where each request lands, and the one moment the software deliberately does not decide for you.
Maya, eighty people, a note about the bar. It arrives naming the room, lands as pending, and she gets an acknowledgement before you have read it.
Lina, also the Loft, also 14 June. Both sit there. Helm does not decide between them and does not pretend one slot is gone — that judgement is yours.
Two clicks. Both are emailed. The record keeps who answered and when, which settles the question the day somebody asks.
Different room, same inbox. The Studio's history is its own, so you can see it has had one enquiry this week and the Loft has had three.
Edit the page, watch the preview, press Go Live. If the number was wrong, the previous version is still there.
You open Maya's record and last June is all there — the room, the numbers, the note about the bar. Nobody searched an email account.
An example week
The honest bit, said out loud
Two people asking for one Saturday is not a bug in this page. There is no live availability holding the date, and a venue that needs one should know that before signing up rather than after.
What it is instead
A request inbox with a confirm, a decline, an automatic reply and a permanent record — which for a room one person runs is usually the whole job.
Example inbox
The enquiry
Every date request in one inbox, not four of them.
One inbox instead of an inbox, a phone and a DM. Requests arrive with a name, a contact, a date, the room and whatever they wrote.
An auto-reply goes the moment the form is submitted, so nobody sits in silence while you check the diary — and every answer records who gave it.
Example history
The site itself
Change the rates yourself, and undo it if you were wrong.
You edit the site yourself — text, images, prices — and the preview updates as you type. Nothing is public until you press Go Live.
Every published version is kept, so a price you typed wrong at nine on a Friday is one click to undo rather than a phone call on Monday. Photographs go in once and are reused anywhere on the site, which matters when a venue is sold on pictures.
The record
The wedding you did last June, and the note about the bar.
Every enquiry attaches to a person, and people can sign in to see their own.
Their history, visible
Who they are, which room, what they asked, when, and what you said. Not a search through an email account at eleven at night.
They can sign in
Accounts on your own domain, so a returning client opens their own requests instead of emailing to ask what was agreed.
One record, not three
The enquiry, the account and anything else they do are rows against the same person — which is why next March takes ten seconds.
Before you start
What this does not do, said now rather than later.
No live availability calendar
There is no calendar holding real-time inventory, no capacity and no double-booking guard. Two people can ask for the same Saturday and you decide. If you need a seating engine, this is not one.
No deposits or payments
Helm does not take a card payment or hold a deposit against a date. Requests and records.
Bookings is switched on for you
It is not on a checkout page — it opens a public write endpoint, so we turn it on per account rather than leaving it armed for every client. It is switched on during setup if your site needs it.
Getting started
Tell us about the space, and we will build around how you let it.
Plans start at $20 a month. Bookings is switched on for your account rather than bought from a pricing page.