Southeast Asia · Latin

Filipino Voice Assistant Dataset

Filipino voice assistant 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 voice assistant in Filipino is its own problem

Filipino voice-assistant users almost invariably speak Taglish; commands in pure Filipino are the uncommon case. An intent schema designed around the language alone will miss a large share of real usage.

The field to pin down first: The intent schema must cover Taglish expression, with an example set of mixed-language utterances.

At a glance

LanguageFilipino
Primary regionSoutheast Asia
Writing systemLatin
CategoryVoice Assistant
Specification field to settle firstThe intent schema must cover Taglish expression, with an example set of mixed-language utterances.
DeliverySourced to order, pilot batch before the full run

What voice assistant data is

Command and dialogue data for voice assistants, usually with intent annotation, covering the full chain from wake word to understanding to response.

What buyers get wrong about it

What buyers actually need is intent plus slot annotation, not just audio and transcription. The intent taxonomy has to align with the schema the buyer already runs.

The specification field that decides the quote

Whether the intent schema comes from the buyer or is designed by us — this is the dividing line in the quote.

The language side: what Filipino demands

Filipinos speak Taglish in daily life — switching between Tagalog and English sentence by sentence, sometimes word by word. This is how native speakers naturally talk, not a sign of substandard speech. Anyone who wants authentic data has to treat this mixing as the target, not as noise.

More on Filipino speech data →

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

ComponentWhat it is
Audio filesFormat, sampling rate and segmentation length set to your pipeline. Named to a convention you specify.
TranscriptionOrthographic or phonetic, produced under a guideline you review before production starts.
Speaker metadataAge band, gender, region and dialect background per file, plus a speaker identifier so the dataset can be sliced.
Recording conditionsEnvironment, device and, where relevant, measured signal-to-noise ratio per file.
Annotation guidelineThe document the annotators worked from, so you can reproduce the conventions on your own data.
Consent recordsSigned speaker consent covering your intended use, with the transfer mechanism addressed where required.
Collection methodologyHow speakers were recruited, screened and scheduled — the part that tells you how biased the pool is.
Quality reportPilot outcome, re-work log, and the annotator agreement figures where the task supports measuring them.

Questions we get about Filipino Voice Assistant

How many distinct speakers can you provide for Filipino Voice Assistant?

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 intent schema must cover Taglish expression, with an example set of mixed-language utterances.

Can you annotate to our own guideline instead of the default?

Yes, and for this pairing we would recommend it. Filipino voice-assistant users almost invariably speak Taglish; commands in pure Filipino are the uncommon case. 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 Filipino Voice Assistant 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 Filipino

  • Filipino Accented English

    English speech from non-native speakers or specific regional accents, grouped by accent origin, used to improve accent robustness in ASR.

  • Filipino Speech Translation

    Parallel data pairing source-language audio with target-language translation, used for speech-to-text and speech-to-speech translation models.

  • Filipino In-the-Wild Speech

    Speech collected under fully natural conditions — no studio, no topic constraints — as close to real usage as collection gets.

  • Filipino Call Center Speech

    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.

  • Filipino Conversational Speech

    Speech from natural conversation between two or more people, on open or semi-structured topics, used for conversational AI, voice assistants, and small talk models.

  • Filipino Singing Voice

    Vocal recordings with melody, in both a cappella and accompanied form, used for singing voice synthesis, music information retrieval, and lyric alignment.

All Filipino data →

Voice Assistant in other languages

All Voice Assistant data →

Request Filipino Voice Assistant

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.

We reply within two business days. Your details are used only to answer this request. See our privacy policy.

Contact

Talk to a human

Send a specification and we will come back with a real number and timeline.

Submit a sourcing request

Or email hello@linguacorpus.com