In this guide
What you’ll finish with
A tested enquiry delivery path with a named owner and a clear boundary between the agent and external processing.
Before you begin
- An agreed customer task and request summary.
- An authorised receiving endpoint for external delivery.
- The required plan, receiver access and a follow-up owner.
Separate conversation behaviour from delivery
In KugaClient workspace › Knowledge
Use Knowledge for approved answers, Contact Requests for conversational capture and Scheduling for the booking process. These are the agent’s working instructions and supported capabilities.
An external automation has its own processing, credentials and failure handling. Do not assume that writing an instruction naming a CRM creates a connection to it. Define the supported event and the destination separately.
| Task | Configure |
|---|---|
| Answer from approved sources | Knowledge |
| Collect a conversational enquiry | Contact Requests |
| Offer an appointment | Scheduling |
| Deliver a supported event externally | Webhooks and the receiving process |
Make the request useful before sending it
In KugaClient workspace › Actions › Collect enquiries
Write the capture trigger and summary requirements. Complete a test conversation and inspect Name, Contact method and Request summary in the inbox. Fix missing context at this stage.
Ask the questions needed to qualify the enquiry, then save the answers in the request summary. Inspect the resulting Contact Request before adding onward delivery.
Example delivery specification
Trigger: a supported new contact request event. Useful context: service requested, relevant location and the visitor’s question. Receiving process: [authorised destination]. Owner: [client team or agency role]. Success check: the test event reaches the receiver and produces the intended follow-up record. Failure process: [where issues are reviewed and who acts].
Configure the authorised destination
In KugaClient workspace › Webhooks
Choose Add webhook, enter the authorised HTTPS destination and select only the supported events required for the process. Configure verification of the signing secret at the receiver and keep that secret private.
Save the configuration. Use the client’s intended destination and credentials, keeping them separate from other clients. Confirm that the receiver handles the selected event before relying on it for live requests.
- Confirm the endpoint owner and receiving behaviour.
- Add the HTTPS destination in Webhooks.
- Select the required supported event.
- Configure signing verification at the receiver.
- Save the webhook.
Test the complete receiving process
In KugaClient workspace › Webhooks
Use Send test and inspect the receiving system. Confirm that the event arrives, passes verification and produces the expected result. A saved webhook address alone does not establish that the downstream workflow works.
Then run the relevant end-to-end client journey with fictional details. Check the saved request in Kuga and the resulting record at the destination. Follow the receiver’s documented handling for retries and duplicate events.
- The selected event reaches the receiver.
- Signature verification works.
- The fields map to the intended record.
- A complete test request is handled.
- An owner can identify and resolve delivery issues.
Document what each system owns
Record whether Kuga, the receiver or the client’s team owns each step. Notifications, portal access and a CRM record may serve different purposes, so avoid creating redundant alerts without an owner.
Review the delivery path after changes to the source workflow, event selection or receiving tool. Keep the documentation close to the client’s operating record.