The day in the life of a customer support agent is not an easy one. Between staying on top of assigned tickets, dealing with angry customers, completing complicated back-end processes, answering repetitive customer inquiries, and adhering to strict company policies, there’s plenty of potential headaches that can spring up. Without adequate support and resources, 74% of customer support agents are susceptible to burnout1.
This is part two of a three-part content series between Freshworks and Textline. You can read part one: “9 reasons your customers want to be able to text support” here. It shouldn’t come as a surprise that a photo can greatly enhance any text message you’re trying to send. That includes messages you send in a customer support role to help customers solve a problem or those texts your customers send you.
2020 taught us that predicting the future can be a risky business. But that’s not stopping people from looking into the crystal ball. In fact, the search term “2021 retail trends” on Google yields a measly 416 million results. Given this, you might wonder why we’re doing this. For starters, we’ll limit the scope of this blog to customer experience in retail and e-commerce.
Jewelry is meant for special occasions, and often customers want to see and feel the product before making that special purchase. Major players in the jewelry market like Tiffany’s and Cartier started out with purely physical retail stores, before eventually incorporating online identities. That’s why Blue Nile, one of the first companies in the jewelry space to establish an online-first business, has had to work harder than most in making their business a success.
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.
