Your park, open at 11 pm.
A traveler finds your page, sees the price your office would have quoted, and books. You find out in the morning, on the grid, with the deposit already taken.
Book a stay the way a traveler would at 11 pm.
channels landing on one thread per guest
apps a guest has to download
folio for the site and everything they buy
hours a day your page is quoting
Before, during, and the part after they park.
A booking page is the easy half. The rest is the two weeks they are actually with you.
One thread per guest, whatever they use.
A guest running late texts for the gate code at 9:48 pm, and whoever is on tonight has never met them. The message lands on the reservation with the context already attached.
Tap the gate code reply and the current code fills itself in, so nobody is texting last season’s number from a personal phone.
See the 9:48 pm textTap a quick reply to answer without typing.
The pass they use once they are parked.
A family in site 12 books four seats on Saturday’s kayak tour, signs the waiver on their phone, then moves it to Sunday when the forecast turns. All of it lands on the same folio as the site.
When a guest checks in, their gate code unlocks. When they ask for a late checkout, it drops into your pending requests instead of a voicemail.
See an order from site 22FolioSettles at check out
Arrival and access
Your trip
Open Events and book seats on the kayak tour.
A six month application, without a document folder.
Somebody applies for a long stay from your page. The application and screening fee is authorized at submit, identity verification runs, and your rules decide what a manager sees.
When verification comes back clean with no other flags, an optional auto advance moves it along. Everything else waits for a person, which is the point.
See long stay and seasonalApplication submitted, deposit authorizedWaiting
They apply from your booking site with their rig, term and references. The site is held and the fee and deposit are authorized on their card, not captured.
Identity verificationWaiting
CampVERIFY sends them a link. They scan a photo ID and take a selfie, and nobody at your desk handles the document.
Automatic screeningWaiting
The checklist runs against the application: identity result, documents, references, and anything else your park requires before a decision.
DecisionWaiting
Approve and the offer and occupancy agreement go out for signature, the hold becomes the deposit, and it converts to a StayLong reservation. Decline and the hold is released.
Submit as the guest. The deposit is held before anything else runs.
One guest, from a search result to checkout.
The same person, moving through five different parts of your park.
Live pricing, your map, your policies and reviews from people who actually stayed.
The reservation is on the grid, the confirmation is out and the deposit is taken, while you are asleep.
Directions, arrival window and what is open, on the thread they will use later.
The pass carries the gate code, quiet hours, the map and what is open tonight.
The ticket reaches the kitchen with the site number on it and posts to their bill.
Site, store, kitchen and tickets, settled together, with nothing walking out unpaid.
Twenty six things a guest can do without calling you.
And every one of them lands somewhere you already look.
26 things listed right there. Ask about any of them and we will show you it working on your own park, not on a slide.
A traveler sees the same price your office would have quoted, so nothing changes when they ring you.
When a guest texts at 10 pm, it lands on their booking with the context, and your internal note never goes out.
Once they are parked they have the gate code, the map, what is open, and a way to order firewood to the site.
What you get.
A clean address
Your park gets a clean address with live pricing, your map, your policies and reviews from people who actually stayed.
Empty sections hide
No photos yet means no empty gallery. CampGuide hides a section until you have something real to put in it.
Stay pass
When they check in, CampGuide unlocks the gate code, the map and ordering on the phone already in their pocket.
Waitlist
When you are full, CampGuide still takes their details and their permission, so a cancellation has somewhere to go.
How operators actually use it.
Short walkthroughs of a real situation, start to finish.
Questions operators ask.
Do I need a separate website?
No. Your park page is included, and a fuller marketing site can be generated from data you already manage.
Do guests have to download an app?
No. The stay pass opens in their phone browser, and website ordering works without an account.
How are opt outs handled?
Anyone who unsubscribed is skipped, and the composer tells you who will and will not receive a message before you send it.