Gate support-queue admission on a short-lived, single-use SMS OTP, and keep the verification decision separate from the routing decision. For a custom Node.js service, the deciding constraint is whether you can explain why a contact-form submission entered a particular support queue, without treating a delivered text message as proof of identity or authorization.
TL;DR: Generate the OTP with Node.js crypto, store a temporary challenge with expiration metadata, send through an external SMS API, and validate against that challenge before admitting the submission. Bind the challenge to the form submission and the intended action. Record the policy that selected the queue. Phone possession alone does not establish account ownership, customer entitlement, or a lawful basis for processing personal data.
How should a custom Node.js OTP service secure support-queue admission?
Consider a developer-tools contact form whose submission, form-17 , requests access to an account-support queue.…