PlaybookEnquiries & use cases

Prepare a property enquiry assistant

Connect approved property and agency information, then collect useful viewing or valuation enquiries. Keep listing availability and appointment confirmation tied to the agency’s actual process.

In this guide

What you’ll finish with

A property assistant that answers approved questions and passes a useful, accurate enquiry to the right team.

Before you begin

  • Approved agency and property information.
  • Separate processes for viewings, valuations and general enquiries.
  • A named person responsible for keeping listing information current.

Choose the enquiry types to support

Start with the journeys the agency already handles. A buyer asking about a specific property needs a different next step from an owner requesting a valuation. Record the information and follow-up owner for each journey.

Use the agent to organise the enquiry. Avoid asking it to decide whether someone qualifies for a home, can afford a mortgage or should make a particular offer.

EnquiryUseful context
ViewingProperty reference, preferred times and contact details
ValuationProperty area, broad property details and preferred contact method
General searchRequested area, property type and preferences the visitor chooses to share

Connect approved information

In KugaClient workspace › Knowledge

Connect the agency’s service pages and any approved listing pages within the website source scope. Review the scan and check that the important pages have been included. Add a current approved document only where it supplies information missing from the website.

Website knowledge should not be presented as a live property availability feed. Define who updates the source and how often it is checked. If the agent cannot confirm whether a property remains available, direct the enquiry to the agency.

  • Service areas and office details are correct.
  • Property references can be traced to an approved source.
  • Outdated listings are removed from the source scope.
  • The fallback for unconfirmed availability is agreed.

Configure the enquiry summary

In KugaClient workspace › Actions › Collect enquiries

Write the capture instructions around the enquiry type. The saved request contains Name, Contact method and Request summary. Put the property reference and any relevant preferences in the summary.

Collect only what the team needs for an initial response. A public property chat is not an application form or a place to collect identity documents, financial records or a full tenancy history.

Example property enquiry instructions

When a visitor asks the agency to arrange a viewing or valuation, collect a request. For a viewing, ask which property they mean and note preferred times without promising availability. For a valuation, ask the property area and a brief description. Collect their name and preferred contact method. Include the enquiry type and relevant context in the summary. Do not make eligibility, affordability or offer decisions.

Include the property reference and enquiry type in the summary so the team can act on the request.

Choose the appropriate appointment route

In KugaClient workspace › Actions › Book appointments

Use Book appointments only for appointment types the agency has approved for direct booking. A general valuation consultation may use a booking page or connected Cal.com availability. A viewing that requires an agent to confirm access may need a Contact Request instead.

Describe the distinction in the workflow. A preferred time in an enquiry is a request, not a confirmed appointment. Check the completion wording for both routes.

  1. Confirm which appointment types can be booked directly.
  2. Configure the approved booking destination.
  3. Write when the agent should offer it.
  4. Test a direct booking and an appointment requiring confirmation.

Test with the agency before installation

In KugaClient workspace › Agent › Configuration

Test a specific listing question, an unavailable property, a valuation enquiry and an ambiguous viewing request. Ask a question about an unsupported property and confirm that the agent does not invent details.

Inspect the saved requests with the agency. They should distinguish the property, the purpose of the enquiry and the requested follow-up without claiming that a booking has been confirmed.

  • A listing answer matches its source.
  • Unconfirmed availability is explained accurately.
  • A viewing request contains the property reference.
  • A valuation request reaches the agreed team.
  • Sensitive application details are not requested.

Maintain the listing and follow-up process

Review new conversations as listings and instructions change. Remove superseded source material and retest affected questions. Ask the agency whether the summaries help the team respond.

Report captured enquiries separately from confirmed appointments or instructions won. The latter outcomes need confirmation from the agency’s own records.

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.