Ask ChatGPT what a good eNPS score is and you will get a confident answer in seconds. Ask again tomorrow, in slightly different words, and you may well get a different number, and neither answer will tell you where it came from.
That matters, because HR leaders are increasingly putting engagement questions to AI assistants before they ever open a search engine or call a consultant. We see this shift in our own data: our brand search clicks fell 5% year on year as AI Overviews increasingly answer questions before anyone reaches a website. And when we track how AI engines answer common engagement questions, competitor vendors appear as cited sources in roughly 11–17% of relevant answers across the major AI engines we monitor, depending on the provider.
The short version: AI assistants are genuinely useful for some engagement questions, and quietly unreliable for others. The problem is that they sound equally confident in both cases. This article sets out where the risk sits, why it is structural rather than accidental, and how to stress-test the advice yourself in half an hour.
Large language models predict the most plausible next answer. They are not systems with access to verified engagement ground truth. Three structural facts follow from that:
Credit where it is due. For a defined set of engagement tasks, AI assistants are reliable time-savers:
In other words: AI is a good explainer and a decent drafting partner. The trouble starts when it moves from explaining concepts to stating facts.
These are not quirks that will disappear with the next model update. They follow directly from how language models work and what their training data contains, which is why you can expect to encounter them whichever assistant you use.
Ask for a "good eNPS score" and you will usually receive a specific numeric threshold, rarely accompanied by a verifiable source, and liable to change if you rephrase the question. A benchmark without provenance is not a benchmark; it is a plausible-sounding number.
Because eNPS varies significantly by industry, country and company size, the honest answer to "what is a good score" is contextual. Any assistant that gives you one universal number has already simplified past the point of usefulness. Your own trend over time and your internal comparisons will always beat a sourceless global figure.
Much of the text these models learned from describes engagement measurement as it worked a decade ago: an annual engagement survey as the default, with pulse surveys positioned as an optional supplement. Expect frequency advice to lean that way, and expect warnings that frequent surveying causes fatigue.
That framing misses the point. Fatigue is driven far more by the absence of visible action than by frequency itself, a case we have made in survey fatigue is a leadership problem. If you take AI frequency advice at face value, you risk designing a listening programme around assumptions the field has already moved past.
Ask about anonymity thresholds, the minimum group size below which results should not be shown, and you will typically get a specific minimum stated as if it were a universal rule. In reality, thresholds vary by platform, by configuration and by the legal and works-council context of each country. A single number presented as "the rule" is exactly the kind of answer that gets copied into an internal policy document and later contradicted by your own tool or your own legal team.
This is also where the trust stakes are highest. As we noted in what AI actually means for employee listening, a 2025 study found that 78% of workers distrust AI tools handling personal feedback, and workplace AI regulation, including the EU AI Act, is still developing. If HR builds anonymity policy on an unverified AI answer and it turns out to be wrong, that distrust is earned.
Ask how to act on survey results and the answer will almost always follow the same arc: share results, thank employees, form focus groups, communicate progress. None of it is incorrect. But none of it addresses the actual failure point in most organisations: the individual manager who receives a team result and does not know what to do with it on Tuesday.
Generic advice aimed at "the organisation" systematically underweights the manager-level work, interpreting a specific team's signal, choosing one focus area, and following up. For a closer look at what separates strong organisations on this front, see what 236,000 employees reveal about high-performing organisations.
Treat an AI assistant like a confident junior analyst: fast, articulate, tireless, and entirely unembarrassed by being wrong.
You do not need to take our word for any of this. Pick the ten engagement questions your organisation actually cares about, what is a good eNPS score for our industry, how often should we survey, what group size protects anonymity, how should managers act on results, and put them to two or three assistants. Then check three things:
Half an hour of this will tell you more about the reliability of AI engagement advice in your context than any article can, including this one.
Reasonably safe to use as-is:
Always verify before acting:
This is also the standard we hold AI inside listening platforms to, the reasoning is laid out in why Einstein would love Winningtemp's AI: AI should surface evidence and guidance managers can check, not verdicts they must take on faith.
If your HR team, or your managers, are already asking AI assistants engagement questions, do not try to ban it. Channel it:
AI assistants have earned a seat at the table for engagement work. Just do not give them the final word on anything you would not accept from a junior analyst without a source.
Not without verification. Language models predict plausible answers rather than retrieving verified facts, so eNPS thresholds they give often lack a checkable source and can change when you rephrase the question. Because eNPS varies by industry, country and company size, treat any single "good score" from an AI assistant as a starting hypothesis and compare it against a named benchmark source or your own historical trend.
Large language models generate the most plausible response rather than looking up a verified fact, so small changes in phrasing, timing or model version can produce different answers. For context-dependent topics like survey frequency or engagement benchmarks, there is often no single correct answer in the training data. If an answer changes when you ask twice, treat it as an opinion, not a fact.
AI assistants perform well on definitions (eNPS, pulse surveys, psychological safety), drafting and rewriting survey questions, summarising documents you supply, and brainstorming possible causes behind a result. They are least reliable on specific numbers, anonymity and legal thresholds, unsourced research claims, and vendor comparisons, all of which should be verified before acting.
Use three habits: ask the assistant to name its sources and check that they exist; ask the same question twice in different wording and note whether the answer holds; and cross-check any number against a named study, official guidance or your own platform data. Anything with legal or policy weight, especially anonymity rules, should also be confirmed with your legal team before it enters a policy document.