Pulse helps you stay on top of your team's performance by automatically delivering the insights that matter most. Set up recurring reports, choose which metrics to include, define the schedule, and receive them by email and/or Slack.
This guide is for administrators and team leads who configure periodic deliveries. No technical knowledge is required!
π What does Pulse do?
Pulse generates automatic summaries with quality data, AI process metrics, topics, and coaching recommendations. Each configuration you create is called a pulse (or recurring report).
Every pulse:
Runs on the schedule you define (daily, weekly, or monthly).
Analyzes a lookback period (data window in days).
Is delivered to the people and channels you choose.
Cannot be downloaded from the app β content is only sent through the configured channels.
Who can use Pulse?
Pulse appears in the sidebar for users with administration permissions for the module. If you do not see Pulse or cannot create reports, contact your organization administrator.
In the app: Pulse β list at /admin/pulse
π Main screen (list)
The list shows all pulses in your company. For each one you can review:
Column | Meaning |
Report | Pulse name and number of content sections. |
Schedule | Frequency, days, and send time. |
Delivery | Number of email recipients and Slack channels. |
Last run | When it was last generated and delivered. |
Next run | When the next send is scheduled. |
Status | Active (sends on schedule) or inactive (paused). |
Created by | User who configured the pulse. |
From here you can search by name, edit, enable/disable, run now, or delete (depending on your permissions).
βοΈ Create a pulse (4 steps)
Click New pulse to open a four-step wizard. Move between steps with Back / Next or by clicking the step indicator at the top.
Step 1 β Basics
Report name: Use a name your team will recognize in email or Slack (e.g. Weekly quality recap β CS).
Status: When the switch is on, the pulse sends on schedule. When off, settings are kept but nothing is sent until you turn it back on.
Step 2 β Content
Define what each delivery includes. A pulse is made of one or more sections. Each section is a block of metrics or analysis.
Working with sections:
Click Add section and choose a type.
Configure that sectionβs options (scorecard, process, thresholds, etc.).
You can add the same section type more than once with different options (e.g. two different scorecards).
Reorder sections by dragging them.
Expand or collapse blocks for easier editing.
Common section types (may vary by workspace):
Type | Purpose |
Quality Overview | Headline quality metrics: evaluations, average score, errors, signed/disputed totals. |
Quality Sections | Breakdown by scorecard section. |
AI Process | AI process coverage and results. |
AI Metrics | AI KPIs (By agent, team, channel, etc) |
Topic analysis | Topic detection and sentiment for the period. |
Each type shows a description when you add it to help you choose. Some options use toggles (yes/no), dropdowns, or multi-select depending on the block.
Important: You must add at least one section. You cannot save two identical sections (same type and same options).
Step 3 β Schedule
Define when the pulse is generated and sent and which data window is analyzed.
Field | Description |
Frequency | Daily, weekly, or monthly. |
Days of the week | Weekly only (you can select multiple). |
Day of the month | Monthly only. In shorter months, the last available day is used. |
Time | 24-hour format (HH:MM) in the selected time zone. |
Time zone | Reference for send time. |
Data window | How many days back each run covers (maximum 30 days). Common presets: 7, 15, or 30 days. |
Example: Weekly on Mondays at 09:00 (America/Bogota), 7-day window β every Monday a summary of the previous week is sent.
After saving or changing the schedule, next run may take about a minute to recalculate and appear in the list.
Step 4 β Delivery
Choose how your team receives the finished pulse.
Select one or more company users as recipients.
Only valid addresses for registered users are sent.
Recipients receive the report in their inbox.
Email Example:
Slack
Requires Slack connected under Integrations.
You can choose public or private channels.
You can add multiple channels at once.
If Slack is not connected, you will see a notice with a link to Integrations.
You can use email only, Slack only, or both. Configure at least one delivery channel for the pulse to be useful in practice.
Edit an existing pulse
Open the pulse from the list.
Review the top panel for last run, next run, and created by.
Change any wizard step.
Save.
Changes to content, schedule, or recipients apply to future runs (and to Run now if you use it).
Run now
Run now generates and delivers the pulse immediately, without waiting for the next scheduled run.
The confirmation dialog shows how many email recipients and Slack channels will receive it.
Generation may take a few seconds. You will see the result in your email and/or Slack β you do not need to stay on the screen.
If a run is in progress, the button stays disabled until it finishes.
Enable, pause, and delete
Action | Effect |
Disable (inactive status) | Keeps configuration; stops automatic sends. |
Enable again | Resumes scheduled sends. If the last run failed, enabling again may clear the error notice. |
Delete | Removes the pulse from the list. This cannot be undone from the UI. |
Run states
State | Meaning |
Never run | No delivery has been generated yet. |
Running | The report is being generated now. |
Delivered | The last run completed successfully. |
Failed | The last run encountered an error. Check the message on the pulse detail page β it usually points to a configuration or delivery issue. |
β Frequently asked questions
Can I download a pulse from the app?
No. Pulse is designed to deliver content by email and/or Slack. There is no downloadable file in the interface.
Can I repeat the same section type?
Yes, as long as the options differ (e.g. two Quality Overview blocks for different scorecards).
What happens if I change the schedule?
The system recalculates next run. You may briefly see βBeing scheduledβ¦β until it updates.
Why donβt I see Slack channels?
Connect the Slack integration under Integrations β Gallery. If it is already connected and loading still fails, use Retry on the delivery step.
Can an inactive user receive a pulse?
Recipients must be valid company users. If someone is no longer active, review and update the recipient list.
How many days of data can I include?
Up to 30 days per run. For longer trends, create pulses with different windows or use Analytics dashboards.
π‘ Best practices
Name with context: Include team, frequency, or audience (βPulse QA β Monday β CS leadsβ).
Start simple: One or two well-chosen sections are often more useful than a very long report.
Align window and frequency: A weekly pulse with a 7-day window is coherent; a daily one often uses 1β3 days.
Test with Run now before relying only on the schedule.
Review recipients when someone changes role or leaves the team.
Use Slack for team visibility and email for owners who need the summary in their inbox.
π Quick summary
Pulse = name + content sections + schedule + recipients
β
Runs automatically (or via "Run now")
β
Arrives by email and/or Slack
For additional help, contact your Oversai administrator or technical support!