Overview
Almost every widget problem falls into one of three buckets: the launcher does not appear, it appears but looks wrong, or conversations fail to start.The Launcher Does Not Appear
The snippet is not actually on the page
The snippet is not actually on the page
View your page source and search for
w.js. If it is missing, the snippet
was added to a template that this page does not use, or a caching layer is
still serving the old HTML.Fix: clear your site and CDN cache, then reload with a hard refresh.The widget is paused or deleted
The widget is paused or deleted
A paused widget deliberately renders nothing, and a deleted widget id no
longer resolves.Fix: open Embed Widgets in the dashboard and confirm the widget is
Active and that the id in your snippet matches.
A Content Security Policy is blocking it
A Content Security Policy is blocking it
The console will show a CSP violation naming
widget.callkaro.ai.Fix: allow the widget’s origins:React strips the script tag
React strips the script tag
A plain
<script src> written inside JSX is removed by React and never
executes — a very common cause in React and Next.js sites.Fix: use next/script, or inject the tag in a useEffect. See
installation.An ad or tracker blocker is removing it
An ad or tracker blocker is removing it
Some aggressive blockers treat any third-party script as tracking.Fix: confirm by testing in a private window with extensions disabled.
This affects only that visitor, not your installation.
The Launcher Appears But Looks Wrong
Default icon and colours instead of my branding
Default icon and colours instead of my branding
The widget loads its appearance from our servers at page load. If that
request is blocked, it falls back to defaults — the widget still works, it
just is not branded.Common causes: a
connect-src CSP rule that omits
backend.callkaro.ai, or a network-level blocker.Fix: allow connect-src https://backend.callkaro.ai and check the
console for a blocked request.Recent dashboard changes have not shown up
Recent dashboard changes have not shown up
Configuration is cached briefly so the widget stays fast.Fix: wait about a minute and hard-refresh.
It overlaps another chat widget
It overlaps another chat widget
Two widgets are competing for the same corner.Fix: change the CallKaro widget’s Position to the opposite corner.
It sits behind something on my page
It sits behind something on my page
Rare, but possible if your site uses extremely high
z-index values on a
sticky header or overlay.Fix: lower the z-index on the element covering it, or contact support.Conversations Fail To Start
This is the “Could not connect” message inside the panel.Your site is not served over HTTPS
Your site is not served over HTTPS
Browsers only allow microphone access on secure origins. The launcher and
panel work on
http://, but starting a conversation always fails.Fix: serve your site over HTTPS. http://localhost is exempt, so local
development works without a certificate.Microphone permission was denied
Microphone permission was denied
If the visitor dismissed or blocked the browser prompt, no audio can be
captured. Browsers remember the choice, so it will not ask again.Fix: click the padlock in the address bar, reset the microphone
permission for the site, and reload.
A Permissions-Policy header blocks the microphone
A Permissions-Policy header blocks the microphone
The widget delegates microphone access to its iframe. A header such as
Permissions-Policy: microphone=() prevents that delegation, so the widget
loads perfectly and then fails the moment a visitor presses Talk.Fix: remove the restriction, or explicitly allow
microphone=(self "https://widget.callkaro.ai").A corporate network is blocking the connection
A corporate network is blocking the connection
Voice needs a real-time media connection. Some corporate firewalls and VPNs
block the required traffic.Fix: test on a different network — mobile data is a quick check. If it
works there, ask IT to permit real-time audio to
callkaro.ai.Audio Problems During A Conversation
Status shows Live but nobody can hear anything
Status shows Live but nobody can hear anything
The session connected but audio is not flowing — usually a restrictive
network blocking real-time media, or the wrong input device selected.Fix: try another network, and check the browser’s site settings for
which microphone is selected.
The visitor cannot hear the agent
The visitor cannot hear the agent
Browsers block audio playback until the visitor interacts with the page.
Pressing Talk normally satisfies that, but an aggressive autoplay policy
can still intervene.Fix: check the tab is not muted, then reload and press Talk again.
The agent keeps interrupting or mishears
The agent keeps interrupting or mishears
This is agent tuning rather than a widget problem — background noise and
interruption thresholds are configured on the agent.Fix: see
call initiation and termination
and transcriber settings.
The Transcript
Some speech is faded
Some speech is faded
Faded text is expected. It marks speech still being transcribed; it
solidifies once finalised.
Still Stuck?
When contacting support, include these — it usually turns a long back-and-forth into a single reply:- The widget id and the page URL where it is installed
- Your browser and version, and the operating system
- Any console errors, copied as text
- Whether it fails for everyone or just one person or network
Contact Support
Send us the details above and we will investigate
Installation guide
Re-check your setup against the reference snippets