PlaybookEnquiries & use cases

Help couples explore a venue and arrange a viewing

Use the current brochure to answer venue questions, then offer the approved viewing or enquiry route. Keep viewing appointments separate from wedding date availability and reservations.

In this guide

What you’ll finish with

A venue assistant with current package information and a tested route to a viewing or enquiry.

Before you begin

  • The current approved brochure and venue pages.
  • An agreed viewing calendar or enquiry process.
  • Approved wording for wedding date availability and reservations.

Prepare the current venue information

In KugaClient workspace › Knowledge

Connect the venue’s approved pages and upload the current brochure when it contains useful package details. Record which year or season a price applies to. Remove superseded brochures from the active source set.

Check capacity, ceremony options, accommodation and supplier policies with the venue. If the brochure does not answer a specific request, collect an enquiry rather than adding assumptions.

  • The brochure is the current approved version.
  • Package prices retain their stated conditions.
  • Capacity and access details have been checked.
  • Unpublished arrangements have a clear enquiry route.

Explain the distinction between viewing and reservation

In KugaClient workspace › Agent › Configuration

Tell the agent what it can confirm. A connected viewing calendar provides appointment availability for that viewing type. It does not establish whether a wedding date is free or place a reservation on the venue.

Ask the venue for approved wording when couples ask about their preferred date. Use the team’s confirmation process unless a separately supported live source actually supplies that information.

Example response instructions

Help couples understand the venue using the current approved pages and brochure. Keep package conditions and dates attached to their prices. Offer the configured route to arrange a venue viewing. Do not claim that a wedding date is available or reserved from a viewing calendar. For preferred wedding dates or bespoke arrangements, collect an enquiry for the venue team.

Configure the viewing route

In KugaClient workspace › Actions › Book appointments

Use the venue’s approved booking page or connect the appropriate Cal.com appointment type. Write the workflow to offer a viewing when the couple wants to visit, rather than at the end of every venue question.

Complete a test of the configured route. Check the appointment name, timezone, confirmation and any instructions for arriving at the venue.

  1. Confirm the viewing appointment type with the venue.
  2. Configure the booking destination or connection.
  3. Write when to offer a viewing.
  4. Test the availability and completion process.

Scheduling is configured for the agreed appointment. A venue viewing and a wedding reservation are different processes.

Collect useful venue enquiries

In KugaClient workspace › Actions › Collect enquiries

When a couple wants a reply from the venue, collect the context the team needs. A preferred wedding date or season, approximate guest count and the main question can make the first response more useful.

Save that context in Request summary with the name and contact method. Keep optional preferences optional and make the next step clear.

Example venue enquiry instructions

Collect a request when the visitor wants the team to confirm a wedding date, discuss a package or answer a bespoke question. Ask their preferred date or season and approximate guest count if known. Collect their name and contact method. Summarise the main question and relevant preferences. Explain that the venue team will review the enquiry. Do not confirm a reservation.

Test a realistic set of questions

In KugaClient workspace › Agent › Configuration

Ask about a package, a price for a different year, an uncertain guest count, a preferred wedding date and a viewing. Check each answer against the current source and workflow.

Open Contact Requests to inspect a complete example. Have the venue team confirm whether the summary gives them enough context for a helpful first reply.

  • Package information comes from the current brochure.
  • Price conditions are retained.
  • A viewing uses the correct appointment route.
  • Wedding dates are not falsely confirmed.
  • The enquiry summary contains useful context.

Plan the seasonal review

Agree when the venue publishes new brochures, prices and viewing availability. Update the sources and Scheduling configuration at those points, then repeat the affected tests.

Use the monthly conversation review to identify recurring questions missing from the brochure. Record enquiries and booked viewings separately from confirmed wedding bookings.

Pick a client you know.

Show them their AI.

Use their website to build a demo. Put your name on it and let them try it.