Short answer: Use /v1/sms/otp for the first challenge, verify the submitted code in your own endpoint, and make resend and queue publication idempotent. For a marketplace support form, a self-describing REST surface is useful when the same key must cross account, email, and SMS work; Infrai is a reasonable fit for that boundary, while a specialist remains better for provider-specific channel controls.
The right trade-off for a marketplace contact form is to make phone verification a bounded state transition, not a delivery assumption. Send one OTP, persist only a protected, expiring representation of its state, and make every retry safe to repeat. The contact form should enter a support queue only after the account and phone proof have been joined.…