Skip to main content
AI Data

How to Collect Conversational Data Across Cultures

July 2026 · 10 min read · Updated September 2026

Short answer. Across major dialogue datasets — DailyDialog, MultiWOZ, PERSONA-CHAT, XPersona, GlobalWOZ, XDailyDialog — cultural relevance is largely absent, and SEADialogues describes itself as the first to represent cultural aspects explicitly within each conversation. Translation cannot fix this: it preserves the language and imports the scenario. Hershcovich and colleagues argue that collecting inside large local communities produces culturally richer data instead.

Key takeaways

  • Across major dialogue datasets including DailyDialog, MultiWOZ, PERSONA-CHAT, XPersona, GlobalWOZ and XDailyDialog, cultural relevance is absent, and several of the multilingual ones are translated rather than natively created.
  • Translation preserves the language and imports the scenario, so a translated dialogue is a foreign situation conducted in the target language.
  • SEADialogues covers eight Southeast Asian languages across six countries with 32,000 dialogues, built from 300 scenarios and 210 personas plus culturally relevant names.
  • CultureTalk-ID covers general Indonesian culture plus ten provinces, spanning Indonesian and ten local languages across thirteen cultural topics, treating national-level culture as insufficient granularity.
  • NormDial's validation standard required native speakers to judge each norm factually correct according to their own lived experiences, culture-specific and sufficiently detailed, yielding 133 Chinese and 134 American norms.
  • Synthetic dialogue is legitimate when grounded in native-verified cultural norms with human verification at every stage, and produces stereotypes when generated without that frame.

Why is cultural relevance missing from most dialogue datasets?

Cultural relevance is missing because the field built multilingual coverage without building cultural coverage, and treated the two as the same problem.

A comparison table in the SEADialogues paper makes the state of the field clear. It lists the major dialogue datasets — DailyDialog, MultiWOZ, PERSONA-CHAT, XPersona, GlobalWOZ, Multi2WOZ, Multi3WOZ, XDailyDialog — and in the column for cultural relevance, every one is marked with a cross. Some are large: XPersona covers six languages with 104,600 dialogues, and GlobalWOZ covers 21 languages. Several of the multilingual entries carry a second cross too, in the column marking whether the dataset avoided translation — GlobalWOZ, XPersona and XDailyDialog are all translated rather than natively created.

A dialogue dataset is a structured collection of conversational exchanges used to train or evaluate conversational AI, typically organised around scenarios, personas and turns. The honest starting position for anyone scoping this work: multilingual dialogue data mostly exists, culturally grounded dialogue data mostly does not, and the two have been treated as interchangeable.

Why does translation fail to produce cross-cultural dialogue?

Translation fails because the scenario itself carries culture, and translating the words leaves the situation intact.

Take a task-oriented dialogue about booking a restaurant table. Translate it into Javanese and the result is a Javanese-language conversation about a Western restaurant booking flow, with Western assumptions about reservation norms, party sizes, payment and how one addresses staff. The language is right; the situation is imported. Hershcovich and colleagues argue that collecting multilingual data within large local communities results in culturally richer data and avoids imposing English-driven use cases on every market. The COD project's approach involves cultural adaptations and replacements of foreign concepts with those common in the annotators' own culture and environment, and its authors note that scenario selection based on cultural relevance and plausibility should come before dialogue generation, not after. Scenario selection, not translation quality, is where cross-cultural dialogue data succeeds or fails — the same lesson explored in why culturally relevant data matters for AI.

What does a culturally grounded data collection pipeline look like?

A culturally grounded pipeline starts from validated scenarios and personas, then generates or collects dialogue against them, rather than starting from conversations and hoping the culture shows through.

Cultural grounding, in this context, means that the scenarios, personas and norms underlying a dialogue were sourced from and verified by people who live the culture being represented. SEADialogues covers eight Southeast Asian languages — Indonesian, Javanese, Malay, Minangkabau, Tagalog, Tamil, Thai and Vietnamese — across six countries, producing 32,000 dialogues. Its pipeline begins with supporting resources rather than conversations: scenario templates, persona templates, and culturally relevant Southeast Asian names. For each dialogue, two domain-relevant scenarios and corresponding personas are selected to ensure consistency across both intra-scenario and inter-scenario persona relationships, followed by manual lexicalisation. The dataset ships 300 scenarios and 210 personas — those two numbers are the actual cultural content, and everything downstream is generation and annotation against them.

CultureTalk-ID goes deeper geographically within a single country. Built through a multi-stage human pipeline involving native speakers, it covers general Indonesian culture plus the cultures of ten provinces — Aceh, West Sumatra, West Java, Central Java, East Java, Bali, Nusa Tenggara Timur, South Kalimantan, South Sulawesi and West Papua — spanning Indonesian and ten local languages across thirteen cultural topics. The design point worth extracting: the team treated "Indonesian culture" as insufficient granularity and built provincially, the same logic that applies to scoping language coverage at locale level.

