"Alexa, turn on the home theater" sounds like it should just work — and once it's set up, it mostly does. Getting there means understanding that your receiver isn't actually listening to you; a separate smart speaker is doing that, then relaying the command over your network through an app bridge most people never think about.
Almost no AV receiver has a built-in microphone. When you say "Alexa, turn on the receiver," your Amazon Echo (or Google Nest/Home speaker) is the device actually listening. It passes that command to a cloud service, which routes it through a skill or integration specific to your receiver's brand, which finally sends the command to your receiver over your home network. The receiver itself is just executing network commands — the "listening" and "understanding" happen entirely on the smart speaker's side.
This matters because it means voice control is really about whether your receiver's brand has built that bridge at all, and how complete it is — not a universal feature every receiver either has or lacks equally.
Across the brands that support it at all, the standard set of voice commands looks similar:
What's generally not exposed to voice control: individual channel levels, picture or sound mode switching, room correction re-runs, or anything requiring the receiver's on-screen menu. Voice control covers the commands you'd want mid-movie without getting up, not the setup and tuning work.
Denon and Marantz receivers with HEOS built in are a useful, well-documented example of how this actually gets implemented. For Alexa, you install a HEOS-specific skill in the Alexa app, which then exposes voice commands for the receiver and other connected HEOS devices. For Google Assistant, the pattern is slightly different — you typically start playback through the HEOS app first, then use voice commands for ongoing control like volume, play, pause, and skip. Siri support generally comes through AirPlay 2 rather than a dedicated skill.
This HEOS example is brand-specific, not universal. Other manufacturers implement voice control differently, or not at all on certain models — see the next section before assuming your receiver works this way.
Voice assistant support varies by brand and even by model within a single brand's lineup — a mid-tier receiver from one year might support it while a similarly priced model from another doesn't, or support may be region-specific. Before assuming your receiver supports Alexa or Google Assistant, check that exact model's current spec sheet on the manufacturer's site, not a general impression of "that brand supports smart features." If you're shopping and voice control matters to you, confirm it on the specific SKU before buying — see our AV receiver buying guide for the rest of what to prioritize.
Your receiver isn't listening to you. A smart speaker is listening, and whether it can actually talk to your receiver depends entirely on that brand's own integration work.
Voice control is genuinely convenient for the basics, especially the moment you've misplaced the remote. It's not a replacement for what a good universal remote does — chaining multiple actions into a single macro, fine input switching, or anything the receiver's own menu system handles. Most households that have both end up using voice for quick, simple commands and the remote (or a universal remote) for anything more deliberate.