CueProX
⌘K

Docsqa-pipeline

The public submit page

What audience members see when they scan the QR code.

The public submit page

When an audience member scans the QR code on the projection screen, they land on the Q&A submit page — a simple, mobile-first form for typing and sending a question.

URL: /q/{token} — unique per room, generated when the room is created.

Treat this URL like an internal broadcast link. Share it with the audience through the QR display — not via social media, public event listings, or printed programs that might circulate beyond your event.


Page states

The page shows one of four states depending on what's happening in the room at that moment:

No active event — a gray banner reads "Q&A starting soon". The form is hidden. This is what the audience sees before the event begins or between events.

Q&A closed — an amber banner reads "Q&A is closed". The form is hidden. Questions cannot be submitted.

Q&A open — an emerald banner with a pulsing indicator reads "Q&A is open — ask your question". The form is visible and active.

Token invalid — a 404 page. This means the URL is wrong or the room no longer exists.

Note

Questions submitted while Q&A is closed are not stored — the form isn't visible in the closed state, so there's nothing to submit. If the audience arrives between segments and Q&A is closed, they'll see the closed banner and can try again when it reopens.

The form

When Q&A is open, the form has two fields:

Name (optional) — up to 100 characters. If the room has the name field disabled, this field is hidden entirely rather than shown as optional.

Question (required) — between 5 and 500 characters. A character counter shows {length}/500 and turns amber as you approach the limit (when fewer than 50 characters remain).

The Submit button cycles through states:

  • "Submit question" — idle, ready to send
  • "Sending…" — request in flight
  • On success: the button disappears and a green "Question submitted!" banner appears. After 4 seconds the banner clears, the form resets, and the button returns. The audience member can submit another question.
  • On error: an error message appears below the button; the button returns to idle.

Note

Submitters are rate-limited to 3 questions per 60 seconds per device. If the limit is reached, the form shows an error message with a countdown indicating how many seconds to wait before trying again.

Designed for phones

The submit page is intentionally minimal and touch-first. There's no navigation, no sidebar, no CueProX branding beyond the logo. It loads fast and works on any smartphone that can scan a QR code — no app, no account, no login.

Important

The public token in the URL is permanent for the room — there is no self-serve way to rotate it. If a token ends up somewhere it shouldn't (a printed QR leaked, a URL shared publicly), contact support via the Helpdesk to request a token reset.
Was this helpful?