Try : Insurtech, Application Development

AgriTech(1)

Augmented Reality(20)

Clean Tech(8)

Customer Journey(17)

Design(43)

Solar Industry(8)

User Experience(66)

Edtech(10)

Events(34)

HR Tech(3)

Interviews(10)

Life@mantra(11)

Logistics(5)

Strategy(18)

Testing(9)

Android(48)

Backend(32)

Dev Ops(11)

Enterprise Solution(29)

Technology Modernization(7)

Frontend(29)

iOS(43)

Javascript(15)

AI in Insurance(38)

Insurtech(66)

Product Innovation(57)

Solutions(22)

E-health(12)

HealthTech(24)

mHealth(5)

Telehealth Care(4)

Telemedicine(5)

Artificial Intelligence(143)

Bitcoin(8)

Blockchain(19)

Cognitive Computing(7)

Computer Vision(8)

Data Science(19)

FinTech(51)

Banking(7)

Intelligent Automation(27)

Machine Learning(47)

Natural Language Processing(14)

expand Menu Filters

Business Continuity for Call-Center Operations: Case Study

3 minutes, 39 seconds read

Coronavirus outbreak has led to prolonged lockdown in several countries, which has crippled many back-office operations. The Government of India imposed a nationwide lockdown (currently 40 days). Because of travel restrictions and health concerns, customer queries are increasing exponentially. Companies dependent on call-centres are struggling to deploy work from home solutions and their business continuity plans. 

Most companies are not prepared for work-from-home arrangements, but there are exceptions. Those with the right strategy and timely action are able to keep their business operationally afloat. Before we delve into the case study, let’s take a quick look at the current situation of call centres.

COVID-19 is testing call-centre businesses. How?

Voice-services are facing a tough time transitioning to a work-from-home model. Companies are not willing to allow access to private and sensitive data outside of the protected office premises. 

Teleperformance, a specialized omnichannel customer experience management company, was able to allow mobility to only 50% of its employees by the first week of April (2nd week of lockdown). The company aims at managing 66% of operations remotely by mid-April. 

This raises a question — why not 100%?

Most of the companies lack the digital infrastructure and a rigid business continuity plan. For instance, the airline business relies heavily on call-centres. After coronavirus outbreaks and resulting lockdowns, most of the call-centres failed to respond to increasing customer queries. To continue communication with customers and support them in whatever ways possible, many airports turned to social media. Delhi’s Indira Gandhi International Airport had over 3.5 million social media engagements during the period.

But, what’s the major limiting factor for adopting virtual call-centre models?

Virtual call-centre adoption challenges

Theoretically, technology can simplify call-centre operations with mobility solutions. But mobility requires an uninterrupted internet connection and developing countries like India struggles for it. Telcos are surely rushing to fill the gaps in customer communications; the fact is— only 2-3% of Indians use wired broadband and the majority of users rely on mobile data. 

The Telcos infrastructure here is designed and built to operate on 75% network capacity utilization. But, due to lockdown, many cities are witnessing 90-100% load capacity and circles like Karnataka are stretching beyond 100% capacity. The country’s inadequate telcos facility is also a limiting factor for setting up virtual call-centres.

Migrating from traditional to virtual operations (ensuring workplace mobility) will require moving the core systems to the cloud. During times like this, the frailed supply-chain defies the thought of procuring devices to achieve 100% mobility.

Despite the aforementioned challenges, some voice-service extensive organizations managed to seamlessly implement mobility at work. 

[Related: Enterprises investing in Workplace Mobility Can Survive Pandemics]

Ensuring call-centre business continuity during a lockdown: a case study

India’s Leading Health Insurer— Religare demonstrated its preparedness against the COVID-19 situation. A major part of the insurer’s customer servicing relies on call-centre based communication, which would have become operationally impossible amidst the ongoing lockdown. To respond to this critical situation and remain operationally afloat, Mantra implemented a call-centre mobility solution with quick turn-around time.

In a typical call centre, the team leader manages and supports callers to handle customer queries. Now that the workforce is operating remotely, the critical question before the company was how to make information available to the callers.

A new virtual call-centre (computer telephony/dialer) system was implemented in the organization’s Lead Management System, which manages the complete customer journey. Through this cloud-based solution, the necessary information is always available to the caller, also eliminating dependencies. 

Companies are sceptical to allow access to private data outside of on-premise systems. To ensure information security and privacy, the new call centre application allowed only required caller IPs, service APIs and Dialer APIs for remote access to the platform.

[Related: The impact of COVID-19 on the global economy and insurance]

Merits of the case

40% of businesses do not reopen after a disaster. Of those who do, 25% reopen and fail. The main reason is firms are unprepared to withstand the short and long term effects of severe business disruptions. 

That’s why leaders emphasize on business continuity plans (BCP).
The benefits of BCP abstracts to –

  1. Protecting the safety of employees.
  2. Maintaining customer service by minimizing interruptions of business operations.
  3. Protecting assets and brand.
  4. Preventing environmental contamination.
  5. Protecting the investment and leveraging the chance to survive and thrive post-disaster.

