PlaybookEnquiries & use cases

Build a receptionist for a local business

Configure the business’s routine answers, booking method and callback process. The steps cover the knowledge, request summary and tests needed for a receptionist the team can use.

In this guide

What you’ll finish with

A tested receptionist that answers routine questions and collects useful enquiries for the client’s team.

Before you begin

  • Approved service, location and opening-hours information.
  • A booking method or a named enquiry owner.
  • A client workspace with Website Chat.

Agree the first customer journey

Choose the service the receptionist should support first. A visitor might be checking whether the business serves their area, asking about a service or requesting an appointment. Write down the answer source and next step for each of those questions.

Ask the client who handles follow-up and when. Set an honest expectation for after-hours enquiries rather than assuming the business can respond immediately.

Example service brief

Help visitors understand our services, opening hours and service area. Answer from the approved information. Offer the configured booking route for suitable appointments. When a visitor wants the team to contact them, collect a request with their name, contact method and a short description of the service they need.

Prepare the shared business information

In KugaClient workspace › Business

Review the business description, location and contact information. Under Knowledge, connect the approved website and upload any current service document needed for answers.

Test facts that often change, such as holiday hours, service areas and published prices. If the client has not supplied a price or availability, use an enquiry or booking route rather than inventing it.

  1. Confirm shared business details.
  2. Connect the relevant pages under Knowledge.
  3. Review the scan and important pages.
  4. Ask test questions about hours, location and the selected service.

Configure enquiry capture

In KugaClient workspace › Actions › Collect enquiries

Open Actions, choose Collect enquiries and define when the agent should offer follow-up. Kuga saves Name, Contact method and Request summary. Ask for the context the team needs and include it in the summary.

Keep the conversation proportionate to the job. A local service enquiry may only need the service, area and a brief description. A long questionnaire can make a simple request harder to complete.

Example Contact Requests instructions

Offer to collect a request when the visitor asks for a quote, a callback or help that the approved information cannot answer. Ask what service they need and their location when it affects the service area. Collect their name and preferred contact method. Save a concise summary of the request. Explain that the team will review it using the details provided.

The request summary carries the context collected in the conversation. The saved field structure stays consistent.

Add the booking method where it fits

In KugaClient workspace › Actions › Book appointments

In Actions, use Book appointments for an approved appointment process. A booking page lets the visitor choose a time externally. A connected Cal.com account can offer live availability and booking in the conversation. Choose the method the client will maintain.

Write the Scheduling instructions to say when booking is appropriate. For questions requiring a preliminary review, collect an enquiry instead of directing every visitor to the calendar.

  • The booking destination belongs to the client.
  • The offered appointment type matches the service.
  • The workflow explains when to offer it.
  • The completed test reaches the expected booking outcome.

Set the messenger and test the boundaries

In KugaClient workspace › Agent › Configuration

Use Agent Configuration for concise response instructions, then Messages in Website Chat’s Customise tab for the opening message. Keep the opening invitation specific to this business, such as services and appointments.

Run routine questions, an unclear enquiry, a request outside the service area and a question requiring professional judgement. Use the client’s approved response for those boundaries. If Human Handover is part of the service, configure and test it separately on Advanced.

  • A routine answer matches the source.
  • The agent asks a useful clarification.
  • An unsuitable enquiry follows the agreed response.
  • The saved request is useful to the client team.
  • The opening message and placement work on mobile.

Review the first live conversations

In KugaClient workspace › Website Chat › Conversations

After installation, review the questions customers actually ask. Note where a source needs updating, an instruction is unclear or the next step feels unnecessary. Make the smallest relevant change and repeat the affected test.

Use the client’s feedback on enquiries to improve the summary requirements. Review activity and confirmed outcomes separately when preparing the monthly update.

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.