How should social norms be labelled in dialogue data?

Social norms should be labelled explicitly, on a per-turn basis, and validated against native speakers' lived experience rather than a reference source.

Social norm annotation is the practice of tagging each conversational turn for whether it adheres to or violates a culturally specific behavioural expectation. NormDial produced 4,231 dyadic dialogues totalling 29,550 conversational turns across Chinese and American cultures, with social norm adherences and violations labelled turn by turn. Native speakers in each culture manually evaluated whether each generated norm was factually correct according to their own lived experiences, in line with the defined norm category, specific to the culture, and detailed in its description — removing any norm that failed a criterion, and arriving at 133 Chinese and 134 American norms as the grounded foundation. RENOVI extends this to repair, containing 9,258 multi-turn dialogue instances and described as the first dataset exploring remediation of norm violations based on Chinese cultural norms, annotated by 20 university lecturers and students familiar with Chinese culture. NormGenesis shows the annotation depth this work can reach: dialogues run 5 to 15 turns, and each utterance is annotated with norm adherence, speaker reaction including intent and emotional state, and a justification for the assigned label. That justification is unusual and valuable — a label without a rationale cannot be audited, and in cultural annotation the rationale is often the only way to tell a genuine cultural judgement from a personal one. The finding that motivates all of this work: existing models often fail to reason correctly about norm adherence and violation in conversational contexts.

What localisation method works best for task-oriented dialogue?

The most robust method separates slot localisation from phrase localisation, using two different groups of people in sequence rather than one translator doing both at once.

In stage one, native speakers translate and localise the slot values — restaurant names, dish names, currencies, addresses, times, honorifics. In stage two, a different group of human subjects translates or localises the entire phrase, using the slot output from stage one. Separating the two steps prevents the common failure where a translator preserves English slot values because they read as proper nouns, leaving a Thai-language dialogue about ordering a Caesar salad from a place called The Golden Lion. The alternative — substituting English slot values with target-language counterparts under a controlled automatic procedure — is faster but produces a thinner result than the slower, more human-driven approach that keeps close contact with the local community speaking the target language.

How is naturalistic spontaneous speech collected across cultures?

Naturalistic spontaneous speech is best collected with open prompts rather than scripts, paired with quality screening before the session and automated checks after it.

The 2026 Hume-DaiKon corpus contains 945 sessions totalling 743.4 hours across German, English, Spanish, Dutch and Polish, collected through a dual-channel conversational platform that connects pairs of participants from similar geographic regions. Participants complete an audio quality screening before participation, ensuring a minimum standard of microphone clarity rather than discovering the problem in post-processing. They respond to a short prompt in their native language — the example given is "How was your weekend?" — which produces spontaneous speech rather than a scripted read. The response is then automatically checked using a language model to verify it is both relevant to the prompt and linguistically fluent, an automated-triage-before-human-review pattern that recurs throughout how speech data is collected for low-resource languages. Splits are stratified by language, with the test set kept blind — per-language stratification is the recurring discipline across multilingual data work.

Is synthetic dialogue data acceptable for cultural training?

Synthetic dialogue is acceptable when it is generated within a human-verified cultural frame, and unreliable when it is not.

Synthetic dialogue data is conversational text or speech generated by a language model rather than recorded from real participants. The NormDial authors argue plainly for it: gathering realistic data at scale in this domain is challenging and potentially cost-prohibitive, particularly for identifying norm adherences and violations across multiple cultural contexts. They report that their synthetic bilingual conversations were comparable to or exceeded the quality of existing naturally occurring datasets under interactive human evaluation and automatic metrics. The qualifier that matters is where the humans sit: NormDial's pipeline has human verification at every stage, and the norms themselves were validated by native speakers against lived experience before any dialogue was generated — synthesis operating within a human-authored cultural frame. Synthetic dialogue generated by prompting a model to "write a conversation between two Indonesian friends," with no such frame underneath it, is the model's stereotype of Indonesian conversation, and it reads as such to any Indonesian.

How does Lifewood approach cross-cultural conversational data collection?

Lifewood collects conversational and dialogue data across 50+ languages through delivery centres across 30+ countries, including several of the Southeast Asian markets these datasets cover, and treats the scenario library — not the dialogue count — as the deliverable.

