By the middle of July you can answer it in your sleep. What's your rate? The honest answer is that it depends, because the room that runs two-eighty on a Saturday in August is more like one-ninety on a Tuesday in June, and you've explained that gap so many times you've stopped hearing yourself say it.
Charter captains run into the same thing with a different number. There's the four-hour trip and the six-hour trip, the peak-weekend price and the quiet-weekday price you'd love to fill. Every caller wants a number for their dates, and every answer pulls you off the dock, or out of a room you were turning over, to go look it up.
The price isn't a secret, and it isn't really complicated once it's written down. The trouble is you keep handing it out by hand, one call and one text at a time, from Memorial Day clear to Columbus Day. A simple auto-reply, which is just a message that sends itself when someone asks, can read the dates in the question and send back the matching price. The question starts answering itself, and you get your afternoon back.
Write the price down once, the way you really charge
Before any software touches this, give it twenty minutes with a pen. Write out how you actually price, not the tidy version you wish were true. Most inns and boats carry three or four prices and a couple of rules, and the whole thing fits on an index card once you stop keeping it in your head.
You're after a small grid. Down one side, your seasons with real dates. Across the top, the day of week. In the middle, the number.
- Your seasons, with exact start and end dates. Peak might run the last week of June through Labor Day, shoulder the weeks on either side, off-season the long quiet stretch after the leaves turn.
- Weekday versus weekend. A Friday or Saturday in season almost never costs the same as a Tuesday, so spell both out.
- Your minimums. Two-night minimum on summer weekends, a trip minimum of so many people, whatever you hold firm on.
- What's included. Tax, cleaning fee, fuel, bait. The number you quote should be the number they'll actually pay.
Write it so a stranger could read it and quote a price without calling you. That's the test. If you can hand the card to a new front-desk hire in April and they get it right, the software will get it right too.
Let the reply read the dates and answer
Once the grid exists, the setup is small. You're giving people two easy ways to ask and wiring both to the same price list.
On text, it's a reply that watches for the question and the dates. Someone texts your number asking about the second week of August, and the reply reads those dates, checks the grid, and sends the matching rate back in a few seconds. On the web, it's a short form on your site, maybe three fields: arrival, departure or trip length, and party size. They pick the dates and the price shows up on the same page, no waiting for a callback.
Either way, the caller gets a straight answer at ten at night when you're asleep, and you wake up to a quote already delivered instead of a voicemail asking for one. Figure most of the rate questions that used to ring your phone now never do.
Say plainly where a person still signs off
This is where being honest pays off. An auto-reply is good at the clean cases and bad at the odd ones, and you want it to know the difference rather than guess.
Set it to quote the straightforward dates and to stop short on the ones that need you. A few that almost always need a person:
- Holidays and event weekends. July 4th, a local festival, the weekend of a big wedding in town. These don't follow the normal grid, and you may not want them to.
- Group blocks and whole-house bookings. Four rooms for a family reunion, or a private charter for a company outing, usually get a conversation, not a sticker price.
- Anything outside the rules. A one-night stay on a two-night weekend, an off-hours trip, a special request riding along with the dates.
For those, the reply should say so in plain words and promise a real answer soon. Something like: those dates look like a holiday weekend, so let me confirm the rate and get right back to you. The caller isn't left guessing, and you're not on the hook for a number the machine made up.
The one line that turns a quote into a held booking
A price by itself is just information. The caller reads it, likes it or doesn't, and either way they go quiet while they think, or while they text the next place down the road. You've answered the question and gotten nothing for it.
One line fixes that. After the number, add the next step and make it easy to take:
That's $240 a night for those dates. Want me to hold them for you? Reply YES or book here.
Now the quote has somewhere to go. The ones who are ready say yes on the spot, and you've turned a question you used to answer for free into a booking on the calendar. The ones who aren't ready still have your number and a price they trust, which beats a guess and a maybe.
Worth doing this week
You don't need to build the whole thing at once. Start here:
- Write the index card. Seasons with dates, weekday and weekend prices, minimums, what's included. Twenty minutes, done once.
- Pull the three or four questions you answer most, in the exact words callers use. That's what the reply has to recognize.
- Pick one channel to start, text or a web form, and wire it to the card. Add the other once the first one's humming.
- Write your holiday and group handoff line, so the odd cases get a person instead of a wrong number.
- Add the hold line to the end of every quote. It's the part that pays for the rest.
Wiring up a rate reply is small, unglamorous work, the kind we set up for Massachusetts inns and charters so the rate question stops eating their summer. Do it in the shoulder season, while the phone's quiet, and it's quietly working the day the first warm Saturday fills the lot.