Church Comms: Why Your Team Needs an Intercom and Where PunQtum Fits

A Sunday service is a dozen people doing a dozen jobs at the same moment. The director needs a camera operator to reframe, the graphics operator needs to know the pastor skipped a point, and audio needs a heads-up before a video rolls. Without a real comms system, all of that happens through waving arms, text messages, and someone jogging to the back of the room.

Good gear that supports your team’s communication is so important. Here’s why a church team needs real comms, how to plan it so it actually helps, and where the PunQtum system fits.

Why “We’ll Just Text” Stops Working

Texting and hand signals break down exactly when you need them most. Nobody can read a phone while running a camera. Nobody at front of house can see a hand signal from the control room.

A comms system gives every operator an open line in their ears and a button to talk. The team hears the call the moment it’s made, and nobody leaves their position.

When I ran production at a church in Canton, Ohio, our team used a comms system to stay coordinated during Sunday services. It’s one of those systems nobody in the congregation notices, which is exactly the point.

What Made Me Take PunQtum Seriously

Church Production Magazine sent me a PunQtum SpeakerStation and BeltPacks to test. I’d never used PunQtum gear before. It took me about an hour to set up, deploy, and learn the whole system, and I came away genuinely impressed.

Three things set it apart from the other comms systems I’d used:

• It’s IP-based. Everything travels over Ethernet cable, and the BeltPacks are powered over Ethernet (PoE+).
• It offers up to 32 channels for users to talk on.
• It includes a free app. Phones can join the conversation beyond the physical hardware.

The flexibility is much greater than the systems I’d used before. Because it runs on Ethernet, a new position is a matter of getting a PoE+ connection to where that person stands.

Plan Your Channels Before You Buy Anything

A common mistake with comms isn’t the hardware. It’s putting everyone on one line.

A comms channel is a room. Put only the people who need the conversation in that room, and give everyone one shared room for the whole team.

For most churches, a simple plan works:

• Channel 1: General line. Everyone is on it. Service cues, schedule changes, “we’re starting in two minutes.”
• Channel 2: Video team line. The video director calls cameras here.

Why split them? So the rest of the team doesn’t have to listen to the video director calling camera shots all service long. Audio, lighting and slides don’t need “camera 2, tighten up” in their ears, and that noise makes them miss the calls that do matter.

As your team grows, add a channel per team. Each team gets the general line plus its own line.

Who Needs a Comms Position?

Walk your building and list every seat that makes a decision during the service. In a typical church setup that includes:

• The producer or director, usually in the livestream control room
• Front of house, including audio, lighting and slides
• Camera operators, if you run manned cameras
• Someone who roams, like a floater solving problems or a stage manager

That list drives your hardware. The PunQtum SpeakerStation is the core of the system and is best used at the producer’s position. BeltPacks go to everyone else.

Starting Small: Eight BeltPacks, No Network Gear

You don’t need a network overhaul to start. The SpeakerStation has four network ports, and two of them provide PoE+ to connected devices. That’s great for starting out if you don’t have PoE-enabled network ports yet.

You can daisy-chain four BeltPacks from each of those two PoE+ ports. A simple layout looks like this:

1. Set up the SpeakerStation in your livestream control room.
2. Chain four BeltPacks from PoE+ port 1 for the team in that room.
3. Run one Ethernet cable from PoE+ port 2 to front of house and chain four more BeltPacks there.

That’s eight positions with zero extra networking gear. It’s also the limit of this approach. The system can provide dozens of channels for dozens of BeltPacks, and camera positions may need more BeltPacks. You might find a creative way to route that FOH cable past a camera position, but a couple of PoE+ switches open the system up. The full technical walkthrough covers that networking step.

Roles Make It Volunteer-Proof

This is the part that makes PunQtum friendly for a rotating volunteer team. The system is built on presets called roles. A role holds a BeltPack’s whole setup, so you configure it once and assign it.

Settings live in Q-Tool, PunQtum’s configuration software for Mac or PC. For a simple setup, I’d give everyone one role using the default channels 1 and 2, so every BeltPack can talk on both.

Example: A Flipped Role

Say one operator wants channel 1 on the right and channel 2 on the left. In Q-Tool:

1. On the Device Config tab, create a second version of the role with the channels flipped.
2. Go to Key Sets to change which channel each talk button uses.
3. On the Online Systems tab, choose which role each BeltPack gets.

You can also do it right on the BeltPack. Push the settings button, choose Role, and switch from “Channels 1 & 2” to the new flipped role.

That’s a simple example, but it shows the idea. You decide what each position needs once, and nobody has to remember button settings on a Sunday morning.

The Producer Position: Talk to Everyone at Once

The SpeakerStation has push-to-talk buttons for four separate channels, which is why it belongs with the producer. In Q-Tool on the Device Config tab, I updated the SpeakerStation’s role to add channels 1 and 2, so I could talk on either channel like everyone else.

Then I gave the third talk button a bigger job. I changed it to talk to many groups, then Talk to All. One press now reaches both channels at the same time.

That’s the button a director needs when the whole team has to hear something now. BeltPacks can get the same Talk to All function if you set it up on their auxiliary page.

The Free App: Where It Helps

PunQtum’s wireless app is free and needs no subscription. Users download it and join the conversation just like they had a wired BeltPack.

The best use case is one that works alongside the wired hardware. I ran a gimbal camera for a service and used the app to hear the video director. My custom molded in-ear monitors were connected to my iPhone with an adapter.

To talk, I’d have had to pull my phone out and push the button to use the iPhone mic. But just hearing the director and knowing when I was live on the livestream was a huge help.

Other good fits:

• Positions that move around, like a roaming camera.
• Non-critical users, like extra people in the control room.
• Separate conversations. With 32 channels, app users can talk on channels no BeltPack is using.

Where PunQtum and the App Don’t Fit

Honest limits matter here, because comms fail at the worst possible moment.

The app is Wi-Fi dependent. Users have to be on the same Wi-Fi as the PunQtum base station. If your production network doesn’t cover the whole building, neither does the app.

Don’t use the app for mission-critical comms. Security teams sometimes come up as a use case, and I don’t recommend it. In the full walkthrough I explain why: security comms should be recordable and run on push-to-talk radios, not people’s personal phones. When someone’s phone app acts up, they won’t be able to talk when it matters most.

Personal phones are a hassle for volunteers. They need charged batteries, earbuds good enough to hear in a loud room, and a phone mount. They also bring notifications and distraction into the booth.

Wired is the heart of the system. If most of your team needs to roam, plan for that from the start. In the full walkthrough I note the hardware wireless route costs far more than the wired PunQtum setup.

Questions to Answer Before You Buy

Work through these with your team first:

1. How many positions talk during a service? Count every seat, not every volunteer.
2. Which teams need their own line? Start with a general line plus a video line.
3. Where can you get Ethernet? The SpeakerStation can power two chains of four BeltPacks. Beyond that, plan for PoE+ switches.
4. Who roams? Decide whether the app is good enough for them, or whether they need something more reliable.
5. Who owns the setup? Someone should understand Q-Tool and the roles, so a volunteer isn’t stuck on a Sunday.

Watch the Video

Here’s my overview of the PunQtum system, including the no-network setup, roles, the producer position and the app:

Ready for the deep dive? How This PunQtum Intercom System Works covers every BeltPack and SpeakerStation function, the Q-Tool settings, PoE+ networking, and setting up app users.

Keep Going

• Every church production system we work on
• ATEM switchers for church livestreaming
• Church AV troubleshooting 101

More training is on the YouTube channel: youtube.com/@CrazyAmazingDesigns.