Every organisation in The GAiGE comes with a built-in pulse called The AI Pulse. It asks people about each tool they're assigned, on a cadence: in the browser extension, wherever they happen to be working, or in their AI Adoption Portal.
It's short on purpose. It branches on the first answer so people only see questions that apply to them: three or four questions, about thirty seconds.
For how the AI Pulse sits beside The AI Review and The AI Capability Check, see The three core pulses explained.
The questionsLink to this section
Did you use ChatGPT today?Link to this section
A yes or no question, and the branch point.
It feeds most of the figures elsewhere:
- Seats used on the Dashboard counts assigned seats where the person said yes
- Unused seats in Reports are assigned people who never said yes in the period
- The reasons a tool is going unused come from the people who said no (see below)
If they said yesLink to this section
Roughly how much time did ChatGPT save you today?
One choice from:
| Answer | Counted as |
|---|---|
| None | 0 minutes |
| Up to 30 mins today | 15 minutes |
| 30-60 mins today | 45 minutes |
| 1-2 hours today | 90 minutes |
| More than 2 hours | 150 minutes |
| I lost time because of it | −30 minutes |
This feeds hours saved, and on Pro the value of that time and ROI. The last option counts against the total, so a tool that costs people time shows up as costing people time.
How well did ChatGPT perform for your tasks today?
A slider from 1 (Useless) to 10 (Outstanding). It feeds the satisfaction figure.
Anything to add about ChatGPT today?
Optional free text. Most people skip it, and the ones who write often have something useful to say. Comments appear in Reports word for word, grouped into themes.
If they said noLink to this section
What's the main reason you didn't use ChatGPT today?
One choice from:
| Answer | What it suggests |
|---|---|
| I didn't need it today | Normal: not every day calls for the tool |
| I forgot it was available | Points to AI learning: what the tool is for, and when to reach for it |
| It was too slow or clunky | The tool may not suit the work |
| I didn't trust its output | Worth checking what it's used for, and how people check its output |
| I couldn't access it | A licence, sign-in or set-up problem to fix |
| I prefer a different tool | Ask which, and why |
Then the same optional comment.
For an agentLink to this section
An agent on your AI tools register, say one called Support Agent, is asked about its work: Did you work with Support Agent today?, How good was Support Agent's work today? and, after a no, What's the main reason you didn't work with Support Agent today?, without "I forgot it was available". The time question and every other answer are the same, so an agent's figures are worked out as every other tool's are.
For a tool you've marked Not approvedLink to this section
It is still asked about while it's on the register and people are assigned to it, because people may still be using it. Once you've briefed the team, a no goes straight to the comment, without the reasons. Until then its questions are the same as every tool's. A tool you've pointed at another entry, an alternative or the same tool on an organisation account, isn't asked about; the pulse asks the people assigned to that entry instead.
Editing the pulseLink to this section
The questions and the name are locked on every plan. Locked questions keep your own numbers comparable month to month and across your teams. On Pro, you can clone the AI Pulse and edit the copy, or build a new pulse with branching.
How often it's askedLink to this section
By default, each assigned person gets the AI Pulse three times a week per tool. Those times are spread across the week, at least 30 minutes apart, and held inside working hours (Monday to Friday, 9:30am to 4pm, unless your organisation sets its own window). Because it asks about today, it keeps to weekday afternoons.
Nobody has to visit the tool for a pulse to come due. That's how the "no" branch gets answered at all: someone who has stopped opening ChatGPT is exactly who you want telling you why. A pulse nobody gets to stays due until the end of its period (a week, by default), then drops off rather than queueing, so time away leaves a gap rather than a backlog.
You can change the cadence on Measurement → Standard pulses.
Something missing or out of date here? Tell us.