How Pulse works — from joining a room on your phone to running a workspace. Can't find it here? The full guide goes deeper.
Scan the QR code on the stage screen, or open the join link the organizer shares — that's it. No app, no account, nothing to install; the same page works whether you're in the room or watching remotely.
Ask anyone already in the room to tap the QR button in the top corner of their Pulse view — it brings up the same join QR and link to scan or copy. (You can only re-share a room you're already in.)
Yes — in Branding, set the QR's color and optionally embed your workspace logo in its center. The color is checked so it stays scannable on the white code card, and the same design is used on the stage screen and when someone re-shares the code in the room.
Passcode-protected events show the code on the stage screen; enter it once to join. If a room is locked, new people can't enter until the organizer unlocks it.
That's the organizer's choice per event. On anonymous events your identity is pseudonymized everywhere — to other attendees, staff, and even support. See Privacy & data.
Staff roles nest: owner ⊃ organizer ⊃ presenter. Every staff role can moderate the live room — the difference is who can configure the workspace.
Request a one-time sign-in ("magic") link by email, or set a password for quicker access later. Staff sign in; attendees never have to.
A workspace is your organization on Pulse — its events, members, branding, and plan. You can belong to several; switch between them from the console. Workspaces are fully isolated from one another.
In People, invite by email one at a time, or Import CSV for many at once (columns email, optional name and role). You can paste an address copied straight from Outlook or another mail client — the Name <name@company.com> form is accepted anywhere an email goes, in the single invite and in the CSV's email column. The import previews every row — invited, skipped (already a member or a duplicate), or an error with the reason — before you confirm. Owners can't be bulk-imported.
Yes — and it's a great way to start. Pulse publishes an open event blueprint format: a JSON file that describes an entire event (agenda with timed segments, speakers, polls and quizzes, prepared Q&A, a survey, appearance). Hand your slides and the spec to an AI assistant you already use; it designs the event and returns a blueprint. In the console, choose Start from a blueprint and upload it — a fully built draft appears, ready to review and run. Pulse itself embeds no AI; it just defines the format so your AI can do the heavy lifting.
Yes — an importable Pulse event-builder skill for Claude. Add it to Claude, share your slides, and it interviews you and returns a blueprint. The skill fetches our living spec each time it runs, so it always builds to the current format rather than an aging download. (It works with any capable AI — the skill just packages the workflow for Claude.)
It lives on our site and evolves with the product, so it never goes stale: the event-blueprint spec (with a machine-readable JSON Schema). If a blueprint has a problem, the import points at the exact field with a fix hint — paste that back to your AI and it corrects itself in one pass.
Yes. Pulse is an MCP server: in the console under Connect AI, create an access token and paste the ready-made config into Claude Code, Claude Desktop, or the API's MCP connector. Your AI can then build and edit draft events and read reports directly — no copy-paste of blueprint files. It works with the same one blueprint format, and it can't run the live room (advancing slides, launching polls, moderating stay human-run) or delete anything. Give a token Read only or Build & edit, set an expiry, and revoke it anytime. Full tool reference: the MCP server reference. (claude.ai web custom connectors, which need OAuth, aren't supported yet.)
Live reactions, raise-hand, pacing feedback (slow down / speed up / repeat), free-flow chat, moderated Q&A with upvotes, and polls, quizzes and icebreakers with live or after-close results. Each is a toggle in setup.
Yes. In event setup, pick a reaction set — default, minimal, energetic, professional, classroom, celebration, focus, sports, or hearts — or choose Custom and tap your own 3–8 emoji from the curated picker (the order you tap is the order attendees see). You also set a control size (X-Small / Small / Medium / Large) for the one-tap buttons. The server only accepts reactions from the set that's in effect.
Yes. Give any agenda segment its own reaction set, and the attendee buttons swap automatically as you move through the run-of-show — so a Q&A block can show 🙋 ✋ ❓ while a celebration moment shows 🥳 🎉 👏. Because segments carry the speaker, this also lets reactions differ per presenter. Leave a segment's set blank to use the event's default.
Yes. In event setup under Content → Video, paste a YouTube link (or video id) into any of three slots: before the event (plays on the lobby screen while people wait), during (plays on attendees' devices when you hit Play video in the moderate view), and after (plays on the ended screen, below the survey). Each slot has a choice: start automatically (it plays muted, since phones and browsers block sound-on autoplay — viewers tap for sound), or let the viewer press play, which shows the video and waits for their tap so it can start with sound. The video shows only on attendees' devices, not the projected stage, and people can close it anytime.
Yes. On a draft event, hit Start rehearsal (in setup or the moderate view). While it's rehearsing, you and your staff can open the join link on another device and experience the real attendee view — react, chat, answer a poll, page through the slides — while the room stays closed to the audience. A clear "Rehearsal — the room isn't open yet" banner shows the whole time. When you're ready, Open the room (go live): the run-through is wiped clean (chat, questions, poll answers, reactions, and the slide position all reset) so the audience starts fresh. Your agenda, decks, and prepared questions stay. Rehearsals never count toward your usage.
Yes — set a start (and optional end) time. Pulse flips it live at the start and ends it at the end; attendees see a countdown until it begins. Manual go-live/end always wins. The end has to be after the start — setup won't let you save an earlier end, and an imported blueprint with a backwards schedule is rejected.
Yes — turn on Presentation timer in the event's engagement settings. A subtle timer then appears on the presenter, stage and moderate screens: time elapsed since you went live, and — if you set a scheduled end — the time remaining, which turns amber in the last five minutes. Attendees never see it.
Yes. From the moderate view's Room notice card, push a countdown or announcement to every device at once — Intermission ends in N min, Session ends in N min (or at the scheduled end), Next session starting, or a custom message. Attendees see a banner with a live mm:ss countdown that dismisses itself at zero; the stage screen shows a large timer. Extend +5 pushes the scheduled end back five minutes (the auto-end scheduler honors the new time) and announces it. Clear it any time.
Yes. In event setup, pick a Next session from your workspace. When this event ends, attendees (after the survey, if you have one) see an Up next card: if the next session is already live they get a Join now button; if it's scheduled they see a live countdown that flips to Join the moment it starts — no refresh. Passcode and lock rules on the next session still apply. Nobody is ever teleported automatically. Moderators and presenters get quick links to open the next session's setup/moderate/present views.
Yes. On a scheduled event's setup page, hit Add to calendar (.ics) to download a standard calendar invite. It carries the join link, the passcode (it's a staff file), and quick links to the setup, moderate, present, and stage views — plus the branded join QR embedded right in the invite, so it's on your phone at the podium. Works with Apple Calendar, Google Calendar, Outlook, and anything else that reads .ics.
Yes. The Events list has a List / Calendar toggle; the calendar places each scheduled event on its day in your timezone, with month navigation and a marker on today. Click any event to jump into its setup. Events without a scheduled date are listed under the grid. List stays the default view.
A lobby: the event title, a live countdown to the scheduled start, and — unless you turn it off — a preview of the agenda (segments, speakers, planned minutes) and speaker cards (name, title, bio). It's the same page they're already waiting on, so they join automatically the moment you go live. Toggle it with "Show agenda before start" in the agenda editor (on by default; off shows just the countdown).
Yes. Each supporting link can be shown manually (you toggle it live), for the whole event, while a speaker is on, or during a segment. Attached links follow the run-of-show automatically — as you advance the deck into a speaker's or segment's part of the agenda, their links appear and then tuck away again, with no manual toggling. A link tied to a speaker who's later removed simply falls back to showing for the whole event.
Yes. Attach a resource to a slide ("after slide N"); it opens in the attendee's Info tab the moment the presenter passes that slide and then stays available. A resource can be a link, a short text note or definition (no URL needed), or both — and it carries a "Slide N" chip that jumps the viewer back to that slide.
Yes. In event setup, add an agenda of segments — intro, each speaker, intermissions, closing — and optionally tie a segment to a speaker and a slide range. When you present, advancing into a segment's slides highlights it automatically (the stage shows "Now: <segment> — <speaker>"), or an moderator can set the current segment by hand.
Two ways. For a workspace-wide default, go to Workspace → Branding → QR code and set the code color and whether to embed your logo — a live preview shows the result. To style the QR for a single event, open that event's setup and hit Customize QR in the Join card; those overrides fall back to the workspace default when you leave them blank, and apply everywhere the event's QR appears (the stage screen, the in-room re-share, and the calendar invite). Want the classic high-contrast look back? Tap Black next to the color picker to set a plain black code.
Yes. Each speaker can carry up to six links — LinkedIn, website, X, GitHub, a custom link, or an email (which opens the attendee's mail app). They appear on the speaker cards in the lobby and the Info tab. For safety only https links and email addresses are accepted — insecure or script-style URLs are rejected — and every outbound link opens in a new tab with no referrer leakage.
Yes. Upload a PDF (or images) in event setup — your browser renders it to static slides, so there are no animations or video, just the grounded slide. You (or an moderator) advance them from the presenter or moderate view, or from the stage screen; attendees see each slide on their phones in sync. The presenter can drive the deck straight from Pulse, or an moderator can advance it for the audience while the speaker presents from anything else.
No. If your instance has the optional converter enabled, open Tools → Convert a
presentation (the Tools link in the console): drop a .pptx
or .ppt and get a PDF back, then upload that as your slides — or use
Create an event with these slides to jump straight into a new event. You can also
drop a PowerPoint directly onto the Slides uploader in event setup and it's
converted in place. If the converter isn't set up on your instance, the same page shows you how to
export a PDF from PowerPoint yourself (File → Save As → PDF) — it's
never a dead end. Conversion happens on the server via an optional service; the core app keeps no
office-document dependency.
If the organizer enables it, attendees can download the slides after the event ends (just the slides that were shown) — optionally only once they've completed the post-event survey. Staff can always download the full deck.
Yes — live, from the moderate view's Stage QR controls (in the Slides card). Turn it on or off, pick which corner it sits in, or pin a position for a specific slide so a QR that would cover a chart tucks away just for that slide and comes back after. Pins are part of the event, so any positions you set during a rehearsal carry straight into the live run.
Yes. On the Slides settings, turn on "Only show slides to people in the room." Pulse learns the venue's network automatically from your stage, presenter, and moderator devices (an organizer can also type a known venue IP). Attendees on that network see the slides; anyone off it doesn't — and it's enforced on the server, not just hidden. One honest caveat the app also shows attendees: a phone on cellular data is on a different network, so it may need to join the venue Wi-Fi to count as "in the room." We match on a per-event hash of the network address and never store raw IPs.
No — and that's enforced on the server, not just hidden. Attendees can page back through slides already shown (with a "Back to live" button to rejoin), but a slide the room hasn't reached yet simply isn't served to them, so upcoming quiz answers or reveals never leak.
Yes. On your phone, pinch or double-tap a slide to zoom in (drag to pan; double-tap again to reset). A reaction strip sits right under the slide so you can react without leaving the view. If you page back to re-read something, a "Live · slide N" pill shows where the presenter is now — tap it to jump back to live.
Yes. On the Slides tab there's a "Hide slides on this device" option; the tab disappears and stays hidden on that device until you tap Show slides again. Your reactions, questions, and other controls always live on the Home tab.
Yes. In event setup (Engagement) or live from the moderator view, reorder the attendee tabs — Home, Slides, Chat, Q&A, Info — with the up/down controls. It changes the order only; a tab still appears only when its feature is turned on, so reordering can never hide something.
Yes — the most recent closed poll's results show on Home, and an "Earlier results" section lists the rest (for polls whose results the organizer made visible). Live quizzes still show you how you did.
Every event produces an end-of-event report: headline stats, per-poll results, a reaction breakdown, an engagement-over-time chart, and a timeline — with a CSV export. Owners and organizers also get it by email when the event ends. It's aggregate-only, never a per-person log.
Seven presets. Dark: Ember (default), Slate, Forest, Ocean, and Midnight. Light: Daylight and Daybreak. Set them under Branding → Theme; add your own accent color on top.
Yes. A workspace has a console theme (what staff see) and a separate meeting theme (what attendees see) — and any single event can override the meeting theme just for itself. So your back-office can stay dark while the audience sees your branded light theme, or vice-versa.
Pulse often runs in a darkened room, with a phone held close to someone's face. Midnight is tuned for exactly that: a deep near-black ground that saves OLED power, ink dimmed just off pure-white to stop bloom in the dark, and a calm indigo accent that doesn't glare up close. Daybreak is its light-room counterpart with the same identity.
Yes, and it's enforced: every preset (and every custom accent) must clear WCAG AA contrast, or the app won't ship it. Poll and result charts keep a fixed, color-vision-safe palette regardless of theme, so results stay readable for everyone.
Pulse is in an open beta. It's fully usable, but we're deliberately benchmarking capacity against real usage rather than scaling ahead of demand — so you may hit limits (concurrent events, attendees, throughput) or brief slowdowns during this stage, and we're tuning as we learn. For a high-stakes event, keep a fallback plan. See the Terms for details.
Pulse includes a free plan with usage limits — concurrent live events, attendees per event, and data-retention window — shown under Plan & usage. Paid plans raise those limits; upgrading opens a secure checkout and a self-serve billing portal. If a payment lapses, your data is never deleted for it — limits simply apply again at the next go-live after a grace period.
Per event, the organizer chooses named or anonymous. On anonymous events every view — attendee, staff, and support — shows pseudonyms, never real identities.
Event content is kept for your plan's retention window after an event ends, then hard-deleted; the event's aggregate summary is kept for your history. You can export a session's template anytime, and export or delete a whole workspace.
Not by default. Operators have no standing access; support can only act inside your workspace after an owner or organizer grants a time-limited "assist" session, which is visible to you and fully audited. Details in the Privacy Policy.
Pulse ships as a single self-contained container. docker run -p 5170:8080 gives you a full working demo with no external services. Production runs the same image with your choice of sign-in (a shared host key, a reverse proxy / SSO, or first-party accounts). The demo path always works with zero configuration. See the guide for deployment.
Check spam/junk first. Brand-new sender domains are sometimes filtered by the receiving mail system (e.g. a corporate Microsoft 365 quarantine) even when delivery succeeded — ask your mail admin to release it or allow-list the sender. You can also set a password once you're in, to skip email next time.
Check whether the room is locked (unlock it in setup) or the event hasn't gone live yet, and that they're using the current QR/link — the re-share button always shows the live one.
Accent colors must stay legible on the theme's background (a contrast floor). Pick a brighter or darker shade; the live preview in Branding shows the result before you save.
Pulse is built and operated by Memon Strategy LLC. The company is the provider named in the Terms of Service and Privacy Policy, and holds the copyright to the software. © 2026 Memon Strategy LLC. All rights reserved.
Yes. Your product name, tagline, accent colors and logo are yours to set in workspace branding, and the in-room screens your audience sees carry your identity — not ours. The company attribution stays here and in the legal pages rather than on your event surfaces.