ConferenceQ User Manual

Chapter 0

Before you start

ConferenceQ is one continuous flow: the audience joins by QR and asks in their own language, the question is translated and reviewed, and it reaches the presenter’s screen. This chapter lays out that flow and the people in it.

The four roles

The path a question takes

1. 1SubmittedThe audience writes in their own language
2. 2TranslatedTranslated with the Glossary applied
3. 3ReviewedA moderator approves or hides it
4. 4QueuedIt joins the running order
5. 5AnsweredThe presenter answers and marks it done

Chapter 1

Signing up and signing in

You sign up as an institution, not as an individual. Whoever signs up becomes its first admin, and adds colleagues from the console afterwards.

Creating your institution

1. Institution name — shown as-is on the audience screen and in the console header.
2. Institution subdomain — the address your attendees and staff arrive at. Lowercase letters, numbers and hyphens, 3–32 characters. Availability is checked as you type.
3. Default time zone — the default for new events. Each event can override it.
4. Admin account — name, email, password. Each requirement ticks off as you satisfy it.

Signing in

When sign-up completes you land on your institution’s own sign-in page (for example iso.conferenceq.live/admin/login). The certificate is issued automatically on that first visit — there is nothing to register. You can copy the address any time from Organization settings in the console.

Chapter 2

Preparing an event

Create the event, add its sessions, then prepare the QR codes, materials and terminology. This is everything you do before the day itself.

Create the event

The join code is what your audience types at /join. An event code sends them to whichever session is running at that moment, so one printed code covers an event with many sessions.

Sessions and their status

Generating and handing out QR codes

Uploading presentation materials

Glossary — pinning your terminology

Priority runs Session > Event > Organization. When the same source term exists in several scopes, the narrowest one wins. A new term applies from the next translation onward — questions already translated are left as they are.

Branding

Chapter 3

Collecting attendees in advance

Use this when you want to collect attendees before the day. You get one address (/r/code) and a QR; the attendee leaves their details, confirms their email, and receives a personal entry link by mail. You can also restrict a session so only those people can join the Q&A.

① Create a form

1. The form name is internal. You can create several forms per event — advance and on-site, general and VIP.
2. You get a public code such as REG12345, and the address becomes …/r/REG12345.
3. It starts open. Set it to unpublished if you are not ready to announce it yet.
4. Leave the window and capacity empty for no limit. Unconfirmed registrations take a seat too.

② Dress the page — image and background

The content cards stay white, so any background remains readable. On a dark background the text and logo outside the cards switch to their light version.

③ Set the messenger preview

1. Leave them empty and they are built from the page title and introduction. The card appears either way.
2. The image is chosen in the order share image → organization image → background. Fill the first one only if you want a different picture just for sharing.
3. The share image is cropped to 1200×630, the ratio messengers ask for.

④ Share it as a QR code

The same QR is also available on the event’s QR screen, under the Registration tab. A registration address carries no join code, so it is safe to put on posters, invitations and your website.

⑤ What the attendee goes through

1. Restricting entry is a per-session switch, turned on and off in the session list further down the registration screen.
2. When on, only people who confirmed their email can open that session’s Q&A. When off, the join code is enough, as usual.
3. The entry link is issued to one person. Opening it once leaves the credential on that device for the day of the event.

⑥ Checking and exporting registrants

Chapter 4

What the audience sees

The audience installs nothing and signs in to nothing. Scanning a QR or typing a code is the whole of it — but one of the two is required. The code is the key to the room.

Taking part in a poll

The clock at the top right is the time left. It turns red at ten seconds and the server closes the poll at zero. The server decides, not the clock on your screen — a tap at the very last moment may not be counted.

The globe button at the top right switches between Korean and English. What changes is the interface wording; question text always shows the original and its translation together.

Chapter 5

The moderator’s working screen

During the event a moderator watches this one screen. Incoming questions on the left, the running order for the presenter on the right.

1. Approve — the question appears in the audience list and in the Presenter Queue.
2. Hide — it drops off the audience screen. This conceals rather than deletes; the record stays.
3. Edit translation — fix an awkward rendering. Your edit is stored separately; the machine translation is kept.
4. Re-check duplicates — rescan just that question for near-matches.

Merging duplicate questions

On a narrow screen such as a tablet the right-hand panel is tucked away. The “Queue · Polls” button at the bottom right slides the Presenter Queue and polls out as a drawer.

Running a live poll

1. New poll — one question and 2–8 options, in Korean or English, whichever is easier. The other language is added automatically the same way questions are (Glossary applied) and shows up on every screen a few seconds later. Pick a time limit from 30 seconds to 10 minutes, or leave it to close by hand.
2. Create and start — it appears on the audience, presenter and projector screens at that moment. Save only keeps it as a draft to start later.
3. Close — you can close it early by hand. When the time runs out the server closes it for you.
4. Reopen — open a closed poll again with a fresh time limit. Votes already cast are kept.

Running the Presenter Queue

The right-hand panel is the order the presenter will see: answering → queued → most voted. “Show on screen” makes a question the current one on the presenter’s screen; “Mark answered” takes it out of the queue.

Chapter 6

The presenter’s screens

The presenter has two screens: one they operate on stage, and one you put on the projector.

Presenter View — operated on stage

Long questions shrink a step at a time, and if they still overflow only the question area scrolls — the controls at the bottom always stay on screen. If the connection to the server drops for a moment a notice appears, and it resumes on its own once reconnected.

Live poll results — small, large, minimal, hidden

“Hide poll” tucks away the current poll only; “Show poll” in the top bar brings it back. Your small/large choice is remembered in this browser and applies to the next poll too. After a poll closes the results stay for 45 seconds, then step aside on their own.

Stage Display — for the projector or LED wall

On the projector an open poll replaces the question with large results (there are no controls). The join card carries a QR code, so latecomers can join from the screen alone.

Chapter 7

Live captions

As the speaker talks, each sentence is recognized in the presenter’s own browser and sent to the audience and the stage as captions. Same principle as questions — the original is kept and the translation sits beside it, and the moderator turns it on or off.

Presenter — starting captions

1. The moderator can fix the speech language; otherwise the presenter picks KO / EN.
2. On-device recognition is the default — the audio never leaves the machine. If that language isn’t available it falls back to cloud recognition automatically.
3. A strip on the presenter screen shows the sentence just recognized, its translation, and which engine is in use (on-device / cloud, server / browser translation).

Captions on the audience screen

Moderator — on/off and cleanup

Chapter 8

Stage slides

An optional way to show the session’s uploaded material (PDF) on the stage screen, one page at a time. Pages are turned with the arrow buttons on the presenter screen.

Presenter — turning pages

The stage screen

1. In the console’s right-hand panel, Stage slides is where you pick which material to use and turn the stage display on.
2. Upload a PDF under the session’s materials and it appears here and on the presenter screen right away.
3. To toggle just the stage captions on the spot, add ?captions=1 or ?captions=0 to the stage URL.

Chapter 9

During and after the event

Keep the dashboard up while the event runs; afterwards, build your report from the analytics and the log.

Dashboard — what you watch during the event

Alerts watches for translation failures and a growing review backlog. Past 20 questions awaiting review it warns you — that is the moment to put a second moderator on it.

Analytics and CSV

Audit Log

Users and the organization

Appendix

Question status reference

Permission matrix

Troubleshooting