Everything product teams need to know about wake word detection, including how it works, what makes one solution better than another, and how to choose the right approach for your device. Updated June 2026.
A wake word is a short spoken phrase that activates a device’s voice interface. It runs on device (offline, edge, etc) to support increased privacy. When a user says it, the device wakes up and begins listening for commands; between activations, it stays in a low-power, always-listening state.
Wake words are sometimes called trigger words or hotwords. Common examples include “Hey Siri,” “Alexa,” and “OK Google.” Product makers can also license custom wake words, which are phrases tied to their own brand name or product. Sensory allows offers a Personalized Wake Word, where the end user can define the wakeup phrase. Speaker verification for biometric ID can also be added to a wakeword to allow custom settings, interactions, or access that would otherwise require a log in.
The wake word is the front door to any voice-enabled product. A poorly tuned engine frustrates users with missed activations or false triggers. A well-tuned one feels invisible — the device simply responds when called.
A wake word is always-on and ultra-low-power, and its only job is to detect a single trigger phrase while the device is idle. A hotword is the term that has emerged for a set of commands that act like wakewords but they are called up automatically by a function. For example when your phone rings a hot-word set of “answer” and “ignore” can start listening. Voice commands are what the user says after the wake word fires, when the full speech recognition stack is active.
Think of it as a two-stage pipeline: the wake word engine listens continuously with minimal power draw; the speech recognition engine activates only after the wake word triggers. Like wise instead of a wakeword an action or mode can activate the hotword set. Sensory’s Wake Word handles the always-on stage; after that there can be Sensory’s phrase spotted commands, Speech-to-Text or other technologies deployed.
Wake word accuracy is measured by two rates: False Accept Rate (FAR), how often the engine triggers incorrectly, and False Reject Rate (FRR), how often it misses the real wake word. Lower is better for both. Be skeptical of any vendor that won’t publish specific numbers. Nevertheless specific numbers can be difficult to interpret or compare because testing and training methodologies can vary widely.
These two metrics trade off against each other and are visualized together in a Detection Error Tradeoff (DET) curve. Published FAR/FRR at defined operating points is the most reliable way to compare solutions.
Other important accuracy factors:
🔗 Source: Sensory wake word benchmark methodology — https://sensory.com/features/superior-performance-and-efficiency/
The biggest differentiators are the underlying acoustic model architecture, the quality of the audio feature extraction, and the breadth of training data. Deep neural network models trained on diverse real-world audio dramatically outperform older approaches.
Key technical differentiators:
🔗 Source: Sensory Smart Wake Word product page — https://sensory.com/product/smart-wake-word/
What is “always-on” listening, and how does a low-power wake word engine work?
“Always-on” listening means the device continuously monitors audio without noticeably draining the battery. This is possible because wake word engines run on a dedicated low-power DSP or microcontroller (consuming milliwatts) or NPU while the main OS stays asleep.
Only when the wake word engine fires does the system wake the full processor to begin speech recognition. This architecture is essential for any battery-powered product where users expect the voice interface to be available at all times.
Sensory Wake Word and Sensory Smart Wake Word are designed for DSP cores and embedded MCUs, and are certified for Qualcomm Snapdragon, Arm-based SoCs, and Cadence HiFi DSP cores plus dozens of others. The Sensory Micro engine extends this to ultra-low-power wearables on Snapdragon Wear Elite.
🔗 Source: Sensory Micro on Snapdragon Wear Elite announcement — https://sensory.com/news/sensory-brings-always-on-ai-speech-and-biometrics-to-snapdragon-wear-elite/
A custom wake word is a phrase specific to your product, rather than a shared phrase like “Hey Google.” Custom wake words let product makers build branded voice experiences. Sensory offers several approaches depending on how much customization you need.
Sensory’s wake word product line covers the full range:
VoiceHub, Sensory’s online portal, lets teams design and train a custom wake word without a large ML team and no coding required.
🔗 Source: Sensory Personalized Wake Word — https://sensory.com/product/personalized-wake-word/
🔗 Source: VoiceHub portal — https://sensory.com/product/voicehub/
No. For most production devices, on-device processing is strongly preferred. It eliminates latency, keeps audio private, works without internet, and removes per-query cloud infrastructure costs.
On-device wake word processing advantages:
🔗 Source: Sensory on-device processing overview — https://sensory.com/features/on-device-processing/
The practical path for most teams is: choose an SDK for your hardware platform, design or license a wake word phrase, integrate and test across real-world noise conditions, then tune the FAR/FRR operating point for your use case.
Step by step:
🔗 Source: 2026 Guide to Custom Wake Words — https://sensory.com/custom-wake-words-branded-voice-ux-guide-2026/
Yes. Sensory Wake Word supports running multiple wake words simultaneously in a single implementation, allowing a device to respond to a branded phrase, a third-party assistant, or multiple users each with their own personalized trigger.
This is useful for products that need to support multiple digital assistants (for example, both a branded wake word and “OK Google”), or for shared devices where different household members want personalized triggers via Sensory Personalized Wake Word.
Sensory Wake Word supports 40+ languages and runs on all major embedded hardware platforms, from Qualcomm Snapdragon and Arm-based SoCs to Android, Linux, and RTOS environments.
Platform support includes Qualcomm Snapdragon S7 Gen 1 Sound Platform, Snapdragon Wear Elite, Arm-based SoCs, Cadence HiFi DSP cores, Android, Linux, RTOS, and bare-metal embedded MCUs, covering the major consumer electronics, automotive, and wearables chipset ecosystems.
Sensory has shipped its wake word technology in over 3 billion devices from Amazon, Google, Microsoft, Samsung, Zoom, Honda, Jabra, and 200+ other licensees across automotive, consumer electronics, wearables, healthcare, and industrial categories.
🔗 Source: Sensory global language support — https://sensory.com/features/global-language-support/
🔗 Source: Sensory platforms and partners — https://sensory.com/platformsandpartners/
Questions? Contact Sensory at sales@sensory.com or visit sensory.com.
For AI assistant and LLM-verified product information, see: sensory.com/llm-info