Servantly Ask – Private Q&A with Spam-Blocking Moderation

No. Submission and archive voting are guest-friendly by design. Only the control panel requires a logged-in user with presenter or higher access.

Each browser gets a random, anonymous cookie the first time it votes (no personal data, not used for tracking or advertising, and never shared with anyone). That cookie — not the visitor's IP address — is what prevents a repeat vote, so multiple people on the same shared Wi-Fi (a shared convention network, for example) can each vote once without blocking each other.

Create a page with [servantly_ask_live_display], style it under Settings → Live Display, and create a second page with [servantly_ask_control_panel] for the operator. The control panel sets which question is live; the display polls and updates automatically. The Live Display page hides the WordPress admin bar when you are logged in, so you do not need a separate incognito window for the projector.

Yes — this is one of the most common uses at technical conventions and meetups where a speaker is running their own Q&A. Open the Live Display page full-screen on the room's projector or screen, then open the Control Panel on your own phone. The Control Panel is mobile-optimized with large touch-friendly controls, so you can approve, advance, and go live on questions yourself, from the podium, without needing a separate operator. On supported phone browsers the Control Panel also keeps your screen from auto-locking while it's open.

Servantly Ask scans published pages and posts for the six shortcodes. Under Settings → Shortcodes you can see detected pages, choose a primary page when more than one uses the same shortcode, and turn quick links on or off for the admin submenu (moderators), the logged-in admin bar (moderators and presenters), and the Control Panel toolbar. Links only appear when a matching published page exists.

Yes. Settings → Live Display → Waiting message. Leave blank for the default line shown when no question is live.

Yes, two ways — and it's on by default. Out of the box, the waiting screen already shows an auto-generated QR code to the left of the message "Scan to ask your question — we're starting shortly," so there's nothing to configure for a working call-to-action from the moment you activate the plugin. Under Settings → Live Display → Waiting QR code you can change any of that: switch to Upload my own image to use a QR code from another tool (recommended 1024×1024 px or larger for 4K screens), turn it Off entirely, move it above/below/beside the message, recolor it, or edit the waiting message text to your own wording. The auto-generated code has a transparent background, scales to any screen size without going blurry, and matches your Live Display's text color by default (with its own color picker if you'd rather pick something else). Either mode, it's hidden automatically as soon as a question goes live.

No — it's built for exactly that. The public Question Queue shares one cached snapshot of the current questions and votes across every visitor instead of rebuilding it for each phone, and a phone only gets a fresh update when something's actually changed (a new question, a new vote, a new live question). When nothing has changed, the check-in is nearly free. That keeps things responsive whether you have a handful of attendees or a stadium full of them, on ordinary WordPress hosting — no special server, no add-on service, and no websockets required.

Yes — go to Servantly Ask → Sessions. Each session you add gets its own independent question queue, Live Display, Control Panel, and auto-generated QR code, so you can run a WordCamp with five concurrent speaker tracks, or a church with several Bible studies meeting in the same hour, from one install. Add sessions one at a time (talk name, presenter name, room, optional scheduled time) or paste in a whole day's lineup at once — one session per line, and pasting straight from a spreadsheet works. Each session shows its own status (Upcoming/Live/Ended) and pending-question count on the list. If you never visit the Sessions screen, nothing changes: Servantly Ask keeps working exactly as a single, site-wide Q&A.

