In this guide
What you’ll finish with
A tested enquiry route that saves the information the client needs and reaches the agreed follow-up destination.
Before you begin
- A named owner for the enquiries.
- The information needed for the first follow-up.
- Pro or Advanced if the client needs Webhooks.
Decide what a useful enquiry contains
Agree which requests the team will follow up. Start with the service the customer needs and the details the client needs for the first reply. A trades business might need the postcode and project type. A venue might need the date and guest count.
Choose when the agent should offer to collect a request. A visitor asking for opening hours can receive the answer. A visitor asking for a quote or a callback can leave an enquiry.
Configure conversational requests
In KugaClient workspace › Actions › Collect enquiries
Open Actions, choose Collect enquiries and define the trigger, the context to ask for and the confirmation wording. The saved fields are Name, Contact method and Request summary. Extra context collected in the conversation belongs in the summary.
Avoid collecting a request at the end of every answer. Tell the agent when the visitor has shown an intention to contact the business, request a quote or ask for a callback.
Example for a home improvement business
Collect a request when the visitor asks for a quote or wants the team to contact them. Ask what work they need, their postcode and the approximate timescale if known. Collect their name and preferred contact method. Include the project, location and timescale in the request summary. Do not promise a price or a confirmed visit.
Name, Contact method and Request summary are the shared request fields. The workflow controls when and what to collect.
Test the enquiry in the customer’s channel
In KugaClient workspace › Deployments
Test an enquiry in each deployment the client will use. Ask for a quote or callback, give sample context and confirm that the agent asks for a name and a contact method.
Try a routine question too. Check that the agent answers it and only offers follow-up when appropriate.
Check the saved Contact Request
In KugaClient workspace › Contact Requests
Open the saved request and compare it with the conversation. Confirm the name and contact method, then read the summary as someone who has not seen the conversation.
Ask the client’s follow-up owner whether they can respond using that information. Adjust the collection instructions and repeat the test if they need additional context.
- The request appears in the correct workspace.
- The contact method is usable.
- The summary explains what the visitor needs.
- The visitor heard an accurate next step.
Connect onward delivery deliberately
In KugaClient workspace › Webhooks
If the client needs an enquiry sent to another tool, add the authorised HTTPS destination and select the relevant supported event. Protect the signing secret and configure verification at the receiver. Use Send test before relying on the production workflow.
Notification email is configured separately under Notifications. Check the recipients and test their delivery. Define who will monitor the inbox or receiving workflow when it fails.
- The destination belongs to the correct client.
- Only the required events are selected.
- A test reaches the receiving workflow.
- Notification recipients are current.
- There is a named follow-up owner.
Review enquiry quality after launch
Read the first enquiries with the client. Find missing context, unnecessary questions and requests outside the intended service. Update the collection instructions and repeat the affected test.
Track whether the team could follow up and what changed as a result. Add a question only when its answer helps the client respond.