Talkback vs Intercom in Live Sound: Choose the Right Communication Path

TL;DR — Console talkback routes an engineer's microphone into selected audio mixes, commonly to performers during setup. Production intercom connects crew members through dedicated stations, beltpacks, headsets, and communication groups. Talkback is efficient for mix-related instructions; intercom supports two-way operational coordination and show cues. Do not treat either as universally private or fail-safe. Define users, destinations, mute behavior, cue priority, ownership, tests, and fallback before doors.

Table of contents

1. Define talkback and intercom
2. Choose the correct communication path
3. Route and test communication
4. Document ownership and fallback
5. FAQ

Define talkback and intercom

Console talkback uses a microphone connected to or selected by a mixing console and sends it to chosen buses or outputs. FOH or monitor engineers may speak to wedge and IEM mixes during line check, soundcheck, rehearsal, or troubleshooting. Depending on the console, talkback may be momentary or latched and may route to one mix, several mixes, a stage wedge, recording, or other destinations.

Production intercom is a dedicated crew communication system. Wired or wireless stations and beltpacks connect users to one or more channels, groups, or point-to-point paths. Stage management, audio, lighting, video, automation, camera, and show calling may use it before and during a performance.

An intercom interface can connect to a console, and an audio cue feed can enter an intercom system, but that does not make their purposes identical. Treat every bridge as a named, tested handoff with an owner.

Choose the correct communication path

Soundcheck and performer instructions

Talkback is useful when an engineer needs to reach performers through their existing monitor mixes: ask for a drum, confirm a vocal channel, or describe a monitor adjustment. Route only to the required destinations. A general instruction may go to all mixes; a sensitive or distracting message may need one selected mix or a stage-only speaker.

Performer replies need a return path. That may be an open vocal microphone, a dedicated stage talkback microphone, a switched microphone, or intercom for crew. State which path is expected so nobody assumes a muted vocal can be heard.

Show calling and crew coordination

Use production intercom for standbys, go cues, scene changes, safety coordination, camera direction, and cross-department timing. These workflows require known participants, communication groups, cue language, microphone discipline, and an operator who owns the system. The production intercom tech rider covers inventory and staffing in detail.

Do not use an artist monitor mix as the main crew intercom. Show traffic can distract performers, and mix changes or console failure may remove the path precisely when crew coordination is needed.

FOH-to-stage troubleshooting

During line check, FOH talkback may reach a monitor engineer or stage technician through a designated wedge, cue bus, matrix, or intercom interface. Confirm whether this route follows console mutes, scene recalls, DCA control, or output processing. The destination must remain understandable when the PA is muted.

For sustained two-way fault finding between FOH and stage, intercom is often clearer because both users have headsets and do not occupy performer mixes. Talkback can remain the direct path to musicians.

Broadcast and recording privacy

Never assume talkback is absent from a stream or recording. Trace direct outs, bus pickoff points, matrices, USB feeds, network subscriptions, and recorder patches. A producer intercom or studio-style cue path may intentionally enter headphones but should not enter the program feed.

Intercom is also not automatically private. Wireless coverage, partyline membership, bridged systems, recording interfaces, and open speakers can expose conversation. Set expectations and avoid sensitive speech on operational channels.

Route and test communication

1. List every user. Include performers, FOH, monitors, stage management, patch, lighting, video, camera, and production leads.
2. Name each communication job. Separate performer instruction, mix requests, show cues, safety, and general crew coordination.
3. Choose the path. Assign talkback, intercom, visual cue, radio, phone, or another approved method to each job.
4. Map both directions. Identify who speaks, who listens, how replies return, and whether a path is one-way.
5. Trace control behavior. Test mute groups, scenes, snapshots, solo modes, bus masters, matrices, and output mutes.
6. Protect program destinations. Confirm talkback is absent from the audience PA, stream, recorder, press feed, and lobby unless explicitly required.
7. Test under show conditions. Wear the real headsets and IEMs, run the PA, close doors, and test wireless coverage and noise.
8. Exercise fallback. Disconnect or mute the primary path and prove the agreed alternative.

Define momentary and latched behavior

A momentary talk button transmits while held; a latch stays open until released. Momentary operation reduces the chance of an accidentally open microphone, while latch can help during extended rehearsal communication. If latching is allowed, provide a clear status indication and reset check before the show.

Intercom stations may also use momentary or latched talk keys by channel. Confirm call lights, sidetone, microphone gain, listen level, and channel selection for every user. A headset that can hear does not prove its microphone reaches the correct group.

Control level and intelligibility

Communication must be loud enough to understand without startling performers or masking show audio. Check the talkback microphone gain, compression if used, bus level, destination level, and IEM limiter behavior. Avoid heavy effects and excessive low-frequency energy. Keep routing simple enough that an engineer can identify an error quickly.

Document ownership and fallback

Put the communication plan beside the audio and production workflows it supports. Exact console routing can live in a show file, but the rider must still explain users, destinations, ownership, and fallback so another crew can verify it.

For intercom, record station count, wired and wireless roles, channel assignments, interfaces, power, coverage, spare batteries, cue language, and who makes configuration changes. Do not write only “comms required.”

Common mistakes

• sending talkback to every mix because it is easy;
• assuming performers can reply after their microphones are muted;
• allowing talkback into broadcast, recording, lobby, or audience feeds;
• using talkback for safety-critical show calling without a tested fallback;
• placing all departments on one noisy intercom channel;
• failing to test scene recalls, mute groups, and output masters;
• leaving a latched microphone open;
• documenting hardware without users, channels, ownership, or cue procedure.

Communication handoff checklist

• Every user and communication job is listed.
• One-way and return paths are both mapped.
• Talkback destinations and program exclusions are explicit.
• Intercom groups and cue language match the production workflow.
• Momentary, latch, mute, and recall behavior is tested.
• Levels and wireless coverage work under show conditions.
• One owner controls each routing boundary.
• A practical fallback has been exercised.

FAQ

What is the difference between talkback and intercom?

Talkback normally sends a console microphone into selected audio mixes for performer or audio-team communication. Intercom is a dedicated two-way crew communication system with stations, headsets, and assigned channels or groups.

What is talkback on a mixing console?

It is a microphone path the engineer can route to selected buses or outputs, usually with a momentary or latched switch. It is commonly used for soundcheck, rehearsal, monitor instructions, and troubleshooting.

Can talkback replace a production intercom?

Not for most multi-department or cue-heavy shows. Talkback can handle simple audio instructions, but intercom provides two-way crew communication, group assignment, show calling, and operational independence. Small productions should still define a fallback.

Who should hear the FOH talkback microphone?

Only the people required for the current task. Select performer mixes, monitor position, stage wedge, or another destination deliberately, and verify that the audience PA, stream, recording, press, and lobby feeds are excluded unless intended.

How do you document talkback and intercom in a tech rider?

List users, talkers, listeners, destinations, return paths, hardware or interface, channel assignments, mute and recall behavior, owner, test procedure, show state, and fallback. Link the plan to monitor, production, and cue documentation.

Keep communication routes current

Build and share the current Rider with Techrider.live, connect talkback and intercom notes to the responsible people and destinations, and invite collaborators to edit the same Rider. Save the verified show state and inspect history so the next crew knows who can speak to whom and what happens if the primary path fails.