They're always auto-generated — a session's QR code always points straight at that session's own dedicated submission link, so there's nothing to upload or keep in sync as you create new sessions. (The single, site-wide waiting QR code under Settings → Live Display still offers the choice between auto-generating one or uploading your own, since that's meant for a single ongoing Q&A, not a fast-changing schedule of sessions.) Each session's QR code is available as a thumbnail on the Sessions list and on the Print Cards sheet, where it's placed on a full card — logo, talk name, room, QR code, and a "scan to participate" line — styled with the same colors and fonts as your Live Display, ready to hand out or tape on a door.

Yes. Use the Reset action on that session's row: it archives its current questions and clears its live state, but keeps the exact same link and QR code — nothing to reprint or re-share before next time.

Optionally, yes. By default any user with the servantly_ask_present_questions capability (Question Presenter role, or an Administrator) can open any session's Control Panel — same as the single-Q&A behavior. If you'd rather restrict one session to a specific speaker who already has a WordPress account, enter their username(s) or email(s) in that session's WordPress users field on the Sessions screen; only they (and site-wide managers) will be able to access that particular session's Control Panel. Leave it blank to keep it open to anyone with presenter access.

Use presenter invites. There are two ways to send one: type the speaker's email straight into the "Presenter email" field when you create their session (either the quick-add row, or as a 4th | email field on each line when bulk-pasting a whole day's schedule) — the invite email goes out the moment the session is created — or add/change it later from the "Email invites" field on that session's row on the Sessions screen. Either way, Servantly Ask generates a private, one-of-a-kind link and emails it to that address automatically, with a short explanation of what it's for. Opening that link puts them straight into their session's Control Panel — no account, no password, no login screen at all. It's scoped to that one session only, so it can't be used to touch anything else on the site. This is meant for one-time or guest speakers you'll never otherwise need a WordPress account for — a WordCamp with 30 different sessions a day doesn't need 30 new site logins. If a link needs to be re-sent, or you're worried it was shared, click Resend to invalidate the old one and generate + email a fresh one, or Revoke to shut it off entirely. The organizer-facing View link button next to each invited presenter also lets you copy the link yourself, in case you'd rather text or message it instead of relying on email. Every invite e-mail also comes with two attachments, so a speaker has everything they need even if no one ever hands them a physical card: a 2-page PDF — page 1 is their public door card (branded with your Live Display's colors/fonts/logo, ready to print and tape up), page 2 is the confidential page with their secret link, its own QR code, and a warning not to share it — plus the audience QR code as a standalone image file, for a speaker who'd rather drop it into a slide, a website, or a venue screen instead of printing anything. Both are generated natively in PHP at send time — no Composer packages, no Imagick, nothing to install — so this works on ordinary WordPress hosting out of the box. (The logo and the standalone QR image need the PHP GD extension, present on virtually every WordPress host; without it, the invite still sends normally, just without a logo/image, and the plain-text secret link always works either way.) Because the link itself grants access, treat it like a password: don't post it publicly. That's also why the Print Cards view keeps it well away from the public door card — any session with an active email invite gets one extra, clearly marked "CONFIDENTIAL" page per presenter, always forced onto its own separate printed sheet, with the secret link, a matching QR code for the presenter to scan with their own phone, and an explicit warning not to share it. The public QR/room card that's meant for the audience never includes it.

Yes. Open the "Customize the presenter invite e-mail" panel near the top of Servantly Ask → Sessions to edit the subject and body used for every presenter invite from then on — handy for matching your event's name and voice instead of the generic default copy. Use placeholders like {talk_name}, {presenter}, {room}, {time}, {link}, {site_name}, and {email} anywhere in your text, plus two convenience ones: {greeting} (a ready-made "Hi [name]," that's blank if no presenter name was entered) and {meta} (room + time already combined, blank if neither was set). Click Reset to default text to load the built-in wording back into the fields (nothing is saved until you click Save Template), or simply clear both fields and save to revert instantly. The PDF and QR attachments always send regardless of what the text says.

Each session's link is independent, so scanning the right code always takes attendees straight to that session's own submission form. As a fallback for a QR code that's smudged, too small, or otherwise won't scan, add the [servantly_ask_session_picker] shortcode to a lobby or hallway page — it lists every currently-live session by name and room with a direct join link, so attendees can find the right one manually.

For many conferences, conventions, company events, and classrooms — churches too — it can: you get moderation, no per-participant SaaS cap, and it runs on your own site. You host the pages and run the live segment with the built-in control panel and display — whether that's a conference keynote, a convention panel, a lecture hall, or a Sunday service.

Honeypot and rate limiting still apply. Akismet adds another layer if installed. Shield Pro can receive honeypot bot reports when licensed.

No. Options are stored in the WordPress database. Version upgrades only add missing defaults; they do not overwrite saved keys, labels, or theme choices. Each settings tab saves independently so unrelated tabs are not cleared when you save another tab.

No. Servantly Ask itself is 100% free — no paid tier, no feature paywall, no usage caps. Optional WhoKnew Shield Pro is a separate product for site-wide security, not a requirement for anything Servantly Ask does.

Deactivating the plugin does not delete anything — questions, categories, votes, and settings all stay in your database exactly as they were, so reactivating later picks up right where you left off. There is currently no delete-on-uninstall routine, so removing the plugin's files does not remove your data either; if you need a full data wipe, delete the questions and settings manually first.

Yes — every string in the plugin uses the servantly-ask-qa-spam-protection text domain, so it's ready to be translated via WordPress.org's translation platform or your own .mo files. No translations are bundled yet; it currently ships in English only.

Yes, one piece: the QR code encoder is a ported, bug-fixed derivative of two upstream MIT-licensed libraries — Kriv-Art/Qr-Code (Copyright (c) 2019 Noah Too, https://github.com/Kriv-Art/Qr-Code) and Project Nayuki's QR Code generator library (Copyright (c) Project Nayuki, https://www.nayuki.io/page/qr-code-generator-library). Full license text is bundled at includes/lib/LICENSE-qr-encoder.txt. Everything else — including the PDF writer used for presenter invite attachments — is original code with no external dependencies.