Troubleshooting

• Confirm snippet is before </body> and widgetKey is correct
• Add your domain under Widget Settings → Allowed domains
• Open browser DevTools → Console for errors
• Ensure embed.js URL loads (check Network tab)

apiBase must match your Wiretalk server. Production: https://wiretalk.tech/api. Embed script: https://wiretalk.tech/build/assets/embed.js

Add your production domain to allowed domains. Clear browser cache after deploy.

Error: violates Content Security Policy directive "frame-ancestors 'self'"

• Use URL https://www.wiretalk.tech/agent/embed — not homepage or /dashboard
• Confirm your parent site domain is approved for agent embed (contact admin@wiretalk.tech with the exact URLs you embed from)
• Hard-refresh the parent page after any domain allowlist change
• If the inbox looks squeezed to the left with empty space on the right, hard-refresh the iframe — embed layout now sizes from the iframe width, not the browser window
• Set iframe width to 100% (or at least 900px) for side-by-side chat list + conversation

Deploy latest code with CSRF exemptions for bearer-token API calls. Hard-refresh the iframe (Ctrl+Shift+R).

• Pass visitor: { name, email, phone } in window.wiretalkConfig — see the embed identity guide
• Ensure field keys match what you pass (built-in keys are name, email, phone)
• For data lookup login, confirm your parent row includes recognizable column names such as email or full_name
• Pre-filled identity should also appear in the Book a demo slot picker — enable Appointments under Widget Settings first

The delay applies per visitor from their first visit timestamp. Returning visitors who already submitted the form are skipped. Clear site data or use an incognito window to test the delay window as a new visitor.

• Enable Data lookup and configure a read-only database connection — see the Data lookup guide
• Turn on Visitor account login and configure the parent resolver table/column
• Map at least one table under Filter record search with a valid link_column to the parent account
• The visitor must be logged in — the button appears in follow-up suggestions after login

• Confirm the visitor completed account login (account_login.logged_in on their profile)
• Verify link_column on filter tables matches the parent account key used at login
• Check filter presets (txn, UTR, status, date range) match your column names in the dashboard
• Review execution logs under Dashboard → Data lookup → Logs

Filter record responses are HTML tables rendered by the widget. If you see literal tags, hard-refresh the widget (Ctrl+Shift+R) to load the latest embed script. Agent inbox messages use the same trusted embed renderer.

This was fixed in recent widget builds — ensure your site loads the latest embed bundle (clear CDN/cache if you proxy static assets). Bot follow-up suggestions dedupe by label; only one button should appear per conversation turn.

• Add app:your.bundle.id to Allowed Domains — not a website URL
• Pass platform and app_id query params on the popout URL
• See the mobile WebView guide

Enable DOM storage in your WebView (domStorageEnabled on Android, default on iOS). Persist visitor_uid from the widget:ready bridge event and pass it as ?visitor_uid=… on the next load, or use bridge storage:set messages.

Listen for unread:count bridge events from the WebView. On Android, register a WiretalkAndroid JavaScript interface. On iOS, add a wiretalk WKScriptMessageHandler.