This step happens **outside the web Platform**, inside your WhatsApp or Telegram app — the behavior is exact and verified against the system's code: 1. You open your WhatsApp or Telegram and write to your tenant's business number/bot (the same channel your customers write to). 2. You send **only the 6-digit code** your authenticator app shows at that moment — the same type of code you use to log in with two-factor verification (Manual 26, section 5), not a different code. 3. The system checks the code and replies **right in the chat**, within seconds: | Situation | Bot's reply | | --- | --- | | First link completed | "Account linked! From now on you can use this chat with your account. Session active for 30 minutes." | | Already linked, correct code (reopening a session) | "Session started. You'll have full access for 30 minutes from this chat." | | Incorrect or expired code | "Invalid or expired code. Generate a new one in your authenticator app and try again." | That same message with the code **both links AND opens your first session at once** — there's no separate confirmation step: as soon as the system validates the code, you can keep writing in that chat with your real role. Back on the web Platform, as soon as the linking is complete, your Profile's row changes from "Waiting for confirmation…" to showing the channel as **Linked**, with the date and a partial identifier (never your full number).