What Is the Right Cloud Contact Centre Pricing Model for You?

hand holding global connection and cloud icons
343
Filed under - Guest Blogs,

Diogo Almeida Fernandes at Talkdesk explains that it is undeniable that the contact centre market has seen an explosive growth in the adoption of Software as a Service (SaaS) to support operations.

This shift started before the COVID-19 pandemic, benefited from the work from home (WFH) trend, and is here to stay. Gartner cites: “On-premises contact centres will increasingly become technologically inferior compared to their cloud counterparts”.

With the growing adoption of Contact Centre as a Service (CCaaS), determining the most suitable pricing model for your business has become an intricate process requiring data and detailed insights into your company’s modus operandi and leadership mindsets.

Contact Centre Pricing Models.

Currently, there are two primary pricing models offered by vendors:

  • Per user or per seat model. Applies to either a named user (one license corresponds to one designated user) or to a concurrent user (the same concurrent license can be used by any number of individuals, as long as they are not signed in at the same time).
  • Consumption or usage-based model. Based on the amount of time any given user is logged in to the software, regardless of the number of users. Vendors typically offer more beneficial terms for this model when customers commit to a certain volume of consumption.

It is easy to understand the temptation of only paying for what has been used, but context is king here. Although each model has pros and cons, the preferred model depends on factors like the number of agents, shift patterns, number of hours online in the systems, cyclicality of the business, and more.

From a cost-benefit point of view, the contact centre pricing model needs to fit the characteristics of the business. Below are a few examples.

Standard 9 a.m to 5 p.m Operations.

Most business organizations operate during standard business hours—think of public services, financial and education institutions, manufacturing organizations, etc. For these organizations, the best pricing model depends on the number of agents and shift patterns.

For a company that has the same set of 1,000 agents logged into the system for an average of 6 hours a day, a per named user pricing model would be the most cost effective. Choosing the consumption model would be approximately 30% more expensive than on a named basis for the 1,000 licenses.

In this specific case, opting for concurrent licenses would be more cost effective only if the customer had approximately a maximum of 750 agents signed in at the same time. Understanding the business requirements is key to selecting the most cost-effective pricing model.

High Utilization Rate.

There are organizations that operate longer than standard business hours, or even 24/7. That is the case for emergency services, utility companies—to handle, for example, outages—or business process outsourcers (BPOs) that aggregate resources for serving global customers.

In these cases, the utilization rate is most likely close to 100%. Agents are almost always logged in and use the contact centre systems to handle inbound and outbound interactions. The per seat pricing model will always be significantly cheaper than the consumption based pricing model because the fixed cost of buying each license is spread out across an enormous amount of minutes utilized in the system.

Also, for international organizations, contact centre agents may even be spread across different time zones, which means they are not using the systems at the same time, even though the procurement processes are likely to be done conjointly. Each time zone can be considered as a different shift, resulting in two or three shifts, for which a concurrent pricing model would be the most cost-effective.

Seasonal Operations.

Some contact centres that typically operate during standard business hours may experience seasonal spikes. For example, retailers experience Black Friday spikes while hotel chains and airlines have seasonal peaks for summer and winter travel.

In these cases, the contact centres require a significant increase in resources during peak times to handle all customer interactions.

For example, an airline contact centre may normally operate with 250 agents but scales to 400 agents for three months in the summer and two months in the winter. In this scenario, the most cost-effective solution is to purchase temporary/seasonal licenses for those months only.

However, there are time and quantity limits for temporary licenses, so opting for alternative models is a wiser choice. The consumption pricing model could be less expensive if the daily login time is lower than the average 6 hour shift.

However, if shifts are longer than 6 hours, the named per seat pricing model for the entire year is more cost effective, approximately 25% cheaper for 8 hour shifts. Moreover, this also allows the organization to have license bandwidth to increase the number of agents at any time in case of unexpected events.

Part-Time.

There are some contact centre operations that are only active for a couple of hours during the day and the resources allocated for handling customer contacts also work in other areas of the organization. An example of this is a start-up where the teams typically assume several roles.

In these cases, a consumption model may be the right choice, depending on the number of hours that agents are logged in handling customer interactions. If we assume users are logged in 4 hours a day, opting for a consumption pricing model would be more cost effective.

If they work 5 hours a day through the year, a per seat named model could be cheaper, so it really comes down to the expected utilization rate and how many agents are signed in at any given time.

Complexity/Sophistication of Contact Centre Operations.

The level of complexity can also play a factor when considering which pricing model is right for you. As digital channels and AI/ML begin to reshape how corporations interact with their own customers (for example, bots, deflection routines, etc.), there are clear implications for the licensing technologies that are chosen to support those evolving customer experience strategies.

For basic inbound voice contact centres with a limited number of hours of utilization, the consumption pricing model might be a good fit. But digital channels and AI capabilities are increasingly being adopted, which aren’t a good fit for consumption models given they typically run in the background.

Therefore, a more traditional pricing model might be the right choice depending on the sophistication of the contact centre operations.

In conclusion, choosing the right pricing model requires an understanding of each contact centre’s needs and the flexibility to scale up and down according to those needs. Although it is always beneficial to compare license models, the consumption pricing is often a more expensive option.

This blog post has been re-published by kind permission of Talkdesk – View the Original Article

For more information about Talkdesk - visit the Talkdesk Website

About Talkdesk

Talkdesk Talkdesk is a global customer experience leader for customer-obsessed companies. Our contact center solution provides a better way for businesses and customers to engage with one another.

Find out more about Talkdesk

Call Centre Helper is not responsible for the content of these guest blog posts. The opinions expressed in this article are those of the author, and do not necessarily reflect those of Call Centre Helper.

Author: Talkdesk

Published On: 7th Dec 2021
Read more about - Guest Blogs,

Follow Us on LinkedIn

Recommended Articles

Robot with coins in a circle around it
Conversation Intelligence & Automated Quality Management Cost Pricing
A person with a blue and red question mark on either side floating above their hands
The Cost-Benefit of Usage and Unlimited Pricing Models
Five hand drawn light bulbs on wooden steps
Contact Centre AI Maturity Model
Person with laptop sitting on chair near colour wall
Creating a People-First Hybrid Working Model