Nudging
Lixir actively chases votes so questions don't rot in your channel. All nudging settings are workspace-wide and configured from App Home → Nudging.
Reminder delivery
Controls how Lixir delivers automated pings to non-voters.
| Option | Behavior |
|---|---|
| In-channel (ephemeral) | Only the recipient sees the reminder in the channel where the question was posted. Quiet; no DM noise. This is the default. |
| Direct message | Reminders arrive as a DM from Lixir. Louder, harder to miss, but requires the im:write scope (granted at install). |
Switching delivery affects all future reminders; already-sent reminders are unchanged.
Deadline reminders
For questions with a deadline, Lixir pings non-voters at configurable offsets before the deadline fires.
- Defaults: 24 hours and 1 hour before deadline.
- Each non-voter receives at most one reminder per offset per question.
- Reminders are suppressed if the question has already resolved (e.g. because a unanimous approval came in first).
Deadline reminders require a deadline on the question and are only effective in decision modes that support deadlines (majority, quorum + majority, polls, or any mode where the asker opts into one).
Stale-question nudges
Optional. For deadline-less questions that have accumulated no activity, Lixir re-pings non-voters once a question has been open for the configured threshold.
| Setting | Effect |
|---|---|
| Off | No stale nudges sent. |
| 24 hours | Nudge non-voters when the question has been open for 24h with no resolution. |
| 48 hours | Same, at 48h. |
| 72 hours | Same, at 72h. |
Each question is nudged at most once; the timestamp of the last stale nudge is tracked per question to prevent duplicates.
Asker escalation
Optional. If a question has zero votes after the configured threshold, Lixir sends a DM to the asker with suggestions — ping approvers directly, add or extend a deadline, or defer to the next meeting.
| Setting | Effect |
|---|---|
| Off | No escalation DMs sent. |
| 24 / 48 / 72 hours | DM the asker once a question has zero votes at the given age. |
Asker escalation fires at most once per question regardless of delivery mode — it always uses a DM to the asker, since the point is to reach them privately with next-step suggestions.
How nudges interact with decision modes
| Mode | Deadline reminders | Stale nudges | Asker escalation |
|---|---|---|---|
| Any one can approve | If a deadline is set | If enabled and deadline-less | If enabled |
| All must approve | If a deadline is set | If enabled and deadline-less | If enabled |
| Majority / Quorum | Always (deadline required) | — (deadline always present) | If enabled |
| Poll (single / multi) | Always (deadline required) | — (deadline always present) | If enabled |
Privacy
All nudges are delivered via the Slack Web API using scopes granted at install (chat:write for ephemeral, im:write for DMs). Lixir does not store message bodies; reminders are generated on-the-fly from question metadata. No user-authored content is persisted server-side — see the Security page for the full data-minimisation posture.