Skip to main content
The Fluents.ai Widget lets you place an AI Agent directly on your website.
Visitors can chat with the agent and start a voice call from the browser, without dialing a phone number. This page explains, in non‑technical terms:
  • What the widget does
  • When to use it
  • Where to configure it in the Fluents.ai dashboard
  • What you or your web developer needs to do next

​
What the widget is

The widget is a small, floating assistant you add to your website. When a visitor opens your site, they can:
  • Open the widget
  • Type questions or requests
  • Click the phone icon to start a live voice conversation with your agent
Behind the scenes, the widget connects to one of your Fluents.ai agents.
Each agent can have its own widget configuration.

​
Typical use cases

Businesses use the widget to:
  • Answer common questions on a website, 24/7
    (for example, hours, pricing, location, basic support)
  • Capture and qualify new leads
    (for example, collect name and contact info, then send them to your CRM or team)
  • Offer instant “call with an agent” from a landing page
    (for example, for sales teams that want to speak with prospects as soon as someone shows interest)
  • Provide after‑hours coverage on key pages
    (for example, contact page, checkout, signup page)

​
Where to configure the widget

The widget is configured from within each agent. To find the settings:
  1. In the left sidebar, click Agents.
  2. Click the agent you want to use on your website.
  3. At the top of the agent page, click the Widget Integration tab.
Everything related to that agent’s website widget lives on this tab.

​
What you see on the Widget Integration tab

The tab is divided into two main sections:
  • Direct JWT Token
    A quick way to generate a token that lets a website use this agent’s widget.
    This is useful for testing or simple setups.
  • API Signing Key
    A more advanced option for developers.
    It lets your backend system create short‑lived tokens automatically for the widget.
    This is better for production websites and logged‑in users.
You do not need to understand all the technical details to use the widget.
In many cases, your web developer will take the information from this tab and add the widget to your website.

​
Direct JWT Token (simple option)

Use Direct JWT Token when you:
  • Want to try the widget quickly on a test site or landing page
  • Do not yet have a developer integration
  • Are comfortable copying and pasting a value into your website settings
On this tab you can:
  1. See which agent the widget will use.
    The widget is always tied to the current agent you are editing.
  2. Choose a Token Expiry (how long the widget token will stay valid).
    Examples: 30 minutes, 1 hour, 3 hours, 6 hours, or Never expire.
  3. Click Generate Widget Token to create a token.
  4. Copy the value shown under Your Widget Token.
    The page also explains that this value will be used with the website snippet.
What to do with it:
  • Give this token to your web developer and ask them to “use this as the widget token” for your site.
  • Or, if you manage the website yourself, follow the instructions next to the token in the UI (and the “Show equivalent code” option, if available).
Note
Tokens that “never expire” are convenient for tests, but less secure.
For important production websites, prefer shorter expiry times or the API Signing Key approach.

​
API Signing Key (advanced, for developers)

If you have a developer or an engineering team, they will likely prefer API Signing Keys. On the API Signing Key tab you can:
  1. Click Generate API Signing Key.
    Fluents.ai shows you a new key once.
  2. Copy this key and store it in a safe place (for example, a secrets manager).
    For security reasons, Fluents.ai cannot show the full key again later.
  3. See a table of your existing keys, with:
    • When each key was created
    • A Key ID
    • A Remove action to delete a key you no longer want to use
What your developer will do with it:
  • Use this key on your server, not in the browser.
  • Have your server create short‑lived access tokens for the widget whenever a user visits your site or logs in.
  • Pass those tokens to the website snippet that loads the widget.
You can simply tell your developer:
“Go to the agent’s Widget Integration tab, open API Signing Key, generate a key, and use it to create tokens for the Fluents widget on our website. You can click ‘Show equivalent code’ in the app for examples.”

​
What you or your developer does next

After you have either:
  • A Widget Token from the Direct JWT Token tab, or
  • An API Signing Key for your developer,
the remaining steps are:
  1. Copy the embed snippet
    On the Widget Integration tab, look for the embed or installation instructions
    (for example, under “Widget Installation” or “Show equivalent code”).
  2. Give it to your web developer
    Ask them to:
    • Add the snippet to the pages where you want the widget to appear.
    • Insert the widget token where the instructions indicate.
  3. Publish or deploy your website
    Once the changes are live, the widget should appear and connect to your Fluents agent.
If you manage your own website and are comfortable editing HTML or scripts, you can follow the exact instructions shown beside the snippet in the dashboard. Those instructions are always the most up‑to‑date.

​
Testing the widget from the dashboard

Before or after adding the widget to your website, you can test the agent itself from inside Fluents.ai:
  1. Go to Agents.
  2. Select your agent.
  3. In the right‑hand panel (or main area, depending on your layout), use Test Call Agent to start a test call.
  4. Confirm the agent behaves as you expect:
    • Answers with the right greeting
    • Understands the questions you care about
    • Follows your configured flows and post‑call actions
If the agent works correctly here but not on your website, the issue is usually with how the website snippet or token was added. In that case, ask your developer to double‑check the installation instructions in the Widget Integration tab.

​
Common questions

Does the widget require a phone number?
No. The widget connects directly to your agent over the web. The visitor can speak to the agent through their browser. Can each agent have its own widget?
Yes. The settings on the Widget Integration tab apply only to the agent you are editing. You can enable widgets on multiple agents if you want different experiences on different websites or pages. Who should use API Signing Keys?
Teams with developers who want more control and better security in production. The signing key allows your backend to create short‑lived tokens and to tie widget usage to logged‑in users or plans.

​
Where to go next