how would you define the success of rappi's in-app chat support system?

Introduction

Defining the success of Rappi's in-app chat support system requires a comprehensive approach that considers multiple stakeholders and metrics. To address this product success metrics 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

Rappi's in-app chat support system is a critical feature within the Rappi mobile application, designed to provide real-time customer support to users of the on-demand delivery platform. This system allows customers to communicate directly with Rappi's support team for order issues, general inquiries, or assistance during the delivery process.

Key stakeholders include:

1. Customers: Seeking quick resolution to their issues
2. Support agents: Aiming to efficiently handle customer queries
3. Rappi management: Focused on customer satisfaction and operational efficiency
4. Delivery partners: May need to be looped into conversations for order-related issues

User flow:

1. Customer encounters an issue or has a question
2. They navigate to the support section and initiate a chat
3. A support agent is assigned and begins the conversation
4. The issue is resolved or escalated as necessary
5. The chat is closed, and the customer may be prompted for feedback

This feature aligns with Rappi's broader strategy of providing exceptional customer service to maintain its competitive edge in the crowded Latin American delivery market. Compared to competitors like iFood or Uber Eats, Rappi's in-app chat aims to offer more immediate and personalized support.

In terms of product lifecycle, the in-app chat support system is likely in the growth or maturity stage, depending on how long it has been implemented and its current performance.