In this guide
What you’ll finish with
A clear response policy with tested transitions between answering, booking and collecting an enquiry.
Before you begin
- The client’s common customer questions.
- Approved answer sources.
- An agreed booking and follow-up process.
Define the main customer task
Ask the client which conversations they want the service to handle. A shop may primarily need product and policy answers. A property agency may need valuation enquiries. A venue may need both information and a route to arrange a viewing.
Write the intended result for a few common questions. The best next step depends on what the visitor asked, rather than on a general instruction to collect everyone’s details.
| Visitor intention | Useful next step |
|---|---|
| A factual question with an approved answer | Answer it and offer relevant context |
| A suitable appointment request | Use the configured Scheduling route |
| A request for a quote or callback | Collect a Contact Request |
| A question requiring the client’s judgement | Use the approved contact or available handover process |
Prepare the answer sources
In KugaClient workspace › Knowledge
Connect current service pages, policies and approved files. Write the Knowledge instructions to explain how the agent should answer and handle gaps. Review Business details for shared facts about the client.
For a shop, use Catalog for supported product connections rather than treating an old file as live stock information. Keep order-specific information outside the catalogue’s role unless a separately supported process supplies it.
- Routine questions have an approved source.
- Important policies are current.
- Unknown information has an agreed fallback.
- Dynamic store information uses the appropriate connection.
Set the enquiry trigger and summary requirements
In KugaClient workspace › Actions › Collect enquiries
Describe the visitor intentions that should produce a request. Tell the workflow what context is needed for follow-up, then collect the name and contact method. The additional context is saved in Request summary.
Use Agent Configuration to reinforce the general response style. Keep the detailed capture process in the Contact Requests workflow so it can apply to the client’s supported chat channels.
- Open Actions and choose Collect enquiries.
- Describe when the visitor should be offered follow-up.
- Name the context needed in Request summary.
- Save the instructions and complete a test enquiry.
Balanced capture instructions
Answer routine questions from approved information. Offer to collect a request when the visitor asks for a callback, a quote or help the available information cannot provide. Ask for the context needed by the team, then collect a name and contact method. Do not request contact details just because a routine answer has been completed.
Ask for enough context to follow up
In KugaClient workspace › Actions › Collect enquiries
Decide which details belong in the request summary for each type of enquiry. A visitor asking for a property valuation can give the area and property type. A visitor asking to visit a venue can give a preferred date and guest count.
Review the first requests with the client and adjust the questions if the team needs different information.
Test the transitions in both directions
In KugaClient workspace › Agent › Configuration
Ask a simple factual question and confirm that it receives an answer without an unnecessary capture request. Then ask for a quote or callback and check that the agent collects useful context and saves a request.
Try an unclear intention and a missing answer. The agent should ask a relevant clarification or follow the approved fallback. Recheck the saved request and booking route when those paths are used.
- The agent answers routine questions without asking for contact details.
- A clear enquiry reaches Contact Requests.
- The summary is useful to the client.
- A booking offer fits the enquiry.
- Unknown questions do not produce invented certainty.