diff --git a/notes/remove_securex_tg_login_button.org b/notes/remove_securex_tg_login_button.org
index b7a0bef5..a1249031 100644
--- a/notes/remove_securex_tg_login_button.org
+++ b/notes/remove_securex_tg_login_button.org
@@ -104,7 +104,7 @@ So to resume
 1. Yes, we could take care of linking the TG account to SXSO account inside
    SecureX.
    Pros:
-   - will be perfectly secure (no risk of )
+   - will be perfectly secure (no risk of linking the wrong account)
    - no work to be done on TG side
    Cons:
    - probably lot of work on SecureX side (both backend and frontend) as a
@@ -113,3 +113,10 @@ So to resume
    - we still need to propose a login via TG for a long period of time
    - we will probably force an ultimatum on customer that might open many
      TAC cases.
+2. We could try to use the email (even if they are not verified by TG)
+   Pros:
+   - Limited work to be done on SecureX side
+   - no work to be done on TG side
+   Cons:
+   - open some security concern that will need to be evaluated
+   - UX should be evaluated, we don't want end user to be even more confused.