what metrics would you use to evaluate glovo's in-app customer support chat?

Introduction

Evaluating Glovo's in-app customer support chat requires a comprehensive approach to product success metrics. To address this challenge effectively, I'll follow a structured framework covering core metrics, supporting indicators, and risk factors while considering all key stakeholders.

Step 1

Product Context

Glovo's in-app customer support chat is a critical feature within their food delivery and quick-commerce platform. It provides real-time assistance to users experiencing issues with their orders, account, or general inquiries.

Key stakeholders include:

• Customers: Seeking quick resolution to their problems
• Customer support agents: Handling inquiries efficiently
• Product team: Optimizing the chat experience
• Operations team: Ensuring smooth order fulfillment
• Business leadership: Balancing customer satisfaction and operational costs

User flow:

1. User encounters an issue and accesses the chat feature
2. They describe their problem or select from common issues
3. An agent or AI responds, gathering necessary information
4. The agent/AI provides a solution or escalates if needed
5. User confirms resolution or requests further assistance

This feature aligns with Glovo's strategy of providing excellent customer service to drive retention and loyalty in the competitive quick-commerce space. Compared to competitors like Deliveroo or Uber Eats, Glovo's chat support aims to be more responsive and integrated within the app experience.

The in-app chat is in the growth stage of its product lifecycle, with ongoing refinements to improve efficiency and user satisfaction.