Read: "@Pep what's channel 1 at?"
You test both ways people use PEP: the Slack bot (@Pep … in a church channel) and the iOS app. They run on the same backend — same brain, same mixer tools — so the same request should produce the same move on both. Pay particular attention to where they diverge.
Severity, safety, and reporting are the same as the main test plan — file findings in Pep Issues; see How issues flow. Marlon covers the app in depth; your focus adds Slack and the cross-surface check.
Pick a venue with no service or rehearsal on — check the schedule in Monday.com and steer clear of any church in or near a service window.
It moves real faders — restore everything when you're done (or say "undo" after each change).
Tasks marked [Caution] can silence or unbalance a PA — only on a safe board.
Known and waiting on a direction call — don't log these as new bugs:
Mix presets aren't wired up (app). The preset tiles — Sunday Service, Spoken Word, Full Band, Acoustic Set, Broadcast — are UI only for now; tapping one doesn't change the mix. Tracked in Questions for Tom.
Undo is unreliable (both surfaces). It only works when the agent reads a value first ("vocals up 2"), not on absolute sets ("set vocals to -6"), and it won't override a change made at the console. "Undo didn't work" is expected for now — tracked in Questions for Tom.
Slack — type @Pep … in the church's channel. No screens, no mix picker, no voice. Less scaffolding than the app, so you address FOH vs IEM directly in the message:
FOH (house): just say it — "@Pep bring the vocals up a touch."
IEM / monitors: name the bus — "@Pep more kick in the WEDGE," "@Pep more of John in Mon 4."
App — FOH and IEM screens, a mix picker, voice mode, and a bit more built-in steering.
Same backend → the same ask should land the same move either way.
Read: "@Pep what's channel 1 at?"
Level: "@Pep bring the vocals up a touch." · "vocals up 2" · "set the kick to -6"
Several at once: "@Pep bring all the drums up a touch."
Fade: "@Pep fade the music out over four seconds."
[Caution] Mute: "@Pep mute channel 5," then "unmute the vocal."
FOH vs IEM, directly: FOH — "@Pep turn up the lead vocal." IEM — "@Pep more kick in the WEDGE." Confirm the monitor request hits the bus, not the house.
Effects: "@Pep more reverb on the lead vocal."
Rename: "@Pep John is on channel 1," then "bring John up."
Undo: "@Pep undo." · "put it back."
Thread memory: in the same thread, follow up with "a little more" — does it remember what you touched?
Limits/honesty: "@Pep the kick is too boomy," "pan the guitar left," "recall the worship scene" → honest decline, not a fake "done."
Run the FOH, IEM, and Voice-mode sections of the main test plan.
App-specific: the IEM mix picker, the FOH/IEM screens, and voice mode (none of which exist on Slack).
Same request, both ways: "vocals up 2" in Slack and in the app → same resulting level? Same confirmation?
IEM both ways: app (pick mix → "more kick in my ears") vs Slack ("more kick in the WEDGE") → same send move on the same bus?
Mis-hear / misfire: does one surface get a request wrong where the other gets it right?
Tone: is Slack terser or more verbose than the app for the same ask? Note any divergence.
File findings in Pep Issues (Inbox), and tag whether it's Slack, App, or both in the title. See How issues flow.