Polls & Surveys

Polls are a single-question quick vote. Surveys are multi-question forms with optional templates (eNPS, pulse check, retro). Both are built on the same primitives as standups — same delivery channels, same question types, same analytics.

Polls

A poll is one question, zero ceremony. Create one in five seconds:

Polls → New poll.

  • Question text
  • Type (multiple choice, checkboxes, scale, yes/no)
  • Options
  • Audience (entire workspace, a team, a custom list)
  • Delivery channel
  • Anonymous? (yes/no)

Polls close automatically after 48 hours (configurable). Results are visible to the creator; optionally visible to respondents after they answer.

Useful for:

  • Lunch choices
  • Meeting time agreement
  • Quick gut-check on a design
  • "Does anyone else see this bug?"

Surveys

A survey is a multi-question form. Similar to standups, but:

  • Not recurring (unless you set a schedule).
  • Not divided into "per person every morning" — one survey, many respondents.
  • Supports a progress bar and section headers.

Use cases:

  • Pulse surveys (quarterly team health)
  • eNPS
  • Retrospectives
  • Post-mortems
  • Onboarding feedback

Survey templates

Pulse ships templates so you're not designing from scratch:

TemplateQuestionsRecurrence
eNPSThe standard "How likely are you to recommend us..." scale + optional comment.Quarterly.
Pulse5 questions on workload, clarity, team, growth, mood.Monthly or biweekly.
RetroWhat went well / didn't / try next sprint.End of sprint.
PostmortemTimeline, root cause, contributing factors, action items.One-off.
Onboarding check-in30/60/90 day questions for new hires.Triggered by start date.

Templates are starting points — customize questions, schedule, and delivery as needed.

Anonymous vs attributed

Per-survey toggle (also available per-question for surveys that mix sensitive and non-sensitive questions).

Anonymous:

  • Responses are stored without user_id.
  • Creator sees aggregated results only — no individual rows with identity.
  • Participation tracking still works (counts, rate), but no "who answered" list.

Attributed:

  • Responses store user_id.
  • Creator sees who said what.

Branching

Surveys support the same conditional follow-ups as standups. Useful for eNPS: only show the "what went well?" question if score ≥ 9, only show "what would you improve?" if score ≤ 6.

Delivery and reminders

Surveys are delivered through the same channels as standups. By default a survey pings:

  1. On launch.
  2. Once at the 48-hour mark if not answered.
  3. Once on the closing day if not answered.

Reminder cadence is per-survey configurable under Reminders.

Closing and results

Creator can close manually or leave it to auto-close.

Results views:

  • Summary — charts per question, response rate, NPS score if applicable.
  • Individual responses — attributed only.
  • Trend — for recurring surveys, week-over-week or month-over-month.
  • CSV export — raw data for anything richer.

Sharing results

  • Digest — auto-posted to a channel or DM when the survey closes.
  • Public link — optional, read-only link outside the workspace (admin toggle).
  • Embed in Ink — live survey results block, updates in real time.

Anonymity guarantees

Pulse takes anonymity seriously. For anonymous surveys:

  • user_id is never persisted on the response row.
  • IP address is never logged.
  • Admins cannot view individual rows — there are none.
  • Export formats drop any identity columns.

See the schema in Database Reference for the exact shape of responses.