To secure operational continuity, organizations need to proactively invest in digital workplaces that remain virtually uninterrupted even during Pandemics. 

Do you need help in ensuring business continuity? We’re listening to you. Write to us at hello@mantralabsglobal.com.

Cancel

Knowledge thats worth delivered in your inbox

Why Netflix Broke Itself: Was It Success Rewritten Through Platform Engineering?

By :

Let’s take a trip back in time—2008. Netflix was nothing like the media juggernaut it is today. Back then, they were a DVD-rental-by-mail service trying to go digital. But here’s the kicker: they hit a major pitfall. The internet was booming, and people were binge-watching shows like never before, but Netflix’s infrastructure couldn’t handle the load. Their single, massive system—what techies call a “monolith”—was creaking under pressure. Slow load times and buffering wheels plagued the experience, a nightmare for any platform or app development company trying to scale

That’s when Netflix decided to do something wild—they broke their monolith into smaller pieces. It was microservices, the tech equivalent of turning one giant pizza into bite-sized slices. Instead of one colossal system doing everything from streaming to recommendations, each piece of Netflix’s architecture became a specialist—one service handled streaming, another handled recommendations, another managed user data, and so on.

But microservices alone weren’t enough. What if one slice of pizza burns? Would the rest of the meal be ruined? Netflix wasn’t about to let a burnt crust take down the whole operation. That’s when they introduced the Circuit Breaker Pattern—just like a home electrical circuit that prevents a total blackout when one fuse blows. Their famous Hystrix tool allowed services to fail without taking down the entire platform. 

Fast-forward to today: Netflix isn’t just serving you movie marathons, it’s a digital powerhouse, an icon in platform engineering; it’s deploying new code thousands of times per day without breaking a sweat. They handle 208 million subscribers streaming over 1 billion hours of content every week. Trends in Platform engineering transformed Netflix into an application dev platform with self-service capabilities, supporting app developers and fostering a culture of continuous deployment.

Did Netflix bring order to chaos?

Netflix didn’t just solve its own problem. They blazed the trail for a movement: platform engineering. Now, every company wants a piece of that action. What Netflix did was essentially build an internal platform that developers could innovate without dealing with infrastructure headaches, a dream scenario for any application developer or app development company seeking seamless workflows.

And it’s not just for the big players like Netflix anymore. Across industries, companies are using platform engineering to create Internal Developer Platforms (IDPs)—one-stop shops for mobile application developers to create, test, and deploy apps without waiting on traditional IT. According to Gartner, 80% of organizations will adopt platform engineering by 2025 because it makes everything faster and more efficient, a game-changer for any mobile app developer or development software firm.

All anybody has to do is to make sure the tools are actually connected and working together. To make the most of it. That’s where modern trends like self-service platforms and composable architectures come in. You build, you scale, you innovate.achieving what mobile app dev and web-based development needs And all without breaking a sweat.

Source: getport.io

Is Mantra Labs Redefining Platform Engineering?

We didn’t just learn from Netflix’s playbook; we’re writing our own chapters in platform engineering. One example of this? Our work with one of India’s leading private-sector general insurance companies.

Their existing DevOps system was like Netflix’s old monolith: complex, clunky, and slowing them down. Multiple teams, diverse workflows, and a lack of standardization were crippling their ability to innovate. Worse yet, they were stuck in a ticket-driven approach, which led to reactive fixes rather than proactive growth. Observability gaps meant they were often solving the wrong problems, without any real insight into what was happening under the hood.

That’s where Mantra Labs stepped in. Mantra Labs brought in the pillars of platform engineering:

Standardization: We unified their workflows, creating a single source of truth for teams across the board.

Customization:  Our tailored platform engineering approach addressed the unique demands of their various application development teams.

Traceability: With better observability tools, they could now track their workflows, giving them real-time insights into system health and potential bottlenecks—an essential feature for web and app development and agile software development.

We didn’t just slap a band-aid on the problem; we overhauled their entire infrastructure. By centralizing infrastructure management and removing the ticket-driven chaos, we gave them a self-service platform—where teams could deploy new code without waiting in line. The results? Faster workflows, better adoption of tools, and an infrastructure ready for future growth.

But we didn’t stop there. We solved the critical observability gaps—providing real-time data that helped the insurance giant avoid potential pitfalls before they happened. With our approach, they no longer had to “hope” that things would go right. They could see it happening in real-time which is a major advantage in cross-platform mobile application development and cloud-based web hosting.

The Future of Platform Engineering: What’s Next?

As we look forward, platform engineering will continue to drive innovation, enabling companies to build scalable, resilient systems that adapt to future challenges—whether it’s AI-driven automation or self-healing platforms.

If you’re ready to make the leap into platform engineering, Mantra Labs is here to guide you. Whether you’re aiming for smoother workflows, enhanced observability, or scalable infrastructure, we’ve got the tools and expertise to get you there.

Cancel

Knowledge thats worth delivered in your inbox

Loading More Posts ...
Go Top
ml floating chatbot