WorkBuzz Dialogue is a web application that enables video, voice and text feedback to be collected across your organisation. A ‘Creator’ creates a video prompt and shares it across the business, inviting contributions from others. Contributors can choose to reply using video, voice or text, and may opt to respond anonymously, hiding their image, voice and name from the Creator.

For this to work smoothly in an enterprise environment, your IT and security teams will need to complete a short set of configuration steps covering:

All devices used to record or submit video and voice responses must meet the following minimum specifications.

Dialogue supports the following browsers. We recommend enabling automatic updates so all users remain within the supported range.

Please whitelist the following domains and sub-domains in your firewall, web proxy and endpoint protection platforms. Do not throttle, inspect or interrupt HTTPS traffic to these addresses.

In addition to domain whitelisting, please verify the following:

· WebRTC real-time media traffic must not be blocked — this is required for all video and voice recording features

· SSL / deep packet inspection must be disabled for Dialogue domains to prevent certificate errors and broken streams

· Custom headers used by the Dialogue API (e.g., X-Dialogue-Context) must be forwarded unchanged by all proxies. Web proxies must not strip headers, break WebSocket connections, or rewrite Dialogue API calls.

· TLS 1.2 or higher must be supported on all client devices and any forward proxies (TLS 1.3 preferred)

Dialogue uses custom HTTP headers (X-Dialogue-*) to operate correctly. Web security proxies and secure web gateways (e.g., Skyhigh Security, Zscaler) may strip non-standard headers by default, which will cause the application to malfunction.

Allow and preserve all HTTP headers matching the X-Dialogue-* prefix through your proxy or secure web gateway. These headers must not be inspected, modified, or stripped.

Vendor-specific guidance

Other proxies and secure web gateways (e.g., Broadcom ProxySG, Palo Alto Prisma Access, Cisco Umbrella) may behave similarly. Consult your vendor documentation for header pass-through configuration.

Ensure your proxy preserves these headers on outbound requests to:

https://api.dialogue.workbuzz.com

We provide a compatibility test page that verifies your browser, hardware and network configuration in a single step. Please run this on representative devices from your estate — both desktop and mobile — before go-live.

Download the completed report from the test page and return it to support@dialogue.workbuzz.com before sign-off.

Dialogue sends loop invitations and notifications from a fixed sender address. Please whitelist the sending IP and address in your email gateway and spam filter, and ensure delivery is not throttled at scale.

Dialogue emails frequently contain links to loops, user login area, and other platform features. Which are routed through our subdomain. To prevent emails from being blocked or flagged, please add this domain to your allow list.

Dialogue supports SSO via Microsoft Entra ID and Google, using OpenID Connect (OIDC). SSO is optional but recommended for enterprise deployments as it removes the need for separate credentials and aligns with your existing MFA policies.

To enable Microsoft SSO, we need your Entra Tenant ID. You can find this in the Azure Admin portal or at https://www.whatismytenantid.com/. Once confirmed, we will send you a consent link for a Global Administrator to click and approve the WorkBuzz Dialogue application in your tenant.

Please also provide all allowable email domain names for your organisation (e.g. @yourcompany.com). These are required to route authentication correctly.

To enable Google SSO, please provide your organisation’s email domain name(s) as part of onboarding. We will configure OIDC authentication against your Google Workspace tenant.

If you wish to connect Active Directory for distribution list management (see Section 8), the following Microsoft Graph permissions are required:

We recommend authorising User.Read.All for the best experience. This enables filtering of distribution lists by manager and department, which is particularly useful for larger organisations.

Permissions are added via: Azure › App Registrations › WorkBuzz Dialogue › API Permissions › + Add a permission

Dialogue allows you to create groups of recipients who can be invited to participate in a loop. Groups can be built in three ways:

The following fields are used when building groups:

A CSV template is available to download directly from the Dialogue platform.

Contact your WorkBuzz onboarding manager or email [email protected]. We are happy to join a call with your IT or security team to work through any of the above.