Allowed channels
Per-request and per-client constraints keep routing inside the product policy.
Channels
Use the right OTP channel for every user.
OTPilot treats SMS as the reliable fallback, not the default business model. Routing can prefer MAX, VK, Telegram or Email when policy and enrollment allow it.
Channel
Best use
Routing note
MAX
RU-focused flows where domestic messenger delivery is preferred.
Good candidate for enrolled repeat users and regulated routing policies.
VK
Domestic social/messenger identity reach and fallback from MAX.
Useful when Telegram is not allowed for a segment.
Telegram
SMB and international flows where Telegram Gateway is permitted.
Policy filter decides whether this channel is allowed.
Email
Low-risk checks, account confirmation and secondary recovery.
Cheap and useful, but not always enough for phone ownership.
SMS
Universal last-mile fallback when other channels cannot be used.
Protects conversion but should be measured by cost per approved.
Policy before optimization.
Cheap delivery is not enough. OTPilot first checks country, client segment and allowed channel rules, then optimizes price and fallback.
Preferred binding
Returning users can use their enrolled channel before SMS is considered.
Provider fallback
Failed attempts are visible and the next route can continue without rebuilding client code.
Lower SMS share without risking conversion.
Start with conservative fallback, then move repeat users toward lower-cost channels as enrollment grows.