01 / Get the details together
A little preparation.
A clearer start.
Use this checklist to collect the decisions and information your setup will need.
Your fields and locations
Names, addresses, directions, parking and any shared entrances.
Your booking rules
Opening hours, visit lengths, buffers, prices, dog limits and change or cancellation rules.
Your visitor experience
Branding, arrival instructions, gate details and the messages visitors should receive.
Your team and payments
Who needs access, who will manage the setup, and the payment-provider account you intend to use.
02 / If you already take bookings
Plan the switch
around the visits.
Your existing bookings need a clear home throughout the change.
- 1
Account for existing bookings
List future reservations, credits and outstanding refunds. Agree what can be transferred and what must remain in the original system. Keep a copy of your records.
- 2
Agree the changeover
Choose when to change booking links. Decide how existing reservations will be represented so already-booked times are not offered again. Confirm how earlier payments and refunds will be managed.
- 3
Check the complete journey
Review availability, prices, messages, visitor links, payment configuration and gate arrangements. Complete the agreed checks before opening the new booking route.
Confirm the migration scope first. Import tools, supported records and assisted services must be checked for your current system. This review does not transfer bookings, balances or payment history.
A useful start,
at your own pace.
Sample data would give dashboards and reports something meaningful to show. Your own organisation settings would stay separate.
- 1Create your organisationVerify your account and add the organisation you run.
- 2Explore and configureUse fictional visits to understand the tools, or build your own blank setup.
- 3Review before launchChoose a membership, connect payments and explicitly activate when ready.
Sample data should be useful and easy to leave.
Clearly fictional.
Example visits and history would be labelled throughout. No real customer details, payments, messages or gate commands.
Separate from your setup.
Your own fields, settings and records would not be mixed with the sample operation.
Remove or restore it.
The proposed controls would remove only sample records and let you restore the sample workspace later.
Sample provisioning, isolation and remove/restore controls still require application implementation and validation.
Ready to tell us about your fields?
Register interest while you prepare your setup.