In this guide
What you’ll finish with
A recorded review of client access, data sources and onward delivery, with unresolved items assigned to an owner.
Before you begin
- Access to the client workspace and the relevant agency settings.
- The approved source list and launch brief.
- The client’s authorised recipients and integration owners.
Check the workspace and account access
In KugaAgency workspace › Clients
Confirm that the business has its own client workspace and that you are editing the right one. Opening a new channel for the same client should keep its shared information together. An unrelated business should have a separate client workspace.
Use Client Portal for invited client users rather than sharing the agency login. Review access whenever someone leaves the client’s team or changes responsibility.
- Each business has the intended workspace.
- The agency account is controlled by the agency.
- Client users access their own portal experience.
- People who no longer need access have been reviewed.
Review every knowledge source
In KugaClient workspace › Knowledge
Inspect connected websites, uploaded files and the instructions that use them. Confirm that private records or unrelated client material have not entered a public agent’s knowledge collection. Use clear source names so another operator can identify what an answer should rely on.
Test a question that asks for information outside the approved scope. The agent should follow the defined fallback and avoid exposing unrelated information. Treat the public conversation test as an essential part of the review.
- Sources belong to this client and this service.
- The client has approved their use.
- Old or conflicting files have been removed or excluded.
- Out-of-scope questions follow the approved response.
Check credentials and event destinations
In KugaClient workspace › Webhooks
Use the dedicated connection settings for store or booking credentials. Put behavioural instructions in workflows, not passwords or API keys. Keep access limited to the people who maintain the connected service.
For Webhooks, verify the HTTPS destination, the subscribed events and the receiving system’s signing-secret validation. Use Send test and confirm the result at the destination. A saved endpoint without a received test has not been verified end to end.
- Credentials belong to the client’s intended account.
- No secret has been pasted into an instruction example or public file.
- The webhook destination is the correct environment.
- The receiver validates the signing secret.
- A test is received and handled by the expected workflow.
Review portal invitations and notification recipients
In KugaClient workspace › Client Portal
Check the client’s portal address, users and access. Invite user generates a private setup link. Share it with the intended person and check the portal using the access they will actually receive.
Open Notifications and review agency and client recipients. Reporting email can contain enquiry details, so outdated recipient lists can send information to people who no longer need it. Use available test delivery with fictional sample data.
- Open the correct client’s portal settings.
- Review the users and their intended access.
- Check the notification recipients for that client.
- Send a sample test and inspect its contents and delivery.
- Portal login and setup links identify the correct client.
- The user’s permissions have been reviewed.
- Recipients are current and approved.
- A test email contains the intended branding and sample information.
Check the public deployment and handover
In KugaClient workspace › Agent › Configuration
Run a normal conversation, an unknown question and a request to contact the team. Check that the agent’s description of the next step matches the configured process. Repeat the relevant tests on the published website.
If Human Handover is included, check the assigned people and settings under Human Handover, then test the escalation. Record the fallback when a person is unavailable. The Advanced plan includes two handover seats.
- The widget is installed once on the intended website.
- The saved conversation and enquiry appear in this workspace.
- No unavailable action is promised.
- Human Handover works if offered.
- The launch record lists the reviewer, date and unresolved items.