IT Quickstart | Customer Value Hub

Overview

What you need to know

Make 4 changes so participants can join from company devices: open your firewall, check browsers, check email delivery and complete your security review.

Participants talk with the Savo interviewer in a Signal Session, a voice conversation in their browser that uses their microphone and speaker. The voice connection runs on LiveKit, built on WebRTC, the browser standard for live audio.

Test on company devices. Company networks, VPNs and virtual desktops can block the voice connection, even when the page loads. A test on a personal laptop or home network won't show this.

You (IT)

Make the network, browser and email changes, and run any security review.

Program owner

Leads the launch and runs a test session on a company device once your changes are in.

Have these answers ready

Your program owner will reach out 4 to 8 weeks before launch. They plan the launch date around your answers.

How much time you need

Your lead time for network changes and any security review. This sets the launch date.

Your standard browser

So testing happens on the browser people actually use.

Any virtual desktops

Whether participants use virtual desktop infrastructure (VDI), such as Citrix, since the microphone has to pass through.

A launch-week contact

Someone in IT who can be reached on launch day, in case sessions won't connect.

Network

Allow the Savo platform through your firewall

Add these destinations to your allowlist.

Destination	Port and protocol	What it's for
`*.savo.ai`	TCP 443	Savo app and session pages
`*.livekit.cloud`	TCP 443	Starts the voice connection
`*.turn.livekit.cloud`	TCP 443	Relays voice. Exclude from SSL inspection.
`*.host.livekit.cloud`	UDP 3478	Relays voice
Media ports	UDP 50000 to 60000, TCP 7881	Recommended for audio quality

All destinations and ports above are open
*.turn.livekit.cloud is excluded from SSL inspection

Browsers

Check browser settings

Signal Sessions run in current versions of Chrome, Safari, Firefox and Edge. Chrome and Edge can carry different company policies.

Participants use a current version of Chrome, Safari, Firefox or Edge
The allowlist applies to every browser in use
Browsers can ask for microphone access on *.savo.ai
Browser updates are not held at an older version

If used

Check virtual desktops and VPN

A virtual desktop, such as Citrix, runs the browser on a remote server, not on the participant's own computer.

Virtual desktops pass the microphone and speaker through, or those users join from a phone or tablet
VPN users can reach the voice connection while connected

Check email delivery

The Savo platform sends each participant their own invitation and reminders.

invitation@email.savo.ai is allowlisted, so invites reach inboxes and not spam
Link scanning tools do not open or break session linksEach link belongs to one participant.

Security and access

Complete your security review and set admins

Vendor, security and AI reviews approved
Admins namedEvery admin sees every campaign.

For your review, ask your Savo contact for Savo's architecture diagram, data flow or subprocessor list.

Verify

Confirm your changes work

A test passes only when the tester finishes a full Signal Session on a company device. Make all your changes before the program owner tests. Only the first test session is free, so a test after every change adds cost.

The program owner runs a test session on a company device once all changes are in
The program owner sends you any failed test the same dayInclude a screenshot, the network used and the browser and version.

The phone or tablet backup. If a network blocks the voice connection, the session page shows a QR code. Participants scan it to continue on a phone or tablet and pick up where they left off.

The full device test plan is in the Launch Guide, under Test a full session.

From the Savo Knowledge Base

Resources

Article

Participant Can't Access Their Signal Session

What to check when a session won't start.

Read article