Sales and support chat on a marketing website

This chapter describes how a product website can answer routine questions with Knowledge-grounded AI and hand purchase decisions to people, using one hosted KasaDESK chat. It uses the KasaDESK website as the worked example. You can apply the same pattern to your own marketing site.

Status. This is the planned configuration for the KasaDESK website. The example origins and workspace below are placeholders for that plan and have not been verified as live infrastructure. The individual product behaviors referenced here are covered in the linked chapters.

How the chat reaches visitorsLink to this section

Piece Example value Notes
Website origin https://kasadesk.com Serves the landing page at / and documentation at /documentation from local content.
KasaDESK installation https://support.mimdigital.net A separate, self-hosted KasaDESK server. It hosts the widget loader, the chat frame and the chat API.
Workspace KasaDESK Landing Page App A dedicated brand, so its Knowledge, AI settings and chat theme stay separate from any other support work.
Workgroup Sales The Web Chat channel’s default workgroup. Every conversation from the site starts here.
Channel One Web Chat channel Allowed origin https://kasadesk.com. Add any other exact origin, such as a www host, only if the site is served there.

The website itself contains only the publishable site key and a script tag. The chat runs in an isolated iframe served by the KasaDESK installation. Messages travel between the visitor’s browser and the installation directly. The website build never contacts the KasaDESK server and holds no KasaDESK credentials.

Public values and private valuesLink to this section

Value Where it lives
Site key (pk_…) Public. In the website’s HTML. It identifies the chat channel, not a person.
Web Chat identity secret Private. Only needed if the site signs in visitors. A marketing site normally does not, so leave it unused.
AI provider keys, messaging provider tokens, ENCRYPTION_KEY Private. Only on the KasaDESK server. Never in the website repository.

Set up the routingLink to this section

  1. Follow Install KasaDESK and complete the first run. For this planned example, use https://support.mimdigital.net as the installation’s public and staff console origin after DNS and HTTPS have been configured and verified by the operator.
  2. In Admin → Settings → Workspaces & Teams, create the KasaDESK Landing Page App workspace and a Sales workgroup. Invite staff and give the sales agents access to that workgroup under Agents & Roles. Set support hours and decide whether to enable Allow callback requests in web chat on the workspace.
  3. In Channels & Integrations, create a Web Chat channel with that workspace and Sales as its default workgroup. Add exactly https://kasadesk.com as the planned allowed website origin. Allowlist an additional origin only for an approved deployment or staging site. Copy the publishable Web Chat site key.
  4. Publish the brand palette as described below. Supply the actual HTTPS support origin and public site key as the separate website’s widget configuration after the operator verifies them.

One chat for two entry pointsLink to this section

The website’s primary Chat with us buttons and the standard floating launcher open one hosted widget. Mount the standard loader once in the shared application shell so navigation between the landing page and documentation retains the conversation on the same browser. In the sample, substitute the configured server and publishable key:

<script async src="https://support.example.com/widget/loader.js"
        data-site-key="PUBLIC_KASADESK_SITE_KEY"></script>

Use the standard loader with its floating launcher. Keep a shared loading state until the loader’s window.KasaDesk.on('ready', handler) event has fired. Each real Chat with us button calls window.KasaDesk.open(). Use the supported close event to return focus to the page button that opened the widget and retain the loader’s normal focus behavior for the floating launcher. During loading or when disabled, unconfigured, or unavailable, leave the page buttons disabled with an accessible status. Use the same widget for all buyer chat.

Pages must work without the chatLink to this section

Treat the chat as an enhancement. Landing-page content and every /documentation page must render and navigate normally when the KasaDESK server is unreachable, the channel is disabled, or a visitor blocks third-party scripts. Do not gate navigation, documentation search or page content on the widget. Load the loader with async and never wait for it.

Brand coloursLink to this section

Publish the chat colours once for the KasaDESK Landing Page App workspace in Admin → Settings → Workspaces & Teams → Widget appearance. New page loads pick up the published palette. The loader’s ready event reports the published primary colours if the in-page button should match. See Per-brand widget appearance.

Routine questions answered from KnowledgeLink to this section

  1. Under Admin → Settings → Knowledge, publish articles in the KasaDESK Landing Page App workspace that answer common, factual questions: what the product is, self-hosting requirements, supported channels and integrations. The public FAQ is a good source.
  2. Under AI & Models, test a provider connection and save the Autopilot chain. Set the workspace’s AI mode to Autopilot. Autopilot can be enabled only after at least one article is published in that workspace.
  3. Set AI coverage in Support Hours & SLA for the hours AI may answer.

Autopilot replies only when a published article in this workspace matches the visitor’s latest message. When nothing matches, or the provider fails or declines, the conversation goes to the Sales queue without an AI reply. See Knowledge and AI.

Do not publish pricing, discount, licence-negotiation or contract guidance as Knowledge articles. Those answers belong to people.

Purchase decisions go to peopleLink to this section

All conversations from this channel already sit in the Sales workgroup, so sales staff see every conversation, including those the AI answered.

  • When AI coverage is active and Autopilot can answer, the chat shows Talk to support. Choosing it marks the conversation as a human request, pauses AI replies and leaves it queued for Sales.
  • When Autopilot is not active, there is no AI step. Every message waits for a person in Sales.
  • Staff who take over a conversation pause AI replies for it.
  • Request a callback, if enabled, records the number on the active ticket for staff follow-up. It does not start a call or reassign the ticket. See Callback requests.

Verify automatic purchase-intent handoff with the actual configuration before describing it as available. Rely on the Talk to support control, unmatched questions escalating to people, and Sales staff watching the queue. Sales staff make every pricing and licensing decision.

Enable Inbox alerts for Sales staff so new messages are noticed. See Staff inbox and notifications.

Synthetic checks before launchLink to this section

Use a staging copy of the page on an allowlisted origin, synthetic visitor names and no real customer data.

Check Expected result
Open the page with the KasaDESK server stopped Landing page and documentation work normally. The Chat with us control is disabled and the page explains that chat is unavailable.
Open the page normally The floating Chat with us launcher appears in the published colours.
Click the in-page button, then the floating launcher Both open the same chat and the same message history.
Ask a question covered by a published article An AI reply arrives in the chat. The conversation appears in Sales with the AI reply.
Ask a question with no matching article No AI reply. The conversation waits in Sales.
Ask about a discount or a licence for a specific deal No pricing commitment from AI. A Sales staff member replies.
Choose Talk to support AI replies pause. The conversation shows the human request in Sales.
Use Request a callback on an open test ticket Authorized Sales staff see the request on the ticket and can follow up.
Staff add an internal note and a reply The visitor sees only the reply.
Load the page from a non-allowlisted origin The chat frame refuses to load.

Record results in your release checklist. Repeat after each change to Knowledge, AI routing or the website template.