Q-SYS support that starts at the touch panel

Something in the room stops working. The customer sends a ticket, and it says what they saw. "The mics are out in the training room." Fair enough. That's what they know.

So support writes back. What does the panel say? When did it start? If the system is on Q-SYS Reflect, someone signs in and goes looking for logs. Sometimes they're there and they help. Sometimes they're not detailed enough to act on, and somebody remotes in to work out what happened.

QR Jockey puts a Q-SYS QR code on the touch panel that starts that conversation for you. The customer scans it with their phone. Their mail app opens a trouble report that's already addressed to your support email, with the site, the design, the Core and its network details filled in. They add a line about what went wrong and send it.

Why a QR code

We built it for a church we support. We wanted them to reach us right from the touch panel, so the first idea was simple: a QR code that opens an email to our support address.

Then it got more useful. The phone is writing the email anyway, so the plugin can write the first part. The details we'd normally ask for are in it before the customer types a word.

The phone sends the email, not the Core. So the QR works on a system with no way out to the internet at all.

One press when the Core can email

A QR code only holds so much. So if the Core can reach a mail server, give QR Jockey your SMTP server and the panel gets a Send Trouble Report button.

For example, in an office with a row of meeting rooms, a room fails ten minutes before the board meeting. Someone presses the button. QR Jockey emails the full report through your SMTP server: which components are faulted or missing, the status from a Status Combiner block, any notes typed on the panel, and a timeline of what changed.

The two don't depend on each other. If the email can't go, the QR still works.

Don't want email at all? Turn it off, and QR Jockey is a QR-only support surface.

A timeline that's still there after a reboot

QR Jockey keeps a timeline of the room: components changing status, restarts, the network changing, warnings and errors. It survives a script restart and a Core reboot.

Each block also writes that timeline to a log file in the Core's media folder. If the system is on Q-SYS Reflect, open Core Manager from there and read the file. No need to ask the customer for anything.

The rest of the panel

The same block draws the QR codes people ask for anyway:

• A Wi-Fi QR, so a guest scans to join the network
• A UCI link QR, so someone can open the room's UCI on their phone
• Up to nine custom QR codes, for a help page, a booking link or anything else

It also sweeps the design's components on a schedule, every 30 seconds, minute or five minutes, so the report knows what's down.

So, that next service call

Maybe it's a church whose volunteers aren't sure who to call. Maybe it's an office where the room has to work at 9:00. Either way, the first message you get can carry the answers you'd have asked for.

QR Jockey is licensed per Core, with a 10-minute demo built in. Try it on the QR Jockey page.

Need something that doesn't exist? We build that too.