SOCS is classified as functional, which means its consent status depends on the exact feature and context in which it is used.

If it supports an optional service such as live chat, saved preferences, or personalised UX, prior consent is usually the safer position. If it is needed only after a clear user request, the necessity exemption may still apply.

Fix: document the feature, assess necessity with your privacy team, and delay the script until interaction or consent when the feature is optional.