Where do you choose the channel?

The same choice appears everywhere you work with an agent:

Choosing the support or sales agent
WhereSupportSales
Widget embedNo data-channel, or data-channel="support"data-channel="sales"
Settings over RESTPATCH /api/manage/settingsPATCH /api/manage/sales-settings
Workspace responsesettingssalesSettings
New source over REST"channel": "support", or leave it out"channel": "sales"
GitHub importYes, over REST and MCPNot available
Insights over RESTGET /api/manage/insightsGET /api/manage/insights?channel=sales
MCP toolsLeave channel out, or send "support"channel: "sales" on update_agent, add_knowledge, get_installation and conversation_insights
Sources and conversationsMarked "channel": "support"Marked "channel": "sales"
DashboardVoice agent tabSales agent tab

What does each agent keep to itself?

The agents are configured separately, and changing one never changes the other.

  • Product name, agent name, greeting, instructions, voice, button label and colour. A new sales agent starts with the support agent’s product name until you change it.
  • Knowledge. Every source belongs to one channel, and a call searches only the approved sources of the agent it started with, so the sales agent never sees support or GitHub sources.
  • Allowed origins, up to 10 each.
  • The customer-calls switch. Switching sales on leaves support as it was.
  • Dashboard test calls, which you run for each agent separately.
  • Automatic insights, which each agent gets from its own customer calls.

What do the two channels share?

These belong to the workspace, so both agents draw on them:

  • One workspace ID, so both embeds carry the same data-helpline value.
  • Tokens. One workspace token manages both agents, and there are no tokens limited to one channel.
  • The free allowance: the workspace’s first 50 conversations, one time only, shared by support calls, sales calls and dashboard tests.
  • The call limits: 3 calls starting or in progress at once, and 12 new calls a minute, counted across both agents.
  • Notification emails, which go to the workspace owner’s sign-in address.

How do you give the sales agent its knowledge?

Add sales notes as documents: POST /api/manage/sources with "channel": "sales", or add_knowledge with channel: "sales". Approve each one after review, as you would for support.

GitHub import feeds only the support agent, and a sales source can’t carry a repository or path. Website import is switched off, so paste the text of your pricing and product pages into sales notes instead. A channel other than support or sales returns 400 with “Choose the support or sales channel.”

Add a sales note for review
curl -X POST 'https://app.kawlnow.com/api/manage/sources' \
  -H 'Authorization: Bearer YOUR_WORKSPACE_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"channel": "sales", "title": "Plans and pricing", "content": "Your checked pricing page copy goes here."}'

# Response 201: {"id": "SOURCE_ID"}, saved unapproved