PlaybookEnquiries & use cases

Collect useful enquiries after hours

Collect a job description and contact details when the office is closed. Configure service coverage, notifications and approved callback wording without implying that a request books a visit.

In this guide

What you’ll finish with

An after-hours enquiry process with useful job summaries and client-approved response expectations.

Before you begin

  • Current service areas, working hours and service information.
  • Approved wording for urgent or unsupported situations.
  • A callback owner and an agreed notification route.

Agree what happens outside working hours

Ask the business which jobs it accepts, where it operates and when it reviews new enquiries. If it offers an emergency service, obtain the exact approved contact process and wording.

Record the distinction between a routine callback request and the client’s urgent contact route. The agent cannot guarantee attendance or assess a situation simply by gathering a description.

Example follow-up brief

Collect routine enquiries for the office to review during its agreed working hours. Explain the next step using the client’s approved wording. Do not confirm a visit, quote or response time that has not been supplied. For urgent situations, use the approved contact instructions without inventing safety advice or promising dispatch.

Prepare services and coverage

In KugaClient workspace › Business

Review the business details, then connect approved service and coverage pages under Knowledge. Add a current service-area document if the website does not explain the relevant postcodes.

Test coverage at the boundary of the service area. When a postcode or service is unclear, collect an enquiry for review rather than confidently accepting a job the business may not support.

  • Opening hours reflect the current operation.
  • Service coverage is supported by an approved source.
  • Published prices are used only in their stated context.
  • Unsupported services have a clear response.

Write the job enquiry workflow

In KugaClient workspace › Actions › Collect enquiries

Ask for a short job description, the postcode and a broad timescale where useful. Collect the name and contact method, then save the job context in Request summary.

Avoid a long diagnostic conversation. The initial enquiry should help the business decide how to follow up, without asking the visitor to carry out checks or supplying technical instructions that the client has not approved.

Example enquiry instructions

When a visitor wants a quote or callback, ask what work they need and the property postcode. Ask their preferred timescale if it helps the office organise follow-up. Collect their name and contact method. Save the job, area and timescale in the summary. State the approved next step. Do not diagnose a fault, promise a price or confirm a visit.

Keep the description concise enough for the office to review before making contact.

Configure notifications and the opening message

In KugaClient workspace › Notifications

Set the recipients who actually review new requests and send a test notification. If the request also goes to another system, configure and test the supported Webhooks event separately.

In Website Chat’s Customise tab, write a welcome that reflects the service. Use the general response instructions to explain after-hours expectations consistently, rather than relying on the welcome alone.

  1. Confirm the request owner and recipients.
  2. Save the relevant notification settings.
  3. Send and check the test email.
  4. Write the messenger welcome.
  5. Test the expected after-hours confirmation.

Test the edge cases

In KugaClient workspace › Agent › Configuration

Run a supported job, an out-of-area request, an urgent question and an enquiry without a clear postcode. Check the agent’s response against the business’s approved process.

Open Contact Requests after a complete test. Confirm that the team has a usable contact method and enough context to make the first call. Check that the confirmation does not read like a booked appointment.

  • The job and postcode appear in the summary.
  • The next step reflects the actual review process.
  • Urgent wording matches the client’s instructions.
  • Unsupported jobs are handled clearly.
  • A request reaches the notification recipient.

Review the first week with the office

Ask which requests required extra clarification and which were outside the service area. Adjust the questions or source information to address those gaps.

Measure requests received and callbacks completed separately. Use the office’s records to confirm appointments and completed work before including them in a results report.

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.