Q-Live Pulse

Pulse is the second mode of Q-Live (next to the classic Event). Instead of a live presentation for an in-room audience, it runs for weeks in the PMGclub feed — your network answers over time and you collect data for insight content, market research, or network sentiment.

Event vs Pulse — which when

Creating a Pulse

1. Tools → Q-Live → + New event in the lobby
2. In the dialog pick the Pulse type
3. Enter a name ("What does the PMG community think of PSD3?")
4. Set validity — date until which the Pulse is active
5. Create → host dashboard opens

Then add questions in the dashboard just like for an Event. For a feed Pulse, the best fits are:

• Multiple choice (2–4 short options)
• Rating (1–5 stars) — for sentiment / agreement / trust

Word cloud, open text, Q&A and quiz work but show only an "Open in full version" link in the embed — the carousel UX in the feed is too small for these types.

Publishing to the feed

After creating and adding at least 1 question, you'll see a Pulse panel in the dashboard:

🟢 Pulse — ready to publish Publish the Pulse to the feed — your network can see and answer it. [Publish to feed]

Click and a qlive_pulse post appears in the feed. Anyone scrolling your feed (or recommended) sees it. The embed auto-shows the first question, viewer responds with a click — no login screen, no code.

What the viewer sees

• Header with the Pulse name + step "Question 1 of 5"
• Question + answer buttons (MCQ) or stars (rating)
• After answer: instant aggregate — what % chose the same, their pick highlighted
• Next → moves to next question
• After last: thank-you state + button "Connect with {your name}" → opens your profile

If the viewer reopens the post, the Pulse jumps them to the first unanswered question automatically.

Your own view in the feed

In your own feed you don't see the response embed (you can't vote in your own Pulse). Instead you get a read-only "Your active Pulse" card with a button to the dashboard.

Real-time data in the dashboard

During the Pulse you see in the host dashboard:

• Response counts per question
• Distribution (which options lead)
• Average rating
• Total participants

Same data as Event mode — uses the same Q-Live analytics.

Closing the Pulse

When you have enough data, click Close Pulse in the dashboard. The feed embed freezes — viewers still see it but can't respond. Instead of question buttons it shows final results.

Publishing the summary

After closing you see the Publish results button. It creates a new post in the feed with the summary:

• Either you write it yourself ("The Pulse showed 73% of the PMG community sees PSD3 as a priority…")
• Or leave it empty and the server fills in an auto-summary with response count

This follow-up is a regular insight post — you can discuss it, recycle to LinkedIn, etc.

Recommendations

• Max 5 questions — the feed embed is capped (longer would overflow the UX). If you have 8 questions, the first 5 go to the embed, the rest is accessible via the "Open in full version" link.
• Short questions — the viewer is scrolling a feed, no time for 200 chars. Aim 8–15 words.
• Specific choices — MCQ with vague answers gives no insight. Instead of "A lot / Some / None" go "1–2× per week / 1× per month / Less".
• Sentiment via rating — "How strongly do you agree…" is more natural as a rating than MCQ.
• Regular Pulse = content — monthly Pulse + summary = a steady content stream backed by data.

Lifecycle

draft → live (published to feed) → closed (ended) → results published (optional)

Move between states with one click in the dashboard. No state is destructive — you can keep a closed Pulse as an archive forever, you never have to publish a summary.