Drift detection
Drift detection is the practice of noticing when a product's interface has changed away from what a system believed about it. In customer support tooling it means scoring how confidently an element was found on each use, flagging routes whose scores fall, and re-reading those routes before a user hits the broken path.
How is drift detected?
By measurement, not by polling. Each time an element is located, the match produces a confidence score. A score that falls from 0.94 to 0.41 is the signal: the route is flagged, re-captured on the next session that visits it, and diffed against the stored map. A rename merges automatically; a restructure waits for human confirmation.
Why can't a chat widget do this?
Because it never touches the interface. A widget that reads your help center can only detect that the help center changed, which is the document that was already wrong. Drift detection requires a system that observes the live product, so the ability to detect drift and the ability to act inside the UI are the same capability.