Customer network allowlisting for Talkative

Modified on Wed, 24 Sep at 2:11 PM

This guide explains which domains your network should allow and why they are required for Talkative to function correctly.

⁠⁠What domains do you need to allow?

Please allowlist the following domains:

⁠

engage.app

Purpose: Core Talkative application and widget endpoints. Loads configuration, routes interactions, and powers the agent console.
Impact if blocked: Widgets fail to load or render rules. Agent console features may not function.⁠

⁠

talkative-cdn.com

Purpose: Content Delivery Network hosting Talkative static assets used by the widget and console.
Impact if blocked: Slow or failed asset loads leading to broken UI or features.⁠

⁠

talkative-ws.com

Purpose: Talkative WebSocket endpoints for real-time events where applicable.
Impact if blocked: Real-time updates degrade or fall back to polling. Delayed message delivery and status updates.⁠

⁠

pusher.com

Purpose: Managed realtime transport for chat messages, dashboards, and widget events in some flows.
Impact if blocked: Messages appear delayed, dashboards require refresh, “realtime” features stop updating.⁠

⁠⁠

twilio.com

Purpose: Telephony and messaging services such as TaskRouter, SMS, WhatsApp, PSTN.
Impact if blocked: Interactions may not route to agents. SMS or WhatsApp messages fail to send or receive. Presence and task events can be affected.⁠

⁠⁠

daily.co

Purpose: Video calling, video recordings and optional background effects.
Impact if blocked: Video rooms fail to start or remain stuck “loading”. Background effects cannot be downloaded.⁠

⁠⁠

cloudfront.net

Purpose: AWS CloudFront used by underlying assets and dependencies.
Impact if blocked: Static or media resources may intermittently fail to load, causing UI or feature issues.⁠

⁠