Give support and sales their own voice agents.

What is separate, and what do the agents share?

Each agent has its own settings, and changing one never affects the other. The table shows what each one has.

Both share the workspace itself: its 50 free conversations, its workspace tokens, its limits of 3 calls at once and 12 new calls a minute, and the email notices sent to the owner.

When should you run both agents?

Run both when the questions differ by audience. A visitor on your pricing page asks which plan fits and what it costs; a customer in your app asks why an import failed. One agent covering both needs both kinds of knowledge and two sets of rules in one set of instructions, which makes its answers harder to check.

If your site has one kind of visitor, start with one agent and add the other later. Nothing about the first changes when you do.

1. Split the knowledge by audience.

Decide where each fact lives before you add anything.

• Sales notes: plans and prices exactly as your pricing page states them, what each plan includes, trials, published security answers, integrations and who the product suits.
• Support knowledge: setup steps, how features work, troubleshooting, account settings and billing how-tos, plus your GitHub docs.
• Facts both need, such as integrations or where data is stored, go into each agent as separate sources. Keep a list of them so you update both copies together.
• Website import is switched off, so paste pricing page text into a sales note, and replace the note after each pricing change.

2. Give each agent its own instructions and greeting.

Support instructions are about solving a problem one step at a time. Sales instructions are about understanding what the visitor wants, explaining fit and pointing to the next step, such as signing up or your contact form. Both agents are already told never to invent prices, discounts or capabilities.

Use a different agent name, greeting and button label for each, so visitors can tell which one they’re talking to. A different voice helps too.

3. Put each widget where its audience is.

Paste the sales script tag on your homepage, pricing and feature pages, and the support tag in your help centre, docs and signed-in app. Each agent’s allowed origins are a separate list: often your marketing domain for sales, and your app and docs domains for support.

Both widgets can share a page. Their buttons stack in the bottom-right corner, and a duplicate tag for the same agent is ignored.

<script
  src="https://app.kawlnow.com/widget.js"
  data-helpline="YOUR_WORKSPACE_ID"
  async>
</script>
<script
  src="https://app.kawlnow.com/widget.js"
  data-helpline="YOUR_WORKSPACE_ID"
  data-channel="sales"
  async
></script>

4. Test, launch and review each agent on its own.

Each agent has its own readiness. The dashboard won’t let you switch on Accept sales calls until the sales agent has approved sales knowledge, saved settings, an allowed origin and a completed test call. The Overview checklist follows the support agent only, so check the Sales agent tab yourself.

On Conversations, filter by Support calls or Sales calls to review each agent. A sales call that needed support knowledge can mean a customer found the wrong button, or that sales needs its own copy of a fact.

Both agents draw on the same 50 free conversations, so a busy pricing page leaves fewer for support. Paid calls aren’t available yet, so new calls stop once all 50 are used.

Common questions