A good check-in is specific, concise, and useful in practice.
For example, not useful:
Units per transaction was weak, so we pushed add-on suggestions.
That doesn't say enough about what actually happened in the store.
More useful:
Motion Joggers sold well, but mostly as single-item purchases. From Thursday, staff started also showing the Gray AirFlex Tee at fitting. One associate's approach worked especially well, so we shared it with the team at Saturday's morning meeting.
Concrete details make it easier to understand the situation later — for example:
"Motion Joggers, size M, down to 2 units by Saturday evening"
"Fitting room wait grew to 3 parties around 3pm"
"Moved the restocker to fitting room support"
You don't need exact numbers every time — add detail when it genuinely helps someone understand what happened.
Pulse isn't for repeating numbers that are already visible on the dashboard.
Not useful:
Conversion was lower than usual.
More useful:
Fitting room wait grew to 3 parties by 3pm on Saturday. We moved the restocker to fitting room support, which meant less coverage near the registers.
Ask yourself: "What can't be seen just from the numbers?" — that's what belongs in Pulse. Flow AI combines this with the actual numbers when it analyzes your report.
You don't need to repeat the same event across all three — each one has its own role.
The overall background or context for the week.
Strong weekend traffic, with a lot of interest in the new outerwear.
The most significant operational problem.
Fitting rooms were busy from 3-5pm on Saturday, and we were short one staff member, which thinned coverage on the floor.
Something the team handled well.
Paused restocking during the peak and moved a team member to fitting room support — kept wait times down while maintaining service.
Separating these out gives a fuller picture of the week than one combined note would.
Pulse isn't only for recording successes. If you tried something and it didn't get the result you expected, record that too.
Moved campaign items near the entrance from Friday. Slightly more people stopped to look, but no clear change in store entries. We'll try changing the mannequin next week.
Recording what didn't work helps avoid repeating the same approach, helps decide whether to try it in other stores, and helps Flow AI analyze the relationship between actions and results more accurately. What matters is recording what actually happened, not making the story sound better than it was.
The following are especially useful to include in a Pulse:
Products that sold well or poorly
Stockouts or low sizes
Changes to the entrance, tables, or mannequins
Fitting room congestion
Register wait times
Staffing shortages or scheduling issues
A strong example of customer service from a staff member
Training or coaching challenges
Campaign or promotion activity
Changes in customer behavior
Local events
Weather effects
Frequently asked questions about a specific product
Something the team tried
Something the team tried that didn't get the expected result
This kind of information can't be seen from sales or conversion numbers alone — which is exactly why it's worth recording in Pulse.
Check the following before submitting:
Have I written something the numbers alone don't show?
Have I included specific details (product, time, staff, store conditions) where useful?
Is my "biggest challenge" genuinely the most significant issue this week?
Does my "biggest win" reflect something the team actually did well?
If we tried something, did I record the result?
Am I stating an assumption as fact anywhere?
Have I noted anything unresolved that might continue into next week?
Would this make sense to someone who wasn't in the store?
A good Pulse doesn't need to be long. What matters is leaving information that's genuinely useful later.
Pulse quality depends on more than what you write in the check-in itself. Flow AI draws on other sources too.
Memos from the week are referenced in your AI insight and appear alongside your check-in in your manager's report. The more you record during the week, the more context Flow AI has to work with.
Documents added in Connections give Flow AI your company's actual policies and procedures to draw on, not just general knowledge. See "[New Flow] Getting the Most from Connections" for what's worth connecting.
Your company's public website is connected automatically as a knowledge source. You don't need to add it — keep in mind Flow AI may reference its public content.
New to Pulse? See "[New Flow] What is Pulse?" for an overview, or "[New Flow] How to Submit a Pulse Check-in" for the steps.
If you have any questions or feedback, please contact support at [email protected].
