Middle East & North Africa · Arabic / Latin
Kurdish Call Center Speech Dataset
Kurdish call center speech sourced to your specification — no inventory, no fixed listing. This page covers what is specifically hard about this pairing, and which fields your specification needs to pin down.
Why call center speech in Kurdish is its own problem
There is no single Kurdish call center operation. A center in the Kurdistan Region of Iraq runs its scripts in Sorani and writes them in Arabic script; a center serving Turkey's southeast runs in Kurmanji and writes in Latin script, and the two teams cannot read each other's material. Underneath sits vocabulary: the same process term arrives as a Turkish loanword in one place and an Arabic loanword in the other, so one script cannot serve both. Settling the branch and the country the operation serves is the first question, and it changes the collection plan completely.
The field to pin down first: The branch (Kurmanji or Sorani) and the transcript script are fixed in the order, and every agent and caller carries a country-of-origin tag, because the loanword layer tracks the state language on each side.
At a glance
| Language | Kurdish |
|---|---|
| Primary region | Middle East & North Africa |
| Writing system | Arabic / Latin |
| Category | Call Center Speech |
| Specification field to settle first | The branch (Kurmanji or Sorani) and the transcript script are fixed in the order, and every agent and caller carries a country-of-origin tag, because the loanword layer tracks the state language on each side. |
| Delivery | Sourced to order, pilot batch before the full run |
What call center speech data is
Recorded customer-service calls, real or simulated, capturing both the agent and the caller side, used for call center QC, intent recognition, and dialogue systems.
What buyers get wrong about it
Compliance is what buyers fear most — call recordings involve personal data and recording consent, and the source has to be able to produce a consent provenance. This is also why we only do simulated collection and never work from intercepted real calls.
The specification field that decides the quote
Two-channel separated (agent and caller on separate tracks) or single-channel mixed — this directly determines how the data is annotated and how models are trained on it, and it has to be decided when the order is placed.
The language side: what Kurdish demands
The two main branches of Kurdish (Sorani and Kurmanji) have low mutual intelligibility, close to two separate languages, and they use different scripts. Public resources are so thin that even TTS datasets are rare — a textbook scarce language.
What we can put in this delivery
-
Read and conversational speech
Scripted recording for TTS, and unscripted conversation for recognition. Specified separately because they need different speaker pools.
-
Transcription to your convention
Orthographic or phonetic, with the guideline written before production and shared with you for review.
-
Speaker metadata
Age band, gender, region and dialect background per file, so you can slice the dataset rather than take it whole.
-
Consent documentation
Signed speaker consent covering the intended use, plus collection methodology and the annotation guideline.
-
Pilot batch
A small batch first, which you can reject. Misalignments surface after a few hours rather than at delivery.
-
Delivery in your format
Audio format, sampling rate, segmentation length and metadata schema set to your pipeline's requirements.
What arrives in a delivery
| Component | What it is |
|---|---|
| Audio files | Format, sampling rate and segmentation length set to your pipeline. Named to a convention you specify. |
| Transcription | Orthographic or phonetic, produced under a guideline you review before production starts. |
| Speaker metadata | Age band, gender, region and dialect background per file, plus a speaker identifier so the dataset can be sliced. |
| Recording conditions | Environment, device and, where relevant, measured signal-to-noise ratio per file. |
| Annotation guideline | The document the annotators worked from, so you can reproduce the conventions on your own data. |
| Consent records | Signed speaker consent covering your intended use, with the transfer mechanism addressed where required. |
| Collection methodology | How speakers were recruited, screened and scheduled — the part that tells you how biased the pool is. |
| Quality report | Pilot outcome, re-work log, and the annotator agreement figures where the task supports measuring them. |
Questions we get about Kurdish Call Center Speech
How many distinct speakers can you provide for Kurdish Call Center Speech?
It depends on the specification and the timeline, and we will give a real number rather than a target. For this pairing, speaker recruitment is usually the step that sets the schedule. The branch (Kurmanji or Sorani) and the transcript script are fixed in the order, and every agent and caller carries a country-of-origin tag, because the loanword layer tracks the state language on each side.
Can you annotate to our own guideline instead of the default?
Yes, and for this pairing we would recommend it. There is no single Kurdish call center operation. That is exactly the kind of decision a default guideline leaves open, and it is where annotators diverge. Send us your guideline, or we will draft one and you can review it before production starts.
Do you offer a sample before we commit to a full run?
Yes. Select a free sample in the request form and describe what you need. A pilot batch is the cheapest way to establish whether the quality bar is reachable for Kurdish Call Center Speech before committing to the full volume.
Is the data licensed or owned outright?
Licensing terms are set per project, so tell us how the model will be used and whether it will be distributed. Consent documentation travels with the data either way, and we do not handle medical or clinical data or recorded telephone calls.
Other datasets in Kurdish
-
Kurdish Noisy Speech
Speech collected under background noise — street, in-car, restaurant, office and other real environments — used for noise-robust models and speech enhancement.
-
Kurdish Code-Switching Speech
Speech that mixes two or more languages inside a single utterance — Hinglish, Spanglish, Taglish — used for recognition in real spoken settings.
-
Kurdish Children Speech
Speech data from child speakers, grouped by age band, used for children's speech recognition and children's education products.
-
Kurdish Audiobook
Continuous long-form narration in audiobook style, steady in intonation and generous in duration, the main source material for high-quality TTS.
-
Kurdish Short Video Speech
Speech in the talking-head style of short video — fast, emotionally strong, colloquial — used for short video subtitles and content understanding.
-
Kurdish Live Stream Speech
Long-session spoken content from live streams — host monologue and responses to audience interaction — fast-paced and heavily improvised.
Call Center Speech in other languages
-
Khmer Call Center Speech
Southeast Asia
-
Arabic (Egyptian) Call Center Speech
Middle East & North Africa
-
Arabic (Gulf) Call Center Speech
Middle East & North Africa
-
Kannada Call Center Speech
South Asia
-
Punjabi Call Center Speech
South Asia
-
Burmese Call Center Speech
Southeast Asia
Request Kurdish Call Center Speech
Tell us the language, the hours, and what the data needs to look like. You will get a real number and a real timeline — not a range. If we cannot source it well, we will tell you that instead.
- Pilot batch before the full run, so problems surface early.
- Consent documentation delivered with the data.
- No medical or clinical data. No recorded telephone calls.