Loading Discera…Loading Discera…Loading Discera…Loading Discera…Support hub
Practical help for preparing a live quiz, getting players in, and recovering during an event.
For sales, product support, or accessibility questions, email mab@consensus.dk.
Prepare the event content, open the player join surface, and keep the host console available before the room starts.
Players should use the current join code or join link from the host. Ask them to reload if an old code was cached in the browser.
If the host tab is closed or moved, use the recovery route with the recovery code for that active session.
Use review queues, panic hide, blocked-name review, and named moderator sessions to keep audience text under control during high-attendance sessions.
For high-attendance or externally visible events, assign someone to watch the moderation queue and player-support panels before the room opens.
Use pre-display queues for audience text surfaces that should be reviewed before display.
Use panic hide when audience-contributed content needs to disappear from player or presentation screens immediately.
Use named moderator sessions for crew members who should review content without receiving full host control.
Use the finished-Run export when you need a record of moderation decisions after the session.
Use the privacy page for policy-level detail. Support content should summarize, not replace, privacy commitments.
For pilot support requests sent to mab@consensus.dk, we aim to acknowledge your request within two business days, during European business hours, Monday to Friday. This is a best-effort target, not a guaranteed response or resolution time.
For a scheduled pilot event, agree the named contact and a direct escalation channel before the event date. Discera does not provide automatic staffed event coverage.
Escalation that was not arranged in advance falls back to best-effort follow-up during European business hours, which can land after the event has ended.
Agree the named contact, the escalation channel, and the covered event window while the pilot is being scheduled.
Try the built-in recovery paths first: the host recovery code for a lost host session, player rejoin for a dropped participant, and the presentation retry path for a failing room display.
When escalating, send the event time, the affected surface (host console, player device, or presentation screen), and what participants saw.
Do not send host control links, recovery codes, or participant names. Discera does not need them to diagnose a live failure.