Social Rocket
X is introducing liveness checks for suspicious accounts. If a profile is flagged for unusual or apparently automated activity, the platform can require a brief verification: either via device biometrics or a selfie video. The measure is meant to curb spam and platform manipulation. It is not a general ID requirement for all X users and, according to the official X Help Center, it cannot be booked voluntarily either.
What X checks – and what it doesn't
These methods first answer the question of whether a human is at the device. With Face ID, Touch ID or Android's biometric unlock, the actual biometric check stays on the device. According to X, it only receives the result and a signal about the integrity of the official app.
Alternatively, a short selfie video can be requested via the front camera. According to X, an automated third-party system analyses the video for liveness; X receives a confidence score, not the video file. A hand-movement check has been announced but is explicitly not yet generally available. Which option appears depends on device, app version and region.
The distinction matters: a passed liveness check is not proof of identity, not a paid premium verification, and says nothing about whether all of the account's posts are authentic.
Who may be affected and which functions are paused
X describes two triggers: registration and a later flag due to suspicious activity. Until the required check is passed, affected accounts cannot, according to X, post, follow other profiles or send direct messages. Reading remains generally possible. After a successful check, full access should normally return immediately.
The feature runs in the official X app, not as a freely accessible web verification. X explicitly states that it does not send verification links by email, SMS or DM. Such messages are therefore a phishing warning sign. The X Help page also explains error cases and support channels.
What this means for social media teams
For brands and agencies, the key issue is less the facial recognition itself than the operational disruption. Teams that run campaigns, customer service or event communication through a few X accounts should set up an emergency process for restricted access: document responsibilities, ensure app access, and don't tie approvals for time-critical posts to a single person.
Also, a single account lock should not automatically be taken to mean that a publishing tool in use is impermissible. X does not publish a complete list of triggers, nor reliable figures on false positives or the effectiveness of the new checks. The coverage from October 8 by Social Media Today describes the step as part of X's broader anti-bot measures.
For automation via approved interfaces, teams should continue to observe platform rules and the relevant API terms. Our comparison of social media automation tools covers the differences between permitted publishing, artificial interactions and risky automation patterns. In parallel, X is trying to structure controlled AI activity through Grok bot templates and API credits for Grok bots. These programmes must be distinguished from the new liveness check.
What has not yet been verified
X has not publicly quantified how many genuine accounts are wrongly flagged, in which countries the feature has been rolled out and to what extent, or whether the checks have already measurably reduced the volume of scam activity. For advertisers, it therefore remains unclear whether the change will improve the quality of engagement metrics in the short term.
Conclusion: The new check adds a hurdle for suspicious accounts on top of the technical anti-spam defences. Social teams should organisationally safeguard against possible account lockouts – and never send users to external "X verification links". Image note: The article image shows a general selfie situation, not an actual X verification dialogue.