Hi, my assistant's chat responses are not showing in the widget on the website. They are showing in the chat logs. Here's a chat ID "548c30c1-5e4e-4017-b280-2dac6b0b831b". Here's a chat Details "8aad6806-d1ad-4771-8eaa-917c14bfbffa" #1211483291191083018

Try updating your widget code to ensure all required props are set correctly. Here’s a sample configuration for the Vapi widget in chat mode:

html
<vapi-widget
  public-key="your-public-key"
  assistant-id="your-assistant-id"
  mode="chat"
  theme="light">
</vapi-widget>

Double-check that

public-key

and

assistant-id

are correct and that

mode

is set to

"chat"

. For more details, see the [Vapi Web Widget documentation](https://docs.vapi.ai/chat/web-widget). Source: - [Vapi Web Widget documentation](https://docs.vapi.ai/chat/web-widget)

Hi Higgybw, Please try these targeted checks — they cover the most common causes when responses appear in logs but not in the widget: 1. Confirm widget props - Ensure the widget has a valid public key and the correct assistant id: - Link: https://docs.vapi.ai/chat/web-widget 2. Verify assistant visibility for chat - In Dashboard → Assistants, confirm the assistant is published and enabled for chat (not only voice/transient). 3. Check assistant vs. inline config - If using

assistant

(full config) in the widget, note that prop is voice-only. For chat use

assistant-id

and, if needed,

assistant-overrides

. 4. Inspect network & console - Open devtools → Console/Network. Look for widget errors (CORS, 401/403, missing assets) or events like

Couldn't Get Assistant

. - If you see auth errors, confirm the public key is the Dashboard Public API Key (public keys are safe client-side). 5. Confirm session/context usage - The widget uses chat sessions. If you’re testing with server-side chat that used a different session/previousChatId, the widget may create a separate session. Use the widget to start the conversation or supply the same sessionId if needed. 6. Reproduce with the provided chat IDs - Provide the two IDs you sent: - chat id: 548c30c1-5e4e-4017-b280-2dac6b0b831b - chat detail id: 8aad6806-d1ad-4771-8eaa-917c14bfbffa I can check whether those responses were returned to a widget session or only logged server-side (if you want me to investigate, confirm org/account and timestamp). 7. CSS / display conflicts - If network shows the message but it's not visible, check for CSS conflicts on your page that may clip/hide widget message text or icons (z-index, font color). If you want, share: - The exact widget snippet you’re using on the page (sanitize keys if needed) - A console/network screenshot showing any widget errors I’ll inspect the IDs and logs once you confirm.