Skip to main content
After creating and configuring your agent, you are ready to put it in front of your users. Beenos Solutions offers three deployment methods so you can meet your audience wherever they are — embedded directly in your product, shared as a standalone link, or integrated into any application through the REST API. Open the Deploy tab on your agent’s detail page to access all options.
The chat widget embeds a floating chat button on any webpage. When a visitor clicks it, a conversation panel opens and they can start asking questions immediately — without leaving your site.

Get your Agent ID

1

Open the Deploy tab

Navigate to your agent’s detail page in the Beenos Solutions dashboard and click the Deploy tab.
2

Copy your Agent ID

Under the Chat Widget section, locate your Agent ID. It is a short alphanumeric string that uniquely identifies your agent (for example, agt_k8x2p1mq). Copy this value.
3

Add the script to your site

Paste the snippet below into the <body> of any HTML page, replacing YOUR_AGENT_ID with the value you copied. The widget loads asynchronously and will not affect your page’s load performance.
You can customize the widget’s accent color by changing the data-primary-color attribute to any valid hex value. Additional widget options — including position, button label, and initial open state — are available in the dashboard under Widget Appearance.
The widget script is versioned automatically. You never need to update the snippet to receive bug fixes or performance improvements.

Managing deployed agents

You can adjust your agent’s deployment state at any time from the Deploy tab without affecting its configuration or knowledge base connections.
  • Enable / Disable — Toggle the agent on or off for each deployment method independently. Disabling a widget or shareable link takes effect within seconds.
  • Regenerate embed code — If you need to rotate your agent ID (for example, after a security incident), click Regenerate to issue a new ID. Update the snippet or API calls in your codebase with the new value. The old ID stops working immediately.
  • Usage metrics — The Deploy tab shows basic usage statistics for each deployment method, including total conversations, average turns per session, and fallback trigger rate.
Consider deploying separate agents for different audiences or product areas — for example, one agent for your developer documentation and another for your end-user help center. Each can connect to its own knowledge base and carry its own persona, so users always get responses tailored to their context.