Hosts
How do I prepare a live event?
Start from the host flow, choose a ready-made format or blank draft, then share the join code or QR code with players.
Loading Discera…Loading Discera…Loading Discera…Loading Discera…Self-service answers
Answers for hosts, players, and buyers planning a live Discera quiz session.
Not in the list below? Ask in your own words about the product manual and follow the citations back to the relevant sections.
Your question is sent to OpenAI to generate the answer and is kept by Discera for up to 90 days. Please do not include personal or confidential information. Read the privacy policy.
Preparing an event, choosing a format, and getting the room in.
Start from the host flow, choose a ready-made format or blank draft, then share the join code or QR code with players.
No. Players join from a short code or link and can play from a browser without installing an app.
Player join codes, links, and quick troubleshooting.
Confirm the six-letter code, ask the host whether the room is still open, and reload the join page before trying again.
Keeping a room moving during a live session.
Hosts can use the recovery flow when they have a recovery code for an active session.
Player support and safe live-room controls.
Discera supports live review queues, panic hide, display-name blocking, Run-scoped moderator sessions, moderation audit exports, and rate limiting for shipped audience surfaces, with known limits buyers should understand.
Discera moderation is built for live events where audience text can reach a shared screen. The controls are Run-scoped, visible to the host, and designed to keep review decisions close to the live room.
Pre-display review queues can hold open-ended answers, word-cloud answers, type-in answers, brainstorm ideas, Q&A submissions, and message-wall posts when the relevant moderation mode or profanity filter is enabled.
Pending and rejected audience content is kept off shared player and presentation screens. Q&A and message-wall participants can still see their own held items, but not other players' pending or rejected content. Host and moderator review surfaces keep those rows available for decision-making and recovery.
A Run-wide panic hide can suppress audience-contributed content from player and presentation screens while review surfaces remain available to hosts and moderators.
Display names can be blocked at join using the baseline blocked-term list and host-provided custom terms. Hosts and moderators can review blocked attempts and grant an override for a player session.
Moderator/operator access is scoped to a single Run. Each moderator session is named, auditable, and revocable per session or in bulk.
Plain-language privacy answers with the policy as authority.
The privacy page is the source of truth for data handling, retention, analytics, and browser storage.
Current availability and buyer-facing next steps.
Discera is currently presented as a beta product while the live-event workflow continues to mature.
Email mab@consensus.dk with your event date, expected audience size, and the kind of session you are planning. We reply during European business hours and set up the pilot agreement, a named contact, and an escalation channel before your first event.
Moderation actions write audit rows. Finished-Run exports include moderation audit coverage, and workbook exports include moderation state for Q&A, message wall, answers, and review actions where those surfaces are present.
Public mutation paths use rate limiting and repeated-abuse lockouts at a high level, so rapid repeated attempts can be slowed or temporarily blocked.
Discera does not yet provide player mute or player reporting controls.
The automated profanity filter is deterministic and term-based. It is a backstop for review, not comprehensive multilingual or evasion-proof filtering.
Host-created quiz content, including question and option text, is not comprehensively filtered before display.
There is no single buyer-facing strictness level and no moderation analytics dashboard today.
Score-bearing type-in answers can be held and reviewed, but after results are finalized, takedown changes visibility only; finalized scores are not recomputed.
Use the Trust page for buyer-facing implementation boundaries and the privacy page for policy-level data handling and retention detail. Moderation copy should not be treated as an enterprise security review substitute.
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. Discera does not offer 24/7 coverage, a status page, or a formal service-level commitment.
Discera runs corporate pilots through a named contact rather than a public support desk. This answer describes what support and availability a pilot can expect today, so the commitment can be checked before an event is booked.
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.
For sales, product support, or accessibility questions, email mab@consensus.dk.
Self-serve recovery paths that work without contacting Discera: host recovery codes for a lost host session, player rejoin, and the presentation retry path.
Operational diagnostics that let Discera detect and triage live failures, where repeated breakage during an active Run session is treated as the highest internal severity.
No 24/7 coverage, on-call rotation, or paging service.
No public status page and no published uptime target.
No formal service-level commitment, support tiers, or service credits.
Escalation outside a pre-arranged event window is best-effort and may not be answered while the event is running.
Response targets are goals rather than contractual guarantees, and they exclude weekends and Danish public holidays.
The Trust page carries the buyer-facing implementation boundaries and the support hub carries the operational detail for event crews. Support expectations should not be read as an enterprise service-level commitment.