Natter is a browser-based platform that relies on real-time audio, video, and data communication to facilitate live conversations.

While most organisations can successfully access Natter without additional configuration, enterprise environments often include security controls, network policies, and routing decisions that can influence how real-time communication services behave.

This guide outlines common deployment considerations, validation approaches, and troubleshooting patterns observed during enterprise onboarding.

This article is intended for:

You may find this guide helpful if:

Many organisations validate Natter using a small group of representative users before broader deployment.

This approach is highly effective, but it is important to recognise that enterprise environments often contain multiple network paths and user types.

Examples may include:

As a result, successful testing in one environment does not always guarantee identical behaviour across every location or network path.

Where possible, we recommend validating a representative sample of users before large-scale adoption.

Some organisations choose to implement network policies that optimise access to Natter.

Depending on your environment, this may include reviewing:

The latest technical requirements, including any allowlisting guidance, are maintained within the Natter Readiness Portal and should be considered the authoritative source of network configuration information.

If you are unsure whether your organisation has completed these steps, Natter can work directly with your IT team to review readiness and deployment requirements.

One of the most common indicators of a network-related issue is when Natter functions correctly from a home network but experiences issues from a corporate office, client site, or VPN-connected environment.

In these situations, differences in routing, security controls, or network policy are often contributing factors.

Users within the same organisation are not always routed through identical infrastructure.

Differences in location, VPN gateways, regional policies, security tooling, or network architecture can occasionally result in inconsistent behaviour between users.

Comparing working and non-working environments is often one of the fastest ways to identify the source of an issue.

Organisations operating across multiple countries or regions may see different behaviour depending on where users connect from.

This is particularly relevant when onboarding has only been validated in a limited number of locations or when network policies differ between regions.

VPN platforms can introduce additional routing, filtering, and security controls.

If permitted by your organisation, comparing the experience with and without a VPN connection can provide valuable troubleshooting information.

Before large-scale usage, we recommend validating Natter using a representative group of users and environments.

This may include:

Where required, Natter can also facilitate a Live Natter Test Session to validate connectivity, audio, video, and user experience prior to wider rollout.

If engaging Natter Support, the following information can significantly accelerate investigation:

Where possible, providing information from both working and non-working environments is particularly valuable.

Natter regularly works alongside IT, Security, and Networking teams during onboarding, deployment, and troubleshooting activities.

We can assist with:

For assistance, please contact: [email protected]

- Run the Natter Tech Check

- Understanding Your Tech Check Results

- Troubleshooting Internet & Network Issues

- Live Natter Test Sessions & Natter Ready Validation