Default order
Without an override, the route is VK → Telegram → email, followed by other enabled client channels.
Channels
VK, Telegram, and email are available now.
The default priority is VK → Telegram → email. After that, OTPilot can try other client channels that are enabled for the integration.
VK
Telegram
Email
Channel
Status
Delivery type
Default position
VK
Available
VK bot or connected messaging service
First
Telegram
Available
Telegram bot
Second
Email
Available
Connected email service
Third
Routing
A clear default with controlled overrides.
OTPilot starts with the default order and checks which routes are available. A user preference, an existing channel binding, or the client routing policy can override the order where configured.
User and binding
A preferred or previously linked channel can be tried first when the integration enables that behavior.
Client policy
The client can define which channels are enabled and adjust their order for a specific scenario.
Enrollment
A binding remembers the user’s channel.
The user can link VK or Telegram. OTPilot stores the binding and can use it in future verifications when the client policy allows it.
OfferThe API returns an enrollment link together with the verification result.
LinkThe user opens the VK or Telegram bot and confirms the connection.
ReuseA channel.enrolled event is emitted and the binding becomes available to future routing.
Configure the first live route.
Choose the enabled channels and agree where the default order needs an override for your scenario.