Skip to main content
Challenge

Build a Vernacular Voice Grievance Transcript and Escalation Router

Convert vernacular voice transcripts from rural buyers into structured Beckn network dispute filings. Map colloquial complaint descriptions into standardized ONDC issue categories.

Workflow AutomationHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Convert vernacular voice transcripts from rural buyers into structured Beckn network dispute filings. Map colloquial complaint descriptions into standardized ONDC issue categories.

Rural buyer support specialist

Receive regional language transcript logs capturing buyer delivery complaints.

Normalize colloquial Hindi or regional phrasing into standardized grievance attributes.

Map complaint entities into Beckn core post-fulfillment issue schemas.

Publish an escalation package with dispute severity scores for operations teams.

Terminal or web workbench presenting original audio transcripts, translated dispute claims, and mapped Beckn schema fields.

Assemble mock regional audio transcripts using standard Bhashini ISO-639-1 language codes paired with synthetic dispute scenarios. Starter examples below are synthetic. They are not downloaded records.

Bhashini documentation Uses Bhashini pipeline standards for Indian language code handling (such as hi, en) and ASR/NMT task separation.

dspy, fastapi. DSPy compiles robust prompt pipelines to extract standardized categorical data reliably from colloquial regional transcripts. Multilingual model adept at Indian language transcript understanding and structured extraction.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Accurately translates informal complaints into one of five standard Beckn dispute codes.

Captures ISO language code metadata according to Bhashini API conventions.

Rejects transcripts that fail minimum intelligible length thresholds.

```json [ { "input": { "transcript_text": "Mera packet phata hua mila aur andar ka tel beh gaya tha.", "detected_lang": "hi", "order_id": "ORD-5541" }, "expected_output": { "mapped_category": "PACKAGING_DAMAGED", "language_code": "hi", "order_id": "ORD-5541", "severity": "HIGH", "escalation_recommended": true } }, { "input": { "transcript_text": "Hello?", "detected_lang": "hi", "order_id": "ORD-2201" }, "expected_output": { "mapped_category": "UNINTELLIGIBLE", "language_code": "hi", "order_id": "ORD-2201", "severity": "NONE", "escalation_recommended": false } } ] ```

Processes synthetic voice logs only; strictly avoids retaining personally identifiable biometric voice samples. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Processes synthetic voice logs only; strictly avoids retaining personally identifiable biometric voice samples. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Accurately translates informal complaints into one of five standard Beckn dispute codes. Captures ISO language code metadata according to Bhashini API conventions. Rejects transcripts that fail minimum intelligible length thresholds.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Receive regional language transcript logs capturing buyer delivery complaints. Normalize colloquial Hindi or regional phrasing into standardized grievance attributes. Map complaint entities into Beckn core post-fulfillment issue schemas. Publish an escalation package with dispute severity scores for operations teams.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Accurately translates informal complaints into one of five standard Beckn dispute codes. Captures ISO language code metadata according to Bhashini API conventions. Rejects transcripts that fail minimum intelligible length thresholds.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Terminal or web workbench presenting original audio transcripts, translated dispute claims, and mapped Beckn schema fields.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Processes synthetic voice logs only; strictly avoids retaining personally identifiable biometric voice samples.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Receive regional language transcript logs capturing buyer delivery complaints.

  • Normalize colloquial Hindi or regional phrasing into standardized grievance attributes.

  • Map complaint entities into Beckn core post-fulfillment issue schemas.

  • Publish an escalation package with dispute severity scores for operations teams.

Resources and assets

Reference links and supporting material

Dataset notes

Assemble mock regional audio transcripts using standard Bhashini ISO-639-1 language codes paired with synthetic dispute scenarios. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

DSPy

Prompt and LM program optimization framework.

Evaluated output

No output checks are configured.

Evaluation checks
  • Receive regional language transcript logs capturing buyer delivery complaints. Normalize colloquial Hindi o...
  • Accurately translates informal complaints into one of five standard Beckn dispute codes. Captures ISO langu...
  • Terminal or web workbench presenting original audio transcripts, translated dispute claims, and mapped Beck...
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 3 configured tools

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • DSPy · Optional
Training Infra
  • DSPy · Optional
Orchestration
  • DSPy · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Vernacular Voice Grievance Transcript and Escalation Router