RNP BUSINESS GUIDES / Applications & premises
Is Starlink good enough for Teams, Zoom and business calls?
THE SHORT ANSWER
Starlink may support business meetings and voice, but the useful test is call quality on your normal devices during a busy working period. Count simultaneous endpoints, include competing uploads and test local Wi-Fi. If calls must survive a circuit failure, measure reconnection through the backup rather than assuming uninterrupted sessions.
01 / Applications & premises
Why is a download speed test incomplete?
A meeting is interactive in both directions. Upload contention, intermittent loss and a weak local wireless connection can matter even when a single download test looks strong. Observe the conversation: delayed responses, missing words, frozen video and unexpected reconnections are more useful commissioning notes than one headline number.
RNP recommends testing a normal meeting while the usual background work continues. Use the actual room system, headset and laptops. A test from a wired laptop near the router is useful for isolating faults, but it does not establish the experience in a distant meeting room.
02 / Applications & premises
How should meeting demand be estimated?
Microsoft publishes Teams bandwidth guidance per endpoint, with recommended video-meeting figures of 2.5 Mbps up and 4 Mbps down. Treat these as Teams planning inputs, not universal specifications for Zoom or every voice system. Consult each application provider for its current requirements.
Count concurrent endpoints and add other traffic. Several people in a room may share one room system, while individual participants joining separately create a different network load. The employee total alone does not describe either situation.
03 / Applications & premises
What should the call trial record?
| Scenario | Observation to retain |
|---|---|
| Ordinary meeting | Audio continuity, video behavior and any reconnects |
| Meeting during a file upload | Whether the competing transfer disrupts interaction |
| Call from each working area | Difference between wired and wireless locations |
| Several simultaneous calls | Behavior under the expected peak concurrency |
| Primary WAN failure | Whether the session survives, reconnects or needs redialing |
| Return to the primary WAN | Any second disruption or unexpected application state |
04 / Applications & premises
What else matters for a business phone system?
Include the phone provider or administrator in the trial. Ask them to confirm the supported network design, authentication and any firewall requirements for the actual service. Test the everyday call workflow, such as transfers or the reception queue, where those features are important.
If the business expects phones to work during a power outage, include handsets, switches and any local phone equipment in the power plan. For safety-critical or emergency calling requirements, have the responsible provider confirm the intended arrangement rather than assuming a general internet test establishes it.
05 / Applications & premises
What should happen if the trial is poor?
- Compare a wired call with the same call over the normal Wi-Fi path.
- Repeat with and without a known competing upload to identify contention.
- Review application diagnostics with the relevant administrator.
- Assess approved traffic prioritization or scheduling of bulk transfers.
- Keep a fallback for essential conversations until the revised design passes.
About this guide
RNP’s planning recommendations are separate from vendor specifications. Sources were checked on October 15, 2026; current plan terms, availability and account-specific offers can change. Illustrative calculations are not installation measurements. RNP confirms project scope, price and local delivery availability after assessment.
PLAN THE INSTALLATION
Turn the question
into a clear brief.
Share the meeting and phone platforms, peak concurrent calls and problem locations.
Request a project review ↗Scope, location, price and availability are reviewed before work is accepted.