Integrations · ParcVu
ParcVu (Booking Experts)Holiday parks and campgroundsBuilt on their own API

AI guest messaging for ParcVu holiday parks

TravelPal connects to ParcVu through Booking Experts and reads your park's rentables, bookings, and customers. It sends guest messages by email or SMS, and replies go to your team.

SystemParcVu
ConnectionReads; your team replies
AccessYour account manager turns it on
SetupFour steps

One ParcVu connection works in both directions. Each item is explained below.

Data in

What TravelPal reads from ParcVu

ParcVu is software for UK holiday and caravan parks. Booking Experts bought it in 2024. Booking Experts reports more than 800 parks and 130,000 system users across 14 countries. Parks range from 50-pitch sites up to parks above 20,000 pitches.

Rentables become properties

Booking Experts calls a unit a rentable. Each one arrives with its name, description, address, city, and coordinates. Names and descriptions come in each language. A park that keeps both Dutch and English gets one readable unit name, not the whole set. A rentable counts as live when today falls inside its active window. This is how a seasonal pitch that closes over winter stops being talked about. A rentable has no photos, no check-in time, and no check-out time. The one clock this API gives is set on the park, not the unit. It is written as a city name. So we agree arrival times, departure times, and the park's time zone with you at setup. We do not guess them.

Bookings, and the unit assigned later

A park sells a type of accommodation and often picks the real pitch or lodge later. So a booking can exist before it points at any rentable. TravelPal waits. It does not attach the guest to a category. The stay is set up once your team assigns the unit, and the next sweep picks it up. Each booking brings the booking reference a guest will quote to you. It also brings the party size, the dates, and the currency your park charges in.

Which bookings are really stays

Booking Experts publishes twenty-three reservation states. Most of them are concepts, options, and temporary holds, not a guest who is coming. TravelPal treats a confirmed booking as a stay. It stops the moment a cancellation starts, and does not wait for it to finish. It leaves a held option alone, so nobody with a basket still open gets a welcome message. Some states cannot be read with certainty. Older bookings of a freshly migrated park often arrive in such a state. TravelPal holds these and asks you. It does not send them a greeting.

Owners, guests, and the language they booked in

A booking carries an owner link for owner-occupied caravans and lodges. It is the one channel difference this API states outright. So TravelPal knows when the person arriving owns the unit. The customer behind a booking is a real person record. It stays the same across that person's stays at your park. That is how a family that comes back every August is known and not met as strangers. Their language comes along too, from the set Booking Experts publishes: Dutch, German, French, Czech, Polish, and more.

The access code stays out of the concierge

A Booking Experts reservation carries the guest access code. At a park this is the barrier or door code. TravelPal removes it before the record is stored. It does this before the AI ever reads the booking, so it cannot be repeated to whoever asks. Your own arrival email keeps that job: see how TravelPal handles sensitive details.

Data out

What TravelPal writes back to ParcVu

Here is what TravelPal sends through ParcVu today, and what it leaves to your team.

Messages go out as a Booking Experts template

This API sends from templates, not free text. So TravelPal's words travel as the value of a variable inside a template made for your park. Booking Experts does the delivery itself and picks email or SMS. Every send is addressed to the booking, so the message belongs to the stay. A customer with no email address and no phone number on file is reported as unreachable. TravelPal does not skip them quietly.

Paid extras a park can really sell

TravelPal makes the offer in the message. The guest takes it on their own private link. It can be a later departure, a bike rental, or whatever your park sells. The prices are yours. Booking Experts adds extras and accommodation into one total on the booking. So TravelPal records what it sold and does not read the number back from the booking. The confirmed extra is sent to your team to apply. See how upsells work.

Sale notes reach your team

Booking Experts keeps one note field on a booking, and it belongs to your park. Writing to it would erase what your own team put there. So TravelPal leaves it alone. A sale to apply goes to your team in the channel they use, and by email.

Setup

Connected in four steps

ParcVu turns on API access for your account. TravelPal does the rest itself.

Step 1

Ask Booking Experts for app access

Booking Experts Apps is invite only. Access starts at their developer contact form. Then comes a short call about what you are connecting, and then a demo administration to install on. This is one message to your Booking Experts contact. Start it first, because the key comes out of it.

Step 2

Install TravelPal and paste the key with your park ID

The API key is issued when our app is installed on your organization. Paste it into TravelPal with the administration ID, which is the number Booking Experts uses for your park. TravelPal checks the two together against your park's own rentables before the connection saves. A key for the wrong park is caught then. It does not show up later as an empty list of units.

