Test every new Experience before making it public or sending the link to guests.
The goal is simple: confirm that guests can book the right thing and staff can operate the reservation after it is created.
Start Hidden Or Unlisted
Keep the Experience Hidden while you configure it.
When you are ready to test the guest path, switch to Unlisted and use a direct link. This lets you test the real booking flow without listing the Experience on the main public booking page.
For visibility details, see Use public, hidden, and private-link Experiences.
Test The Booking Link
Open the booking link in a private or incognito browser window.
Check:
- The correct venue appears.
- The correct Experience appears.
- The description is clear.
- Photos and guest-facing expectations are clear.
- The link works on desktop.
- The link works on mobile.
- The page does not require staff login.
For unlisted Experiences, test the exact direct link you plan to share.
For copy and photo guidance, see Make your Experience clear to guests.
Test Availability
Search for the dates, times, and party sizes guests are likely to choose.
Check:
- Expected dates are available.
- Closed days are not available.
- First and last reservation times are correct.
- The default duration makes sense.
- Larger parties use the right duration.
- The public party-size limit blocks parties that should contact the venue.
- Minimum booking notice blocks times that are too soon.
If no times appear, check schedule, table assignments, date bounds, visibility, and party-size rules. For the detailed availability setup path, see Assign tables and hours to a CoverCount Experience.
Test Tables And Staff View
Create a test reservation and confirm staff can see what they need.
Check:
- Experience name
- Reservation date and time
- Party size
- Duration
- Guest contact details
- Assigned or eligible table
- Deposit or card-hold status, if applicable
- Pre-visit question answers, if applicable
Then cancel or clean up the test reservation according to your internal process.
Test Payments Or Card Holds
If the Experience uses deposits or card holds:
- Test a party size and date that should require payment.
- Confirm the payment step appears.
- Confirm cancellation policy text appears.
- Confirm confirmation copy matches the payment method.
- Confirm staff can see the payment or hold state.
If a payment step does not appear, check that the booking method and matching deposit rule are both active.
Test Pre-Visit Questions
If the Experience asks questions:
- Confirm each question is understandable.
- Confirm required questions behave correctly.
- Confirm select options are complete.
- Confirm staff can see the submitted answers.
- Confirm the questions do not ask for information staff will not use.
Good questions help service. Unnecessary questions slow guests down.
For question setup examples, see Use pre-visit questions on Experiences.
Test The Public Launch State
When the test path works, choose the final visibility:
- Use Public if the Experience should appear on the main booking page.
- Keep Unlisted if only people with the link should book it.
- Return to Hidden if the Experience is not ready.
After changing visibility, test one more time from a guest browser.