Calculating Phone Service Rates Accurately in Your Business

A phone bill often only seems expensive after it’s already been paid. Yet unnecessary costs rarely result solely from a high per-minute rate. More often than not, they stem from ill-suited flat-rate plans, forgotten add-on services, international calls, or a phone system that doesn’t fit the company’s operations. Who Calculating Phone Plans Correctly Therefore, [the company] considers not only the price per connection but also the entire communications architecture.

For Swiss SMEs, distributed teams, and organizations with multiple locations, one simple question ultimately matters: What does a reliably accessible workspace actually cost per month? The answer includes phone numbers, SIP trunks, cloud PBX licenses, call volume, Microsoft Teams integration, internet quality, and operations. Only this comprehensive view allows for predictable costs.

Start with calling habits, not the price list

The cheapest rate isn't necessarily the most cost-effective. A company with few but long international calls requires a different cost calculation than a service team with many short calls to Switzerland. Similarly, the bill changes when employees make calls via Making Calls in Microsoft Teams, work on the go, or initiate customer calls from the CRM.

The most important basis is actual usage data. Review at least the last three to six months: How many users make calls regularly? What numbers are dialed? How many call minutes are there per user, location, and country? And when do peak periods occur?

Don't just focus on outbound calls. Inbound calls, call queues, IVR menus, call forwarding, and simultaneous ringing can also affect capacity or licenses. For example, a company that operates a central service number with multiple teams requires a different setup than one where every workstation is directly accessible.

The Five Cost Categories of a Robust Cost Estimate

A clear breakdown of costs distinguishes between fixed and variable costs. This makes it clear which expenses increase with growth and which ones are incurred regardless of call volume.

• Connections, SIP Trunks, and Phone Numbers
• Cloud PBX or telephone system licenses per user or feature
• Call Rates for Switzerland, Cell Phones, and International Destinations
• End devices, such as IP phones, headsets, or conference phones
• Implementation, Porting, Configuration, Security, and Ongoing Support

This breakdown helps avoid a common comparison mistake: A plan with a very low monthly fee can end up being expensive if international calls, cell phone minutes, or services are billed separately. Conversely, a flat-rate plan isn't worth it if it regularly goes unused.

Flat rate or per-minute billing?

The right choice depends on your usage profile, not on a general rule. A flat rate offers predictability. It is particularly well-suited for teams with a consistently high call volume within the included countries and networks. Sales, customer service, scheduling departments, and medical practices often benefit from this because phone costs do not increase with every additional customer inquiry.

Billing by the minute This approach often makes more sense when only a few employees make calls, calls occur irregularly, or a large portion of communication takes place via Teams, email, and tickets anyway. This model can also be advantageous for seasonal businesses. The key factor is whether the monthly base fee for the flat rate is covered by the call costs actually saved.

A simple calculation can help: Multiply a user’s average monthly minutes by the price per minute and compare the result with the flat rate. If the difference is only a few francs, the administrative benefit is what counts. A flat rate reduces the administrative burden and protects against unexpected additional costs. If there’s a significant difference, the per-minute option is more economical.

Example: An employee makes 450 minutes of calls per month to Swiss landline and cell phone networks. At a rate of 0.08 francs per minute, this results in 36 francs in variable costs. If the corresponding flat-rate plan costs 29 francs, it’s worth it. If the same employee makes only 90 minutes of calls, the variable costs amount to 7.20 francs. In this case, choosing the flat-rate plan would primarily be a decision for budget stability, not for the lowest price.

Treat international calls separately

International calls skew many rate comparisons. A national flat-rate plan often does not cover international calls, or covers them only partially. Companies with suppliers, branches, or customers abroad should therefore evaluate the most frequently called countries individually. Calls to cell phone numbers are particularly relevant, as they can be significantly more expensive than landline calls, depending on the country.

If only a few employees regularly make international calls, the entire company does not need to be on the same rate plan. Role-based models are often more efficient: The reception department receives predictable domestic service, the sales department gets an appropriate international component, and individual specialists are billed by the minute. This provides cost transparency without unnecessary flat rates.

Calculating phone service rates correctly means factoring in infrastructure costs

An affordable calling plan won’t solve quality issues if your internet access, network, or security strategy aren’t up to par. VoIP calls don’t require extreme bandwidth, but they do need a stable connection with low latency, proper prioritization, and sufficient reliability. Interruptions, poor voice quality, and dropped calls cost more in customer relations than a small difference in the per-minute rate.

Therefore, you should also consider business-grade Internet, network Quality of Service, firewall rules, and, if necessary, a session border controller (SBC). An SBC protects the communication boundary, manages connections, and facilitates the secure integration of SIP trunks or Microsoft Teams. Whether a separate SBC solution is necessary depends on the existing architecture. With an integrated cloud PBX, the effort involved can be reduced, while complex multi-site environments often have specific requirements.

Redundancy must also be factored in. For a business where availability is critical, a second Internet connection or mobile backup may be a good idea. The additional monthly costs are offset by the risk of being unable to receive orders, service requests, or emergency calls in the event of a line outage.

Don't Pay Twice for Licenses and Collaboration

Microsoft Teams is used extensively in many companies, but not always as a full-fledged telephony channel. This leads to duplicate systems: Employees communicate internally via Teams but switch to separate softphones or desk phones for external calls. This can result in additional training, more support cases, and duplicate licenses.

Therefore, determine which features users actually need. Does every person need a physical IP phone? Is a Teams client with a headset sufficient for mobile employees? Are group calls, a busy lamp field, IVR, call queues, or CTI integration with CRM and ERP required? These features are no trivial matter. They determine which PBX licenses and which configuration are required.

Native Teams integration can reduce licensing and operational costs if no additional add-ons or separately managed components are required. At the same time, not every organization needs to completely replace its existing phone system. If the hardware is functioning properly and the requirements are clear, a phased migration may make more sense than an immediate, complete overhaul.

Create a cost model for each workstation

When making a purchase, a monthly price per user is helpful, provided it is calculated accurately. Add up the prorated costs for the telephony license, connection or SIP capacity, call charges, phone number, handsets, support, and infrastructure. You should spread one-time project costs—such as number porting, setup, training, and network adjustments—over a realistic time frame, such as 36 or 48 months.

This does not result in an artificially low starting price, but rather provides a solid basis for decision-making. Always compare two quotes over the same time period and using the same assumptions. If one quote already includes number porting, IVR and call queue configuration, and personal support, while another lists these items separately, the monthly prices alone are not comparable.

Also, ask about scalability: How much does an additional user cost? How quickly can a number be activated? What happens if a location changes? Growing companies, in particular, benefit from a solution that can be expanded without a large upfront investment.

Continue to monitor costs after implementation

The initial estimate is just the starting point. After three months, check whether the projected call volume is accurate. Review unused licenses, unusually high international costs, and features that are missing or never used. If there are changes to the team, a new branch office, or increased use of Microsoft Teams, the pricing plan should also be reviewed again.

Winet helps companies evaluate telephony, cloud PBX, SIP trunks, Teams integration, and network infrastructure as a cohesive solution. This ensures not only that the price per minute is transparent, but also that the service remains accessible on a day-to-day basis.

A good plan adapts to your business—not the other way around. By planning your usage, infrastructure, and future needs together, you create room for growth without losing control of costs every time you add a new phone number or workstation.