If the scenarios are culturally accurate, dialogue volume scales cleanly from them, as SEADialogues demonstrates by generating 32,000 dialogues from 300 scenarios and 210 personas. If the scenarios were imported and translated, no amount of dialogue volume fixes it — which is why the question to ask a supplier is how the scenarios were sourced, not how many dialogues they will deliver. Cultural granularity also needs deciding as explicitly as dialect granularity: CultureTalk-ID built provincially within Indonesia because national-level culture was insufficient resolution, a decision that belongs in a scope document rather than being resolved by default, much like the community-partnership questions covered in partnering with universities and local communities for language data. A dataset labelled "Indonesian" that was collected entirely in Jakarta is a Jakarta dataset, and nothing in the delivery statistics will say so — the same reasoning behind what a multilingual data collection service should include and Lifewood's multilingual data collection services more broadly, as well as recruitment practices such as recruiting native contributors for language data.

What should a scoping checklist for cross-cultural dialogue data include?

A scoping checklist should specify how scenarios were sourced and validated, at what cultural granularity, by whom, and with what handling of synthetic content.

  • Specify the scenarios, not just the languages — where they come from, and who validated that they are plausible in that culture.
  • Decide cultural granularity explicitly, at national, provincial or community level, with a stated rationale.
  • Recruit for lived experience, since the verification standard that works is whether a norm is correct according to the annotator's own life, not a reference.
  • Localise slot values separately from phrases, in two stages with different people.
  • Annotate norms explicitly where the application involves social appropriateness, including adherence, reaction and a justification for the label.
  • Use prompts rather than scripts for spontaneous collection, with audio screening before the session and automated relevance checking after it.
  • Stratify everything by language, including evaluation splits, and be precise about synthetic content — human-verified norms grounding model-generated dialogue is a method; unverified generation is a stereotype, a distinction that applies equally to collecting speech and text that mixes languages and to collecting accented or non-native speech.

Frequently asked questions

You will get the right language and the wrong situation. The scenarios carry cultural assumptions about roles, norms and procedures, and translation leaves those intact. Several major multilingual dialogue datasets are translated and none of them carry cultural grounding.

The scenarios and personas. SEADialogues generated 32,000 dialogues from 300 scenarios and 210 personas built with culturally relevant names and situations. The scenario library, not the dialogue count, is where the cultural content lives.

Usually more granular than national. CultureTalk-ID built across ten Indonesian provinces because "Indonesian culture" was insufficient resolution, mirroring the same decision required when scoping dialects or accents within one language.

Against native speakers' lived experience. NormDial required each norm to be factually correct per the annotator's own life, in category, culture-specific and detailed, discarding any norm that failed one of those criteria before use.

Yes, when it is grounded in human-verified cultural norms with verification at every stage. NormDial reported synthetic conversations comparable to or exceeding naturally occurring datasets under human evaluation. Unverified generation produces the model's stereotype of a culture instead.

With prompts rather than scripts. Hume-DaiKon used native-language prompts such as "How was your weekend?", with audio quality screening before participation and automated checking of relevance and fluency afterwards.

Sources and further reading

  1. "SEADialogues: A Multilingual Culturally Grounded Multi-turn Dialogue Dataset on Southeast Asian Languages", arXiv, on the comparison against existing dialogue datasets, the eight-language six-country scope, and the scenario and persona pipeline
  2. "CultureTalk-ID: A Multi-Task Dialogue Benchmark for Cultural Commonsense in Indonesian Local Languages", arXiv, on the multi-stage native speaker pipeline and provincial cultural coverage across ten provinces and thirteen topics
  3. "NormDial: A Comparable Bilingual Synthetic Dialog Dataset for Modeling Social Norm Adherence and Violation", arXiv, on the 4,231 dialogues, 29,550 turns, the native speaker validation criteria, and the finding on model reasoning about norms
  4. NormDial, EMNLP 2023 proceedings, on the four-stage pipeline with human verification at every stage and the resulting 133 Chinese and 134 American norms
  5. "RENOVI: A Benchmark Towards Remediating Norm Violations in Socio-Cultural Conversations", arXiv, on the 9,258 dialogue instances and the annotator training procedure with 20 university lecturers and students
  6. "NormGenesis: Multicultural Dialogue Generation via Exemplar-Guided Social Norm Modeling and Violation Recovery", arXiv, on turn-level annotation of norm adherence, speaker reaction and justification
  7. "Crossing the Conversational Chasm: A Primer on NLP for Multilingual Task-Oriented Dialogue Systems", arXiv, on two-stage slot and phrase localisation and the Hershcovich et al. argument for community-based collection
  8. "The 2026 ACII Dyadic Conversations (DaiKon) Workshop and Challenge", arXiv, on the Hume-DaiKon corpus scale, languages, audio screening, native-language prompting and automated fluency checking
  9. "Cross-Lingual Dialogue Dataset Creation via Outline-Based Generation", TACL, on cultural adaptation and replacement of foreign concepts and scenario plausibility selection
  10. Lifewood, multilingual data collection services

Have an AI or visibility project in mind?

From AI evaluation and human-in-the-loop review to GEO and AEO strategy, our team can help you deploy with confidence and get found in the AI search era.

Talk to our team