In this guide
What you’ll finish with
A documented purpose, approved visitor wording and a checked process for personal information collected through the agent.
Before you begin
- The client’s decision-maker for privacy and customer data.
- The current Kuga DPA and Privacy Policy.
- The client’s privacy notice and proposed follow-up process.
Record the responsibilities and purpose
Write down the purpose of the deployment, such as answering service questions and arranging a callback. The organisation deciding why and how visitor information is processed needs to identify its legal basis and responsibilities. These decisions should be made before a live agent starts collecting information.
Kuga’s DPA distinguishes the customer acting as a controller from an agency acting as a processor for its client. Kuga may process service content as a processor or sub-processor and acts independently for purposes described in its Privacy Policy. Read the current documents for the arrangement that applies to your service.
Deployment privacy record
Purpose: [customer task] Client/controller: [organisation] Agency role: [agreed role] Legal basis and rationale: [client decision] Information collected: [fields and conversation context] Recipients and access: [people and systems] Retention and request process: [agreed policy]
Approve what the visitor is told
In KugaClient workspace › Deployments › Website Chat › Customise › Messages
The ICO’s AI transparency guidance requires people to receive meaningful information about the use of their personal data. The client’s notice should explain the deployment in a way visitors can understand, including the relevant use, review and sharing of conversation information.
Check the opening message and the surrounding website notice together. Make the client’s privacy information accessible in the journey. A friendly greeting is useful product copy, but it does not replace the privacy information the client needs to provide.
- Ask the client to approve the visitor notice.
- Review the messenger identity and opening message.
- Confirm that the relevant privacy notice is accessible on the public website.
- Test the conversation that leads to an enquiry request.
Keep knowledge and requests focused
In KugaClient workspace › Knowledge
Connect the sources needed to answer the approved questions. Review files before upload and exclude material that contains unrelated customer records or private information the agent does not need. A business policy file and a customer case file serve different purposes.
Under Actions > Collect enquiries, define when a request should be collected and what context belongs in the summary. Kuga saves Name, Contact method and Request summary. Keep the summary relevant to the follow-up and use the client’s approved process for sensitive matters.
- Knowledge sources have been reviewed and approved.
- The request asks for the information needed for the agreed follow-up.
- The agent avoids soliciting unrelated sensitive detail.
- Examples use fictional data during preparation.
Check access and onward delivery
In KugaClient workspace › Client Portal
Review who can sign in to the client portal and who receives notification emails. Check the client’s user permissions and the experience of an invited user. Share private setup links only through the agreed channel.
If Webhooks sends information to another system, record the destination and selected events. Confirm that the receiving system and its users are authorised for that client’s data. Use a test payload before enabling the intended production process.
- Portal users are named and appropriate for the client.
- Notification recipients are current.
- A webhook destination is documented and tested if used.
- Copies of enquiries are covered by the client’s handling process.
Agree retention and request handling
Document the retention and access-request process using the current agreement and policies. Include copies held in email or downstream systems as well as records in Kuga. Make sure the client knows who to contact when a visitor asks about their information.
Keep the deployment brief, configuration checks and source approvals with the delivery record. If the service changes purpose or begins collecting different information, revisit these decisions before changing the agent. This guide covers practical setup; it cannot decide the client’s legal basis or confirm legal compliance for them.
- Retention is recorded for each relevant system.
- Access and deletion requests have an owner.
- The client knows the escalation contact.
- Changes to purpose or data collection trigger a new review.