Skip to content
LogosPilot
Request private preview

For the person at the desk on Sunday

LogosPilot for volunteers

You do not need to be technical to run this. This page explains what you actually do during a service, what the software does on its own, and what happens when something goes wrong.

What your job becomes

Today, running Scripture on a screen usually means listening hard, recognizing a reference, finding it, typing it, and getting it up before the moment passes — while also watching everything else.

With LogosPilot, the software listens for the reference and puts the passage up. Your job changes from typing to watching. You are still in charge; you are just not racing a sentence.

You are not replaced by it

The software never decides anything you cannot immediately undo. It stops when you tell it to, and it stops on its own when it is unsure.

The three controls

Almost everything you need during a service is one of three actions.

What you do during a service
ControlWhen you use itWhat happens
Stop automation Anything unexpected. When in doubt, stop It halts immediately and does not start again until you start it
Take manual control You know the passage and want it up now You search and select it yourself. Your choice replaces whatever the software was considering
Clear output Something is on screen that should not be The display clears

That is the core of it. If you remember only one thing on your first Sunday, remember that stopping is always safe.

If you get it wrong

The software is built around the same fear you have

If LogosPilot is not confident it heard a reference correctly, it does nothing at all — no slide, no display change. A blank screen is recoverable. Wrong Scripture in front of a congregation is not. That is the software making the same call you would make.

Nothing you do at the desk is permanent. Clearing the output, taking manual control and stopping automation are all immediate and all reversible. There is no state you can get into that requires somebody technical to rescue you mid-service.

Working from inside the room

A paired tablet lets one person operate from within the room rather than from the booth. It extends your reach; it does not become a second brain. The desktop host stays authoritative, so there is never a question of which device is really in charge.

When something breaks

What to expect, and what to do
If this happensWhat the software doesWhat you do
The internet goes down The passage on screen stays and you carry on manually. Recognition resumes when the connection does Carry on
The microphone feed is lost It stops listening for references Use manual control. Everything else still works
Something stops responding It restarts the component rather than leaving the service without output Usually nothing
A licensing message would appear It is recorded and dealt with after the service Nothing. It never appears where the congregation can see it

What you need to learn

Honest answer: the three controls above, and where the passage search is. Everything else can wait until you have run a service.

Training material is still being written

A volunteer guide and step-by-step procedures are being written against the current build and are not published yet. This page will link them when they exist rather than listing them before they do. Until then, support@logospilot.com answers questions directly.

If you want to see the whole service from start to finish, read A Sunday with LogosPilot.

Where to go next

Request private preview A Sunday with LogosPilot Installation guide