Step 3

Paste your callback URL into the app settings

Subscriptions are added by hand in the Booking Experts app settings. TravelPal gives you the URL to paste. The URL holds a secret of its own. A delivery that does not show that secret is refused. New bookings, check-ins, and check-outs then arrive as they happen. A sweep of your arrival window adds the stays already on the books.

Step 4

Name the message template and the variable inside it

Sending needs two things. One is the template identifier. The other is the exact name of the custom variable that carries the text. That is the body in {{ body }}. Until both are set, the connection reads your park and messages nobody. If the variable name is wrong, Booking Experts still reports success. The guest reads a template with our words missing. So the last step is one real test send to a booking of your own. Read it on the phone that gets it.

TravelPal shows the connection at every step: connected, last update, and any error in plain words. To see the other setup steps, read what onboarding involves.

Limits

What the ParcVu connection will not do

Know the limits of ParcVu before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.

Guest replies do not come back through ParcVu

Booking Experts publishes no event for an incoming message and no guest thread this connection can read. So an answer to one of our messages goes wherever your park already gets email and SMS. Your team picks it up. A guest who came through a reseller is reached the same way, by email or SMS. It is not reached inside that channel's own inbox. TravelPal's part here is to write first: arrival instructions, offers, reminders, and follow-ups on the schedule you set. See how messaging works.

Nothing is written onto the booking

TravelPal makes no date change, no arrival or departure time, and no calendar hold. A Booking Experts reservation has no arrival-window field. Channels at a park are free-text rows your own team made. No row has a fixed name for one source or another. So a booking cannot be proven to be yours to rewrite and not a reseller's. TravelPal sells an extra clean or a damage waiver and emails your team.

The template is yours, and your park can edit it

The wrapper that holds our words is a Booking Experts template your own administrators can change. A send reports success but does not return a copy of what the guest received. Agree the template before go-live. Read it again after anyone edits your park's message templates. If a variable is taken out, our words go missing from a message that looks normal.

One park per connection

Booking Experts calls a park an administration. Booking 1 at your park is a different booking from booking 1 at the park down the road. Subscriptions belong to the app, not to one park. So all the parks of a group send to the same address. TravelPal refuses any delivery that names a park other than the one it is connected to. A group with several parks needs one connection per park, so tell us the count before go-live.

When TravelPal's AI is not sure, it stops and asks your team instead of guessing. This rule is the same on every system: see the safety guardrails.

Questions

ParcVu integration FAQ

Do I need Booking Experts to switch something on before TravelPal can connect?

Yes. Booking Experts Apps is invite only. Access starts with their developer contact form and a short call. After that you get a demo administration, install TravelPal, and receive the API key. It is one message to your Booking Experts contact. Send it before anything else, because the key comes out of it.

Can TravelPal hold a conversation with a guest at our park?

Not through this connection. Booking Experts delivers our messages by email or SMS. It publishes no event for an incoming reply and shows no guest thread to read. So a reply goes where your park already gets email and SMS, and your team answers it. What TravelPal does here is write first. It sends arrival instructions, offers, reminders, and follow-ups on the schedule you set. Each one is in the language the guest booked in.

Why does TravelPal ask for a message template identifier?

Booking Experts sends guest messages from templates, not free text. TravelPal's words travel as the value of a custom variable inside a template made for your park. So the connection needs that template's identifier and the exact name of the variable. The API accepts a wrong name, and then the guest reads the template with our words missing. This is why setup ends with one real test send that you read yourself.

We run several parks. Is that one connection?

No. Booking Experts calls a park an administration, and ids are unique only inside one. So booking 1 at your park and booking 1 at the next park are different bookings. Each park is connected on its own. TravelPal refuses any event that names a park other than the one it is connected to. Tell us how many parks are in the group before go-live. We then plan the setup around it.

Does connecting ParcVu cost extra?

No. At a park a unit is a rentable. The pitches, caravans, and lodges you put on the connection are what the flat monthly price counts.

Other systems

Not the system you use?

TravelPal connects to 33 property management systems. Below are the systems closest to ParcVu in how widely they are used.

See every system TravelPal connects to

Updated

ParcVu is a trademark of its owner. TravelPal is not affiliated with or endorsed by ParcVu.

See how it works with your ParcVu units.

Book a 30 minute demo with a founder and watch it sell a late checkout.

Do you run a small hotel or an inn? In the demo, we will tell you plainly if TravelPal connects to the booking system you use today.