How Do Churches Get Tech Support for Their AV Systems?

The question behind the question

When a church searches “tech support for church AV,” it’s rarely curiosity — it’s the morning after. Something failed on Sunday, the one person who understands the system was unreachable or exhausted, and someone finally asked the structural question: who is actually supposed to help us with this stuff?

The honest answer is that church AV support was never one thing — it’s a stack of five layers, and most churches are running on two of them. Here’s the whole map, what each layer is genuinely good at, and where the gaps have historically lived.

Layer 1: community and manufacturers — deep, free, and slow

The forums (OBS’s, the console communities, church-tech groups) and manufacturer support lines hold enormous expertise, free. Their limits are structural: forums answer on forum time, and a manufacturer supports their device — nobody at the camera company owns the question of why the camera, the switcher, and your network aren’t agreeing. Use this layer for Tuesday research and single-device questions; never plan a Sunday around it.

Layer 2: the local integrator — brilliant at builds, wrong tool for Sundays

AV integrators design and install systems, and good ones are worth every dollar — when to hire one is its own honest question. But their model is project-shaped: quotes, installs, punch lists. Weekly operation, volunteer questions, and 9:40-on-Sunday failures were never what integrators were built to carry, and it’s unfair to expect it of them.

Layer 3: the volunteer expert — the layer carrying everything else

In most churches, layers 1 and 2’s gaps all drain to one place: the volunteer who knows the system. They are the support plan — which works until it burns them out, and fails completely the Sunday they’re away. A support stack exists precisely so this person becomes a layer instead of the whole architecture.

Layer 4: automation and AI — the support that’s already there

This layer barely existed five years ago, and it changes the math. Automation shrinks tickets before they’re opened: Self Healing catches a dropped stream or stopped recording the instant it happens and offers a one-tap restart, monitoring watches the booth around the clock, and alerts reach humans only when a human is needed. AI support answers the questions that remain — and the difference from asking a chatbot is context: Luminos reads your actual system — your live inventory, your Signal Map down to cable labels — so “why is camera two dark?” gets an answer about your camera two. Luminos in the app is unlimited on Pro and Max (on Free, 5 conversations a month for verified churches), and Journey, the same intelligence answering 910-WORSHIP by phone, comes with Pro ($49/mo, 2 hours a month) and Max (5 hours).

Layer 5: humans who can see your system

For everything above a machine’s pay grade, the question is what kind of human stands behind Sunday — and this is a choice, not an accident. The Care add-on puts a person on weekdays, 9 to 6 CT, with up to 4 hours a month of remote help, priority email tickets, and 2 more hours a month of AI phone support. Sunday Assurance puts a production pro on call Sundays, 5 am to 2 pm CT, your system on their screen the moment you dial, and makes AI phone support unlimited. And a detail worth knowing about who answers: there’s no call center behind any of it — WorshipMetrics is a pastor, an engineer, and an AV educator who’ve spent their careers in church production, and Paul still answers 910-WORSHIP himself.

What makes this layer different from “hiring an IT guy” is visibility: support starts from your telemetry, your support history, and your documentation — diagnosis, not description.

Stacking it: the plan that fits on an index card

Tuesdays: forums and manufacturers for research; integrators for projects. Always-on: automation, monitoring, and AI that knows your system — free to start. Sundays: your trained team first (the deepest support layer is more people), with Sunday-morning humans behind them at whatever depth your church chooses.

Build the stack and the original question dissolves: nobody asks “who’s supposed to help us?” in a church where every layer already knows the answer.