Keep Your Campground PMS—Fix the Phone: When AI Front Desk Is Enough
Saturday, 4:40 p.m. The grid is honest. Site 18 is a 50-amp pull-through, pets allowed, open Sunday night. You already paid for that software. Then the office line rings while you are at the dump station with a fifth-wheel that will not clear the elbow. Voicemail takes it. You are not migrating a PMS in July.
Keep the PMS when the calendar, rates, and site map already work. Fix the phone when missed calls still empty sites. Add an AI agent only when it can read live inventory, answer pull-through, 50-amp, and pet questions, and write a hold into the system you already run. A rip-and-replace is a different job, for a different season.
TL;DR
- Phone is still a booking door. RoverPass's 2025 mix is about 60% online direct and 29% phone. Walk-ins are basically gone. Voice is not.
- A keep-your-PMS overlay already exists in human form: campground answering services that book in the reservation software you already have, often inside 48 hours, not a six-week cutover.
- PMS replacement has its own bill. Setup, export rights, contracts, and off-season timing sit next to the new invoice. Do not start that project because the phone dumped one Saturday.
- Hospitality vendors already sell "works alongside your existing PMS" in hotels (Grevon). That is a category. It is not a campground integration list. Test writeback on your sites.
- Before you trust any phone brain, make it answer pull-through, hookups, and pets and put a hold on the staff calendar (webhook test).
- Lunaria Connect is the keep-your-PMS path. Lunaria Booking is the full PMS plus the same agent craft. Do not buy a layer that cannot write a hold and call it booking.
When is the calendar fine and the phone the actual leak?
The calendar is fine when staff trust the grid, rates match what you quote, and a guest site can already hold a pad. The phone is the leak when those tools sit idle while a booking-ready caller hits voicemail, a busy desk, or a bot that cannot see site 18.
RoverPass's 2026 report is first-party platform data, not a national census. Still, the shape is useful: online direct around 60%, phone around 29% and slightly up year over year, walk-ins near zero. The phone did not die when the website started taking cards. It stayed the door for the driver who needs 50-amp, two dogs, and tonight.
Firefly's ops writeup puts a staff cost on that door: 5 to 10 minutes per phone reservation. Peak season, that is hours at the desk reciting hookups. Online booking steals some of those rings. It does not steal the guest who will not tap a map until someone says the pull-through will clear a 38-foot fifth-wheel.
The leak test is boring and local:
| Signal | Calendar is the problem | Phone is the problem |
|---|---|---|
| Double books | Grid lies, two sources of truth | Hold never got typed |
| Empty Friday | Rates or LOS rules wrong | Missed calls, after-hours voicemail |
| Angry gate | Site type / amps wrong in PMS | Voice promised a pad the grid never saw |
| Staff complaint | "I fight the software all day" | "I cannot leave the window" |
If the left column is quiet and the right column is loud, keep the PMS. Fix the call. That is the same missed-call math we already taught: the cost is the booking that left, not the ring.
What does replacing a campground PMS actually cost you?
Replacing a campground PMS costs more than the new subscription. You pay mapping, training, parallel run, and the season you pick to cut over. If the grid already books, that bill is optional this year.
PitchCamp's 2026 cost guide is vendor copy. Use the questions, not the pitch. Enterprise setup often lands in the $500 to $5,000 band. Ask, in writing: can you export the full guest list and reservation history? Is there an exit fee? What is the contract length? Vendors like to time the switch for off-season. PitchCamp claims most parks finish in one to two days. Treat that as a sales number until you have watched your own export.
Our 3-year cost sheet is the other half: flat vs per-booking vs marketplace take. Switching cost sits beside that math. You still have to remap 40 pull-throughs, 30-amp vs 50-amp, pet fees, loop names, and next summer's seasonal contracts. Staff have to stop hunting the old grid during check-in.
Peak-season rip is how you get a double book on a holiday weekend. If the PMS is the leak (locked rates, no export, site types that lie), plan a real fit test for the shoulder. If the PMS is not the leak, do not start an RFP because an AI demo was pretty.
What can a phone layer do without becoming the system of record?
A phone layer can answer, qualify, hold, and hand off while the PMS stays the calendar. It cannot invent inventory. If it cannot read live sites and write a reservation the staff grid shows, it is a receptionist with a nicer voice.
Campgrounds already buy this as humans. Campground Support books in the reservation software you already run, lists experience with 12 programs, and says most parks stand up in 48 hours. Hours are 8 a.m. to 11 p.m. CT, not true 24/7. Seasonal parks use it when the office is closed. That is the keep-PMS pattern: overflow that types into your system of record.
AI is the same job with different hours and a different failure mode. Hotels already hear "works alongside your existing PMS" (Grevon). Translate, do not copy. Those integration names are hotel stacks. Your park still has pull-through length, 30/50 amp, and a pet policy the hotel agent never saw.
What the layer is allowed to do:
- Answer "is a 50-amp pull-through open Friday, two dogs?"
- Hold the pad in the PMS, or say it cannot and hand off.
- Send a payment link or take a card the way your current software already takes money.
- Leave a clean note: dates, rig, hookup, pets, callback.
What it is not allowed to do:
- Quote a rate the grid does not have.
- Promise site 14 when the adapter is read-only.
- Become a second calendar in a spreadsheet.
After-hours booking is the same rule at 11 p.m. A greeting is not a reservation. A lockbox is not a reservation. Something still has to write the calendar and collect money.
How do you tell a bolt-on from a stealth PMS swap?
A bolt-on keeps your system of record and proves writeback. A stealth swap asks you to live in a new calendar, new rates screen, and new guest site, then calls it "just the phone."
Run this table on the vendor, not on the demo reel.
| Question | Bolt-on (keep PMS) | Stealth swap |
|---|---|---|
| Where does the hold appear? | Staff grid you already open at 7 a.m. | Their new dashboard |
| Who owns rates and LOS? | Your PMS | "We will sync later" |
| Guest website | Stays yours, or they admit it is a new book path | New booking engine in the first call |
| Enemy they name | Missed calls, voicemail, dumb bots | Your current PMS |
| Exit | Unplug the phone adapter | Export project |
| Proof this week | Test hold on site 18 | Six-week onboarding |
Answering services fail this test when they email you a reservation to type. They pass when they log into your software. AI fails when it chats about 50-amp and never writes. It passes when the night agent’s hold is sitting on the grid before you open the office.
If the pitch leads with "modern campground PMS" and a feature grid for rates, maps, and channel managers, you are not buying a phone fix. You are buying a migration. That can be the right buy. It is not this article’s buy. Name it.
Lunaria splits the two products on purpose. Lunaria Connect is AI phone and chat that attach to the PMS you already run, when that adapter can see inventory. Lunaria Booking is the PMS plus the same agent. If a salesperson collapses those, they are selling the wrong door.
What must the agent write back before you trust it?
The agent must put a real hold on the staff calendar, with the right site type, dates, and money path, before you point the published number at it. Anything less is a script with a phone line.
Test in this order. Do not skip to brand voice.
- Read. Ask for a 50-amp pull-through, Friday to Sunday, two pets. The answer must match the grid, not last year’s brochure.
- Refuse. Ask for a 40-foot rig on a 32-foot back-in. A good agent says no. A bad agent books it.
- Write. Complete a test stay. Walk to the office computer. The hold is there, or you hang up on the vendor.
- Pay. Card or payment link, the same way your PMS already takes deposits. A "we will send a form" is not closed.
- Handoff. Ask something the agent must not guess (soft pad after rain, a ban on generators in loop C). A human gets the call with the notes.
We already wrote the site-specific accuracy bar and the webhook / calendar test. Reuse them. If the integration is read-only today, say that out loud. A read-only night agent can answer hours and pet policy. It cannot sell Saturday. Do not market it as booking.
Honesty beats a demo. Campground Support’s humans type into your software. Your AI should too, or you still have a receptionist.
When should you replace the PMS instead of bolting on?
Replace the PMS when the system of record is the thing that lies, locks, or cannot export. Keep it when the grid is trusted and the only hole is a human who cannot be in two places.
Swap is the job when:
- Staff fight the software more than the phone.
- You cannot export guests and history in a normal file.
- Site types, amps, and pet rules live in someone’s head, not in the record the website reads.
- Rates and LOS cannot be changed without a vendor ticket.
- The guest site cannot finish a stay on a phone, and the PMS vendor will not let you fix that.
Bolt-on is the job when:
- The grid matches the loop.
- Online already takes a share of nights.
- The wound is missed calls, lunch overflow, and after-hours.
- You will not cut over in July.
Those are different seasons. A keep-PMS phone layer in May does not block a PMS fit test in November. A mid-season rip to "get AI" is how you empty a loop you already knew how to run.
What should you do this week?
Do not issue an RFP. Measure the leak, then run one bake-off that writes a hold.
- Pull 14 to 30 days of phone logs. Count missed, voicemail, and after-hours. Use the missed-call worksheet: booking-related share × conversion × your ADR × nights. That number is the budget for overflow, not for a new PMS.
- Call your published number at 8 p.m. If it is voicemail, the night door is closed. Write that down before a vendor tells you otherwise.
- List what the PMS already does well: calendar, rates, site map, payments. If that list is long, you are in bolt-on territory.
- Ask one answering service and one AI vendor the same five questions: 50-amp pull-through, two dogs, tonight, pet fee, "put it on the grid." Whoever cannot write the hold is a receptionist.
- Create a test reservation yourself. Confirm it on the staff calendar. If it is not there, do not point the real number.
- Pick one policy that disagrees between the website and the voice (pets, hookups, check-in). Put the true version in one place both doors read.
- If the PMS itself failed the list in step 3, put a shoulder-season fit test on the calendar. Do not start it this Saturday.
Lunaria Connect is the keep-your-PMS product: phone and chat that attach to the system of record you already run, when the adapter can actually see inventory. Lunaria Booking is if you want the PMS too. Either way the bar is the same. The agent reads pull-through and 50-amp from the same truth as the grid, writes a hold, and hands off what it must not guess.
FAQ
Can I add AI phone without switching PMS?
Yes, if the adapter reads live inventory and writes a hold into the software you already run. That is the keep-PMS pattern campground answering services already sell. If the vendor needs you to live in a new calendar, you are switching PMS whether they say so or not.
Will the AI double-book if it cannot write the calendar?
Yes. A voice that quotes site 18 without a hold is how you get two fifth-wheels at the gate. Read-only Q&A is allowed for hours and pet policy. It is not allowed to sell Saturday. Test writeback before you publish the number.
Is an answering service the same as AI front desk?
No. Both can keep your PMS. A human center like Campground Support types into your reservation software on set hours. AI can cover the rest of the night if, and only if, it writes the same grid. Compare them on site answers, hours, and a test hold, not on "robots vs people."
When is PMS replacement the right move?
When the grid is the liar: no export, rates you cannot change, site types that do not match the loop, a guest site that cannot book. That is a fit-test, usually in the off-season. It is not the fix for a Saturday voicemail.
What if my PMS has no API?
Then you still have humans who can log in, which is how answering services already work. AI that cannot see the grid should not take the published line. Do not accept "we will email you the reservation" as booking. Demand a path that lands on the staff calendar, even if that path is a trained person this season.
Does Lunaria Connect replace Lunaria Booking?
No. Connect is AI on top of the PMS you keep. Booking is the PMS plus the same agent craft. If you are happy with the calendar and angry at the phone, Connect is the door. If the calendar is the problem, Booking is the door. Do not buy one to get the other.
What should stay human?
Anything the record does not know: a soft pad after rain, a regular who always gets loop C, a generator fight, a medical pull-in at 11 p.m. The agent should hand those off with notes. Staff should not sit on "is 50-amp open Friday" if the grid already knows.
---
Keep the PMS if it already tells the truth. Fix the phone if that is where the money leaves. The agent earns the line when site 18 shows up on the grid, with the right hookup, before you open the office.