The Pulses page
The Pulses page has a metrics strip at the top, then four tabs:Metrics cards
Shows at a glance: total pulses sent, response rate, active automations, and pending responses.History tab
Every pulse ever sent from your workspace — with status, send date, target audience, response breakdown, and a link to the full result. Use this to review what’s been sent and follow up on non-responders.Automation tab
The list of active pulse automations (automated workflows that send pulses on a trigger or schedule). Each automation shows its name, trigger condition, target, last run, and on/off toggle. This is where you set up recurring pulses — for example, “every month, send a check-in to anyone with an inactive account on any app with spend.”Templates tab
Pre-built pulse templates for common scenarios:- “Are you still using [App]?”
- “Your access to [App] will be removed soon. Do you need to export any data?”
- “We’re reviewing licenses for [App] ahead of our renewal. Do you still need access?”
- “Please confirm whether you still need your [App] account.”
Audit Log tab
A record of pulse activity, such as sends, responses, and cancellations.When to use pulses
- Before a renewal — verify who still needs the tool before you decide how many licenses to keep
- Inactive license cleanup — confirm that low-activity users genuinely don’t need access
- Shadow Apps review — ask employees whether they still need an app before IT decides on it
- Access review — periodic confirmation that people still need their existing access
- Offboarding — give a departing employee a chance to flag data export needs
How pulses work
1
Create a pulse
Choose a template or write your own question, then choose who receives it.
2
Choose delivery channel
Slack, Microsoft Teams, or email. Slack and Teams need their connection set up in Settings → Integrations. Employees respond with button clicks, so no typing is needed in Slack and Teams.
3
Set a response window
Choose how long people have to respond. Automations can follow up with people who haven’t responded.
4
Send or schedule
Send immediately or schedule for a specific date and time.
5
Review results
The History tab shows the response breakdown for each pulse.
Targeting
- App users — everyone with access to a specific app
- App owner — the person responsible for the app
- Manager — the recipient’s manager, where directory data provides it
- Admin — a workspace admin
- Via rule — a rule can send a pulse when its conditions match
Acting on responses
Review responses in the History tab and export them as CSV. Use the results to decide next steps, such as removing access in the app or running an offboarding playbook. Admins can cancel a pulse that hasn’t been answered yet.Snoozes and opt-outs
Employees can snooze a type of pulse for 7, 14, or 30 days, or opt out of a specific type of pulse. Future sends respect both.Next steps
Rules
Trigger pulses automatically on usage signals
Playbooks
Include pulses as offboarding workflow steps
Spend analytics
See the inactive/abandoned spend that pulses help you eliminate
Apps catalog
Act on pulse results to right-size licenses