​ To learn more, see the sources I considered: [[1] Disconnections in Call](https://discord.com/channels/1186424376300679209/1364985947254685796) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

in what format Retell STT accepts, Retell’s realtime STT expects JSON frames ???

@AI Evy in what format Retell STT accepts, Retell’s realtime STT expects JSON frames ??? https://cdn.discordapp.com/attachments/1458452259615674389/1458463935144525834/image.png?ex=695fbbe3&is=695e6a63&hm=c4044dab61b3340a88fcd69480910fe5e286e12dd26c912a9b0bf92f1b1d8f4b& https://cdn.discordapp.com/attachments/1458452259615674389/1458463935635263651/image.png?ex=695fbbe3&is=695e6a63&hm=d1a904e250d28fe8569cd0f8e3a0ae6b9d88ed5694b2cd8ab5a1152d9ebc964a&

### Answer I don't have specific documentation in the available sources about the exact format Retell's realtime STT expects for incoming frames (whether JSON or raw audio) . The sources I have access to cover custom functions, agent creation, and LLM configuration, but don't detail the WebSocket message format for the STT/custom LLM interface. For the custom LLM WebSocket protocol and message formats, I'd recommend checking: - [Custom LLM WebSocket documentation]() (search for "custom LLM" or "WebSocket") - [Contact Sales]() for direct support - [Retell AI GitHub]() for SDK examples Would you like me to try providing a general answer based on common WebSocket patterns, or do you have any error messages/logs that might help narrow down the issue?

message has been deleted

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer ### Answer Actually, I do have documentation on the LLM WebSocket protocol. Here's what Retell expects: Message Format All WebSocket messages are text events where the

data

attribute is a JSON object stringified. [(1) ]() Your Server → Retell Events: When responding to Retell, you send JSON with a

response_type

field. For responses, use:

json
{
  "response_id": 0,
  "content": "How may I help you?",
  "content_complete": true,
  "end_call": false
}

[(2) ]() Retell → Your Server Events: Retell sends JSON with an

interaction_type

field (

update_only

,

response_required

,

reminder_required

,

ping_pong

) . [(1) ]() Key Protocol Points: - Your server must send the first message upon WebSocket connection (set content to empty string if you want the user to speak first) [(3) ]() - When

interaction_type

is

response_required

, you must send a response back - You can stream responses or send them in one go (streaming recommended for lower latency) [(1) ]() Example Response Handler:

javascript
const res: RetellResponse = {
  response_id: request.response_id,
  content: "I am sorry, can you say that again?",
  content_complete: true,
  end_call: false,
};
ws.send(JSON.stringify(res) ) ;

[(2) ]() Check out the [Node Demo Repository]() or [Python Demo Repository]() for complete examples. [(3) ]()

​ To learn more, see the sources I considered: [[1] LLM WebSocket](https://docs.retellai.com/api-references/llm-websocket) [[2] Setup WebSocket Server](https://docs.retellai.com/integrate-llm/setup-websocket-server) [[3] Custom LLM Overview](https://docs.retellai.com/integrate-llm/overview) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer --- I don't have specific documentation in my current sources about the exact format that Retell's STT (speech-to-text) expects for incoming audio data. The sources I have access to cover agent configuration (like

stt_mode

which can be set to

"fast"

or

"accurate"

) [(1) ]() , custom functions, and LLM response formats—but they don't detail the raw audio input format for the STT pipeline itself. For the custom LLM WebSocket integration, **Retell handles the STT internally**—your custom LLM server receives already-transcribed text from Retell (as JSON with the transcript in the payload) , and you send back text responses. You don't send audio directly to Retell's STT in that flow. If you're asking about sending raw audio to Retell, I'd recommend checking: - [LLM WebSocket documentation]() - [Contact Sales]() - [Retell AI GitHub]() Could you clarify your use case? Are you trying to: 1. Send audio directly to Retell's STT? 2. Receive transcriptions in your custom LLM server? 3. Something else? This will help me point you to the right resources.

​ To learn more, see the sources I considered: [[1] Update Voice Agent](https://docs.retellai.com/api-references/update-agent) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer I don't have specific documentation in my current sources about sending raw audio directly to Retell's STT service and what format it expects. Based on the available documentation, for web calls using the Retell Web SDK, if you're working with custom audio handling, the SDK mentions PCM audio format. The documentation references conversion functions

convertUnsigned8ToFloat32

and

convertFloat32ToUnsigned8

for PCM audio representation. [(1) ]() However, the typical Retell architecture handles STT internally—you connect via: - Phone calls (SIP/PSTN) : Retell handles the audio and STT - **Web calls**: The Web SDK handles audio capture and STT - **Custom LLM**: You receive already-transcribed text from Retell If you're trying to stream raw audio to Retell's STT outside of these standard flows, that's not a documented use case in my available sources. Could you clarify your setup? 1. Are you using the Web SDK and trying to send custom audio? 2. Are you trying to bypass Retell's phone/web infrastructure entirely? 3. What's the source of your "live call audio"? For direct support on custom audio streaming to STT: - Visit [Contact Sales]() - Visit [) Would you like a general answer about common audio streaming formats for STT systems?

​ To learn more, see the sources I considered: [[1] Connect to web call](https://docs.retellai.com/deploy/web-call) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer I don't have specific documentation about the

RetellWebChat

widget configuration in my available sources. The sources I have cover the Retell Web SDK for voice calls (using

retell-client-js-sdk

) , not the chat widget you're referencing. For web voice calls, the documented approach uses:

javascript
import { RetellWebClient } from "retell-client-js-sdk";
const retellWebClient = new RetellWebClient() ;

[(1) ]() A few things to check with your chat widget code: 1. Replace the placeholder — You have

agentId: "YOUR_RETELL_AGENT_ID"

which needs to be replaced with your actual agent ID 2. Agent configuration — Ensure your agent is configured for chat mode (not just voice calls) 3. Console errors — Check your browser's developer console for any JavaScript errors when the page loads For the chat widget specifically, I'd recommend: - Check out these potentially useful sources: [Connect to web call]() , [Create Web Call]() - Visit [Contact Sales]() - Visit [) Would you like me to try providing a general answer about debugging embedded widget scripts, or can you share any error messages from your browser console?

​ To learn more, see the sources I considered: [[1] Connect to web call](https://docs.retellai.com/deploy/web-call) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

@AI Evy provide me right chat widget code: is this link correct https://cdn.retellai.com/webchat.js https://cdn.discordapp.com/attachments/1458452259615674389/1462114711020507331/image.png?ex=696d03ef&is=696bb26f&hm=93fadf03e6ac92a2825f55f9a14912e95a75897e0abfba52112b8e357896991b&

### Answer The URL ` is not correct. The correct script source for the Retell Chat Widget is:

<https://dashboard.retellai.com/retell-widget.js>

[(1) ]() Here's the correct chat widget code to embed in your HTML

<head>

tag:

html
<script
  id="retell-widget"
  src="<https://dashboard.retellai.com/retell-widget.js%22>
  type="module"
  data-public-key="YOUR_RETELL_PUBLIC_KEY"
  data-agent-id="YOUR_CHAT_AGENT_ID"
  data-agent-version="YOUR_AGENT_VERSION"
  data-title="YOUR_CUSTOM_TITLE"
  data-logo-url="YOUR_LOGO_URL"
  data-color="YOUR_CUSTOM_COLOR"
  data-bot-name="YOUR_BOT_NAME"
  data-popup-message="YOUR_POPUP_MESSAGE"
  data-show-ai-popup="true"
  data-show-ai-popup-time="5"
  data-auto-open="false"
></script>

Required attributes: -

data-public-key

- Your Retell public key (get it from Dashboard → Keys → Public Keys) , [(2) ]() -

data-agent-id

- Your chat agent ID [(1) ]() Optional attributes: -

data-agent-version

- Agent version (defaults to latest if unset) -

data-title

- Custom chat window title -

data-logo-url

- URL of your logo image -

data-color

- Hex color code for widget theme (e.g., "#FFA07A") -

data-bot-name

- Bot name for popup messages -

data-popup-message

- Popup message before users open chat -

data-show-ai-popup

- Set to "true" to enable popup messages -

data-auto-open

- Set to "true" to auto-open chat widget on page load Important: You need a Retell Public Key (not an API key) for the chat widget. Create one in Dashboard → Keys → + Add Key → Public Key, and specify your website domain. [(2) ]()

​ To learn more, see the sources I considered: [[1] Retell Website Widget](https://docs.retellai.com/deploy/chat-widget) [[2] Chat Widget, Custom Function Enhancement and more!](https://www.retellai.com/changelog/chat-widget-custom-function-enhancement-and-more) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer If your chat widget is loading but not getting AI responses, here are the key things to verify: *1. Ensure you're using a Chat Agent (not a Voice Agent) * The chat widget requires a chat agent ID, not a voice agent ID. [(1) ]() 2. Verify your agent version If you haven't published any new versions, make sure

data-agent-version

is set to

"0"

. [(2) ]() 3. Check your Public Key configuration Make sure your public key is configured with the correct domain where the widget is embedded. [(1) ]() 4. Correct widget setup Confirm your script looks like this in the

<head>

tag:

html
<script
  id="retell-widget"
  src="<https://dashboard.retellai.com/retell-widget.js%22>
  type="module"
  data-public-key="YOUR_RETELL_PUBLIC_KEY"
  data-agent-id="YOUR_CHAT_AGENT_ID"
  data-agent-version="0"
  data-title="YOUR_CUSTOM_TITLE"
></script>

, [(3) ]() 5. Test your agent in the dashboard first Use Manual Chat or AI Simulated Chat in the agent builder to confirm your agent responds correctly before embedding. Troubleshooting steps: - Check your browser's developer console for any JavaScript errors - Verify the agent ID and public key are correct (no typos) - Ensure the domain in your public key settings matches where you're testing If the agent works in the dashboard but not in the widget, the issue is likely with the public key domain configuration or the agent ID. Would you like help verifying any of these specific items?

​ To learn more, see the sources I considered: [[1] Retell Website Widget](https://docs.retellai.com/deploy/chat-widget) [[2] Introducing Retell Chat - Web chat widget]() [[3] Retell AI Chat Agent – Real-Time Web Chat Automation Widget | Retell AI](https://www.retellai.com/blog/meet-retell-chat-agents-build-smarter-web-chats) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

​ To learn more, see the sources I considered: [[1] Chat bot not responding](https://discord.com/channels/1186424376300679209/1384593638499160124) [[2] Public Keys](https://docs.retellai.com/accounts/public-keys) [[3] Discord message from @itstubzy on 2026-01-13](https://discord.com/channels/1186424376300679209/1294891368505937952/1460668540058079365) ​

ted directly in the Retell dashboard?

### Answer If you've verified all the previous suggestions and the chat widget still isn't responding, here are additional troubleshooting steps based on common issues: 1. Domain Whitelisting Issue A common cause is the public key domain mismatch. The error "Public key is not allowed for this domain" occurs when the domain where the widget is embedded doesn't match what's configured in your Retell dashboard. [(1) ]() [(2) ]() - Navigate to Dashboard → Keys → Public Keys - Click on your public key and verify the exact domain is listed - If you're testing locally, add

localhost

to your allowed domains list 2. Path-Based Domain Limitation If your site loads on a subpath (like

website.com/page/

) , you may only be able to whitelist the root domain (

website.com

) . One user reported this exact issue with Google Sites and WordPress sites loading on subpaths. [(1) ]() , [(3) ]() 3. Check Browser Console for Specific Errors Open DevTools (F12) and look for: -

create-chat 401

error → Public key/domain mismatch -

get-chat/undefined

error → Missing or incorrect agent ID, or the widget script loading before config 4. Verify Agent is a Chat Agent Confirm in your Retell dashboard that you're using a chat agent ID, not a voice agent ID. 5. Test Agent in Dashboard First Use the built-in testing in the agent builder to confirm your agent responds before embedding. If you're still stuck, could you share: - The exact error message from your browser console? - What domain you're embedding on vs. what's in your public key settings? - Whether the agent responds when tes

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer I see you mentioned receiving an error, but you didn't include the actual error message in your message. Could you please share: 1. The exact error message from your browser's developer console (F12 → Console tab) 2. A screenshot if possible Common errors and their meanings: - "Public key is not allowed for this domain" → Your domain isn't whitelisted in your public key settings [(1) ]() , [(2) ]() -

create-chat 401

error → Public key/domain mismatch [(3) ]() -

get-chat/undefined

error → Missing or incorrect agent ID, or the widget script loading before configuration is ready Once you share the specific error, I can help you troubleshoot the exact issue.

​ To learn more, see the sources I considered: [[1] Public Keys](https://docs.retellai.com/accounts/public-keys) [[2] Chat bot not responding](https://discord.com/channels/1186424376300679209/1384593638499160124) [[3] Discord message from @itstubzy on 2026-01-13](https://discord.com/channels/1186424376300679209/1294891368505937952/1460668540058079365) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.