Microsoft Software / SaaS India

Meesho

Customer Service Automation · IT Operations Automation

Debdoot Mukherjee, Head of AI and Demand Engineering, Meesho, says, "We were looking for a generative AI solution primarily to turbocharge our customer service function.

We also witnessed a record 16 million app installations during our sale events.
With a vision to enable 100 million small businesses to succeed online, Meesho is democratizing internet commerce and continuously facilitating MSMEs' transition from the offline to the online realm.

Reported impact

Business outcome

Recognizing the transformative potential of generative AI, Meesho's leadership team saw it as a catalyst for improved productivity across diverse business functions.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Meesho built its Microsoft solution to improve customer-service and conversational-support workflows. Debdoot Mukherjee, Head of AI and Demand Engineering, Meesho, says, "We were looking for a generative AI solution primarily to turbocharge our customer service function. Key components included GitHub Copilot delivered dashboards, apps, or copilots to users, and Azure OpenAI Service ran model inference or heavy processing. User prompts and domain content are orchestrated through GitHub Copilot, processed by Azure OpenAI Service, and then delivered through GitHub Copilot so Meesho can return context-aware answers or automation in the flow of work. The stack stayed governed and extensible on Microsoft. Recognizing the transformative potential of generative AI, Meesho's leadership team saw it as a catalyst for improved productivity across diverse business functions.

Data flow

User prompts and domain content are orchestrated through GitHub Copilot, processed by Azure OpenAI Service, and then delivered through GitHub Copilot so Meesho can return context-aware answers or automation in the flow of work.

Solution architecture

2 components · 2 layers
  1. Compute
    • Azure OpenAI Service Runs large language models that generate grounded responses, summaries, and copilots.
  2. Serving
    • GitHub Copilot Assists developers with code generation and software-delivery tasks inside engineering workflows.

Architecture clues

  • Key Microsoft components include GitHub Copilot, Azure OpenAI Service.

Evidence from the source

Debdoot Mukherjee, Head of AI and Demand Engineering, Meesho, says, "We were looking for a generative AI solution primarily to turbocharge our customer service function.
Following this event, Azure OpenAI Service, GitHub Copilot, and vernacular language support for AI models were identified as key technologies to be used in the solution to be deployed.
Recognizing the transformative potential of generative AI, Meesho's leadership team saw it as a catalyst for improved productivity across diverse business functions.
Teams from Meesho and Microsoft worked together to deploy a multi-region, virtual chat agent based on Azure OpenAI Service and GPT-4.
We also witnessed a record 16 million app installations during our sale events.
With a vision to enable 100 million small businesses to succeed online, Meesho is democratizing internet commerce and continuously facilitating MSMEs' transition from the offline to the online realm.
Transparency Evidence & methodology 65/100 reference value · 87% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value65/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Microsoft

    Meesho customer story

    First-party
    https://www.microsoft.com/en/customers/story/1747191591416935394-meesho-azure-retail-en-india
    Source type
    Vendor-published customer story
    Published
    Mar 27, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Mar 27, 2024 · Microsoft · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.