Local councils in the UK public sector are under increasing pressure to deliver seamless, easy-to-use services, which are accessible to a diverse demographic, as cost effectively as possible. Councils in England will face an overall funding gap of £6.5 billion by 2025, even before COVID-19 is factored in. Coupled with this deficit, local councils are expected to deliver public services that emulate the end-user experience constituents receive from private businesses.

Facing the impact of the pandemic as we get into 2021, keeping employees engaged is a top priority and challenge for business leaders and enterprises across the globe. Simply put, organizations that do not provide easy accessible tools for enabling online collaboration and steady communication among teams may see its employees disengage and lose motivation.

The World Wide Web is for everyone, right? Sadly, when it comes to digital experiences, it’s more of a bob and weave if you are not a ‘typical’ user. Which is why inclusivity in design is much more than a buzzword now. As we edge toward a digitally native population with a vibrant and varied demography of people who are connected by a digital environment, it’s time to question some of the design assumptions we have.

In this blog (Part III), we will discuss the motivation and high-level architecture of the DBaaS Backup and Recovery procedure for databases hosted on DBaaS. This blog discusses the motivations behind the Backup/Recovery process and it’s high-level design and architecture of the various components that constitute it.] These are the high-level motivations/goals for the Backup and Recovery design for DBaaS. There are two major design components.

[In part I of this blog series we saw an overview of our DBaaS design. In this blog (part II) we discuss the automated MySQL primary failover design in some detail.] We use the hashicorp consul and a custom consul watcher service, along with the orchestrator service, to inject proxySQL route changes in the event of a MySQL primary failure in a shard. Consul cluster

Teams at Freshworks primarily use MySQL for their database needs. Freshworks being an AWS shop, RDS MySQL has been our primary, go-to solution. Sometime back a team was formed and tasked with building a self-hosted DB solution. We called ourselves the DBaaS (Database as a service) team and started with a DBaaS solution for MySQL. In this blog post (part I of the series) we discuss the motivation and high-level architecture of the DBaaS solution.

Much like every other aspect of virtually running a business, technology has drastically changed customer service. There are constantly new channels for customers to reach out to businesses. An important addition to this growing list of channels is a customer service chatbot. In this blog, we talk about everything you need to know about a customer service chatbot.

If businesses were previously skeptical about the potential of chatbots in customer service, there is no longer any question about it. The pandemic has pushed businesses to mainstream AI and different types of chatbots for varied objectives. With evasive measures such as cost cuts, chatbots have not just helped businesses stay afloat but also garner the goodwill of customers and ROI.

“Customer needs serve as the ‘north star’ for most product leaders”, especially those who are always striving to leverage customer feedback to build the best products. An important part of this customer feedback naturally lands in support tools like Freshdesk, but your company actually has as many feedback channels as you have customer touchpoints and internal teams.

When it comes to customer service scripts, practitioners are as divided as people are about pineapple on pizza. The benefits of using customer service scripts are manifold, but there are some serious downsides too, like sounding robotic or not displaying enough empathy. However, when used wisely, scripts can be very helpful to customer service representatives. In this blog, we cover everything you need to know about customer service scripts.