Getting started with network readiness for Volie
Use this guide to learn what your dealership network needs before agents use Volie for calls and Communication Center work. You will understand the Internet capacity, voice-path quality, and firewall checks that help Volie run reliably on your site.
Why teams validate network readiness
Dealerships use Volie for real-time voice in the browser and ongoing Communication Center activity. A fast Internet circuit alone does not guarantee good calls—latency, jitter, packet loss, Wi-Fi instability, WAN congestion, and firewall rules can all affect call quality and agent responsiveness.
Validating network readiness before go-live helps your IT team fix issues early and sets a clear baseline for support if problems appear later.
Before you start
To work through network readiness for Volie, you need:
A dealership Admin or Manager who can coordinate go-live timing
Access to your IT contact or network administrator who can review firewall rules, QoS, and circuit capacity
An agent workstation on the same network path agents will use in production (wired Ethernet is preferred for validation)
What to validate
Network readiness for Volie covers three areas that work together:
Internet capacity — download and upload speeds with headroom for your full dealership environment, not only Volie
Voice-path quality — round-trip time (RTT), jitter, and packet loss on the path to Twilio (Volie's voice provider)
Firewall and connectivity — Twilio media and signaling, plus a stable WebSocket path to realtime.volie.com
Internet capacity by dealership size
The table below lists Volie planning standards for total dealership Internet capacity. These tiers account for DMS/CRM traffic, cloud apps, video meetings, software updates, guest Wi-Fi, and other systems—not Volie alone.
Dealership size | Typical concurrent business users | Minimum download | Minimum upload | Recommended download | Recommended upload |
Small | ~5–25 | 100 Mbps | 50 Mbps | 250 Mbps | 250 Mbps |
Medium | ~25–75 | 250 Mbps | 100 Mbps | 500 Mbps | 500 Mbps |
Large | ~75–150+ | 500 Mbps | 250 Mbps | 1 Gbps | 1 Gbps |
Sites with cloud security cameras, heavy guest Wi-Fi, large software downloads, or centralized VPN/SASE egress may need more capacity than the tier above suggests.
Voice-path quality targets
These targets align with Twilio Voice SDK network requirements. Measure on the agent network path when possible—a nearby speed-test server is not a substitute for the path to Twilio.
Metric | Target | What it means for Volie |
Ping / RTT to Twilio | <100 ms preferred; <200 ms maximum | Higher latency can delay call setup and make conversations feel sluggish |
Jitter | <30 ms | Higher jitter can cause robotic audio, gaps, or inconsistent quality |
Packet loss | <3% | Sustained loss is a voice-quality risk; lower is better |
Normal peak WAN utilization | <70% target | Preserves burst capacity for real-time traffic during busy hours |
Voice QoS | High-priority real-time queue | Strongly recommended on shared or constrained circuits |
Connection type | Business fiber preferred | Symmetric upload/download is strongly preferred for medium and large sites |
Readiness outcomes
After you run the validation steps in How to prepare your dealership network and firewall for Volie, classify your site using these outcomes:
Ready — Meets or exceeds recommended bandwidth; voice-path metrics are within target; Twilio Network Test passes; firewall and QoS requirements are confirmed. Proceed with go-live and keep test results on file.
Conditional — Meets the minimum planning floor but is below the recommended bandwidth target, while voice-path metrics and Twilio testing still pass. You may proceed only with the gap documented and expectations set with IT; monitor closely during launch.
Needs remediation — Below the minimum planning floor, fails Twilio connectivity, exceeds RTT/jitter/loss thresholds, shows repeated instability, or has unresolved firewall or routing concerns. Resolve with IT before treating the site as ready for Volie voice.
A site below recommended bandwidth can still launch when it remains above the minimum and all voice-quality tests pass. A site with excellent raw bandwidth can still need remediation if latency, jitter, packet loss, routing, or firewall behavior is poor.
Limitations
Network readiness planning for Volie has these verified limits:
Bandwidth tiers are Volie operational planning recommendations for the dealership's complete technology environment—they are not Twilio per-call bandwidth requirements and do not guarantee performance on their own.
Each rooftop or site with a different circuit, firewall, or WAN path should be validated independently.
Wi-Fi-first operations require separate validation of coverage, congestion, roaming, and channel utilization in addition to WAN circuit checks.
Next steps
How to prepare your dealership network and firewall for Volie — firewall rules, validation procedure, and go-live checklist
Troubleshooting Volie voice quality and network connectivity — fixes when agents report choppy audio, delayed inbound calls, or connection failures