In this guide
What you’ll finish with
A scoped website addition with a tested customer journey and clear maintenance responsibilities.
Before you begin
- The client’s current website and common customer questions.
- Approved sources for a demonstration.
- An agreed website change and review process.
Review the customer journey with the client
Ask what visitors struggle to find and what enquiries the team receives repeatedly. Check the existing site navigation, service pages, booking links and forms before deciding that chat is the right addition.
Choose a focused task where the client has reliable information and a useful next step. Record how the website and the client’s team handle that task today.
- The customer task is specific.
- The necessary information exists or has an owner.
- The business can act on the resulting enquiry.
- The agent’s role complements the existing site.
Build a focused Preview example
In KugaAgency workspace › Clients
Create the client workspace and review Business details. Connect the approved website scope under Knowledge. Configure the enquiry or booking route that matches the task.
Set the response instructions in Agent Configuration and use Customise in Website Chat to prepare the widget and opening message. Use Test agent to check the agreed example questions before showing it to the client.
- Create and review the client workspace.
- Prepare the approved knowledge sources.
- Configure Contact Requests or Scheduling.
- Match the messenger to the client’s website.
- Run and record the example tests.
Appearance belongs to the client’s messenger. Review its placement alongside the site’s existing controls.
Show the full path to the team
Demonstrate a routine answer and a relevant request or booking. Open the saved record so the client can assess what their team receives. Explain where live connections or approvals are still required.
Ask whether the summary is useful and who will respond. Use the answers to refine the scope instead of relying on an attractive chat demonstration alone.
Write the addition into the service scope
Specify the client plan, launch channel, sources, workflows, installation and acceptance checks. Define the ongoing review work and how it relates to your existing website maintenance agreement.
Clarify who updates the agent when website content, prices or services change. A website edit may require a knowledge refresh and a repeated answer test, even when the messenger code stays the same.
Install and check the live website
In KugaClient workspace › Website Chat › Deploy
Use the generated Widget code and the site’s approved code insertion method. Install it once. Check the live site on desktop and mobile, including consent controls, sticky buttons and any existing chat widget.
Submit a complete test enquiry and confirm its saved record and delivery. If attribution is required, configure Capture UTM fields and test the actual landing journey.
- The widget appears once on intended pages.
- Placement works with existing mobile controls.
- The approved knowledge answers remain accurate.
- A test enquiry reaches the correct destination.
- Attribution is checked where configured.
Review the addition as a service
Use the first live conversations to find missing information and improve the workflow. Report the changes and the client’s confirmed outcomes separately from basic activity.
When the website is redesigned or the client adds services, review the agent’s appearance, sources and customer journeys as part of that change.