ChecklistGetting started

Prepare a client agent for launch

Work through the business details, knowledge, workflows and live website before launching. Record the expected answers and saved outcomes so the client can approve a tested service.

In this guide

What you’ll finish with

A tested client deployment with approved answers, working follow-up and a clear owner for the first live review.

Before you begin

  • A completed client workspace.
  • Approved website pages or files.
  • Access to install the widget on the client’s website.
  • A live plan for public deployment.

Check the business and the selected plan

In KugaClient workspace › Business

Confirm the business name, services, location and contact details. These shared details are used by the client’s agents, so an incorrect address or outdated service description can affect more than one channel.

Open Subscription & Usage and confirm that the plan covers the launch. Preview provides 50 lifetime AI replies for building and testing. Choose a paid plan before treating the agent as a public service.

  • The correct client workspace is open.
  • Shared business details have been approved.
  • The chosen plan includes the required channels and tools.
  • The person responsible for billing understands the selected subscription.

Confirm that knowledge is ready

In KugaClient workspace › Knowledge

Check the website connection and uploaded files. For a website scan, review its progress and final report before relying on the pages. Use Pages to check the material available to the agent.

Read the Knowledge workflow instructions as well as the sources. They should explain how to use the approved information and what to do when the answer is missing. A successful upload alone does not prove a correct customer answer.

Review the knowledge instructions, connected website and uploaded files before testing the answers.

  • The required website pages are available.
  • Files contain readable text and current information.
  • Outdated or conflicting material has been removed or excluded.
  • The agent has been tested against facts from the important sources.

Test each next step

In KugaClient workspace › Actions

Review Collect enquiries and Book appointments. A booking link sends the visitor to a booking page; a supported calendar can open inside the website widget. Test the method you have actually configured.

If the launch includes Human Handover, check the Advanced plan, settings and assigned people. Then run a test that reaches the handover process. A written escalation instruction is not enough if no one is configured to take over.

  • An enquiry creates a request with a usable name, contact method and summary.
  • The agreed notification recipient receives a test.
  • The booking route works with the configured provider.
  • Human Handover is tested if it is part of the service.
  • The fallback response is appropriate when a person is unavailable.

Review the messenger and the answers

In KugaClient workspace › Deployments › Website Chat › Customise

Check the opening message, placement and footer in Customise. Select Test agent and ask the questions agreed with the client. Use a fresh conversation for separate scenarios so an earlier answer does not make the next test easier.

Include a question the knowledge cannot answer. Confirm that the agent acknowledges the gap and follows the approved next step rather than inventing a price, policy or booking.

  • The name and opening message match the client.
  • Desktop and mobile placement leave important website controls usable.
  • The agency footer is legible.
  • The test set includes routine questions, uncertain answers and follow-up.

Install and test the public website

In KugaClient workspace › Website Chat › Deploy

Use the widget installation supplied by Deploy. Install it once on the intended website and publish the website changes. Open the public page in a fresh browser session and repeat a complete conversation.

Check the public deployment on a phone as well as a desktop. Confirm that the conversation appears in Kuga and that any resulting request reaches the right client inbox.

  1. Install the generated widget code using the website’s supported custom-code area.
  2. Publish the client website.
  3. Open the public URL and test the messenger.
  4. Check the saved conversation and request in the same client workspace.

Assign the first live review

Agree who will check the first conversations and when the client will receive the first update. Use the initial review to find missing information and unclear instructions, then retest the scenarios affected by any change.

Record launch approval, the installation location and the follow-up owner. This makes subsequent changes easier to check and gives another team member enough context to maintain the client.

  • Client approval is recorded.
  • The installation location is documented.
  • The inbox and conversation review have named owners.
  • A first review date is agreed.

Pick a client you know.

Show them their AI.

Use their website to build a demo. Put your name on it and let them try it.