This guide is intended for IT admins and technical users to help diagnose and resolve common issues with the Engage chatbot and chat widget platform. It covers common problems across the agent console, routing, outbound interactions, video and cobrowse tools, authentication, and more.
1. Console Issues
Confirm router type: Twilio, Mitel, SF Omni
Check console version and integration type: New/Old, Integrated (Mitel, SF) or Standalone
Messages not appearing without refresh?
Refreshing may temporarily resolve the issue
Check the browser console and network tab for errors or excessive XHR requests to
pusher
If issues persist, collect this data for escalation
Cramped or squashed UI?
Agent’s screen resolution may be too small
Minimum supported resolution is 1366×768
Embedding the console in Salesforce or Ignite can worsen the problem
Customer view not loading?
Likely caused by iframe restrictions on the customer’s website
Website owner must allow our domain (e.g.,
eu.engage.app
) to iframe the page
Queue timeout message not triggering?
Canned messages referencing missing interaction data (e.g., a “name” field) will fail
Test the canned message in the interaction to confirm it appears
Prefer using safe defaults or interaction data lookups
Websocket fallback message appears?
Indicates missed real-time messages from Pusher
System will fall back to polling and display a warning
Refresh the page to restore real-time events (if not a wider Pusher outage)
2. Routing Issues
Router correctly set up?
Standalone: Check user is in the right queues and groups
Mitel:
Confirm queue is mapped to Ignite correctly
Has the issue been escalated to your channel partner?
Load the Ignite queue page to verify the Ignite API is working
WhatsApp:
Confirm licensing limits have not been reached and the correct license is available.
3. Outbound Interactions
Outbound WhatsApp not sending?
Must use a pre-approved Twilio content template
Add the template to the config in Engage
4. Video Issues
Using Ignite or Salesforce integration?
Requires our Chrome plugin for camera/autoplay permissions
Without the plugin, users may experience video/audio issues
5. Cobrowse Issues
Cobrowse option missing in console?
Confirm it’s enabled under Company Configuration > Agent Experience > Console Feature Configuration
New console requires ECS version 0.32+
Widgets must also be on this version or higher
Cobrowse console shows blank screen?
Likely due to websocket being blocked
CSP must allow:
https://talkative-cdn.com
ws://talkative-ws.com
Cobrowse is slow?
May be caused by a large website payload
Contact support to review rate limits
6. Daily Video Issues
“Loading…” stuck screen?
WebSocket to Daily.co may be blocked — ensure all
daily.co
subdomains are whitelisted
Background effects failing?
Zip file required for effects may be blocked by firewall — allow downloads from
daily.co
CORS/CSP errors with Daily?
May be caused by custom headers (e.g. prototype pollution with
fetch
)A fix from Daily is expected to roll out (notified on 2024-05-16)
7. Console/Interaction Security
Ignite users can view all interactions in the Interaction Logs iframe
Standalone users must use the History tab to review previous transcripts
8. Authentication Issues
Integrated or SSO login?
2FA login issues cannot be bypassed — users must ask account holders to delete/recreate accounts
419 CSRF Token Errors
Caused by expired/invalid tokens
Ensure cookies are enabled
Clear cache or hard refresh (
Ctrl + Shift + R
) may resolve
SSO Issues
Permission changes: check if they're managed via SSO groups
Account provisioning is done via the customer’s SSO provider
“SAML assertion failed” usually indicates an expired certificate
Integrated Login Issues
Verify user is in the correct region
Check for password reset
Email issues:
Verify reset emails were sent
If using Microsoft, check the email quarantine
Check the Engage Notifications channel for bounces
9. User Management
Cannot delete a user?
They may be:
Active in interaction
In an active session or reservation
Affected by an orphaned reservation due to webhook/race conditions
Confirm the user is not active, then escalate to support with the user ID and region
10. Chat Widget Issues
Widget not loading?
Check browser network tab for script loading
Ensure configuration endpoint returns data
If using query parameters for routing, confirm they’re present in the import script
Using URL query parameters
Card rules not working?
Requires widget version 0.42+ with query parameter support enabled
CSP blocks?
Required allowlist entries:
https://eu.engage.app
https://talkative-cdn.com
ws://talkative-ws.com
Is the site a Single Page Application (SPA)?
Check if browser logs persist across page changes
If SPA, use SPA wrapper:
SPA wrapper guide
Other checks:
Are queues online and correctly configured?
Presence changes can take up to a minute to reflect
Business hours and overrides correctly set?
Has the referenced queue been deleted?
For Mitel: verify settings and SSL cert
Programmatic actions pointing to invalid queues?
11. Widget Editor Issues
Data collection forms not showing?
Interaction data label must be “Email” (case-sensitive)
12. Google Analytics Tracking
No GA4 event tracking?
Confirm widget is configured to use GA4 via
gtag
API (not deprecated Universal Analytics)Check Google Tag Manager (GTM) is correctly relaying events
GA4 event integration guide
Nudge data not visible?
Must be enabled in the widget
Widget version should be 0.41+
Tags not sent to GA4?
Review configuration in Company and Queue configs for GA Events Integration
13. Common Error / Status Codes
502 – Load balancer timeout or large payload; escalate if persistent
500 – Application exception; tracked in Sentry (context required for interpretation)
422 – Validation error; inspect failed request in browser dev tools
419 – Expired CSRF token; refresh page or hard reset
403 – Permission denied by policy check
402 – License limit reached (e.g., ECS widget loader)
401 – Unauthorized API call (missing auth token)
400 – Malformed request from client
302 – Redirect (e.g., form validation failure or restricted area)
14. Firewall Allowlisting
Make sure the following domains are allowed through your firewall:
*.pusher.com
*.engage.app
*.twilio.com
*.talkative-cdn.com
*.cloudfront.net
*.talkative-ws.com
*.daily.co
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article