| From | "Carlo Koh (EDU Support)" <support@alpha-school-support.kayako.com> |
|---|---|
| To | Alpha Billing <billing@alpha.school> |
| Cc | Cathrina Carmen <cathrina.carmen@trilogy.com> |
| Date | Thu, 24 Sep 2026 00:09:43 +0000 (UTC) |
| Subject | Re: Alpha Billing 2FA Code Authenticator Issue |
You are receiving this email because request [#60488180] [https://support.alpha.school/conversation/view/60488180] has received the below update: Dear Alpha Billing, Thank you for joining me in a quick call to address this problem. Feel free to reach out to us again if you encounter any further issues logging in to the Google account. Best regards, Carlo Koh EDU Support Team > On Thu, Sep 24, 2026 at 3:22 AM, Alpha Billing > <billing@alpha.school> wrote via Helpcenter: > > Any update? > >> On Thu, Sep 24, 2026 at 2:25 AM, Alpha Billing >> <billing@alpha.school> wrote via Helpcenter: >> >> Hi Logan, >> >> Same error. >> >>> On Thu, Sep 24, 2026 at 2:20 AM, Logan >>> <support@alpha-school-support.kayako.com> wrote via Mail: >>> >>> Hi Cathrina, >>> >>> Thanks for the screenshot. That confirms the prompt is Google's >>> own 2-Step Verification challenge for billing@alpha.school, >>> asking for a code from the Google Authenticator app. >>> >>> Your account itself is healthy. It is active, not suspended, and >>> it recorded a successful sign-in today at 3:55 PM CT, so your >>> password and the sign-in path are working. Only the >>> second-factor code is being rejected. >>> >>> Google Authenticator codes are time-based. When the clock on the >>> phone running Authenticator drifts even slightly, every code it >>> produces is rejected as "Wrong code", even though the app looks >>> normal. That is the most common cause when an authenticator that >>> worked before suddenly stops. >>> >>> Please try these steps on the phone that has Google >>> Authenticator: >>> >>> 1. Open the Google Authenticator app, tap the three-dot menu, >>> then Settings, then "Time correction for codes", then "Sync >>> now". Retry with a fresh code straight away. >>> 2. If your app does not show that option (Authenticator 7.0 and >>> newer removed it), open your phone settings instead and turn on >>> automatic date, time, and time zone. On Android: Settings > >>> System (or General Management) > Date & Time. On iPhone: >>> Settings > General > Date & Time > Set Automatically. Then retry >>> with a fresh code. >>> 3. Confirm you are reading the code from the >>> billing@alpha.school entry in Authenticator, not another >>> account, and enter it before the 30-second timer runs out. >>> >>> Please reply and let us know whether the code is accepted after >>> the time sync. If it is still rejected, tell us and we will >>> clear the existing 2-Step Verification enrolment on our side so >>> you can set up the authenticator again from scratch. >>> >>> Best regards, >>> EDU Support Team >>> >>> This ticket (#60488180 >>> [https://support.alpha.school/conversation/view/60488180]) will >>> stay open for one week unless you reply with "This ticket can be >>> closed" or update the status to Completed in the portal. We will >>> write to you again to remind you. >>> >>> ------------------------- >>> >>> This response was generated by AI. How we use AI: >>> aiterms.trilogy.com [https://aiterms.trilogy.com/] >>> >>>> On Thu, Sep 24, 2026 at 2:10 AM, Alpha Billing >>>> <billing@alpha.school> wrote via Helpcenter: >>>> >>>> Gmail sign-in. >>>> The error is wrong code. >>>> Previously, the authenticator is working fine. Then, I am >>>> getting the "wrong code" error when I tried to generate back >>>> up codes yesterday. >>>> >>>>> On Thu, Sep 24, 2026 at 2:05 AM, Logan >>>>> <support@alpha-school-support.kayako.com> wrote via Mail: >>>>> >>>>> Hi Cathrina, >>>>> >>>>> Thanks for reaching out. I checked the Alpha Billing account >>>>> (billing@alpha.school) in Google Workspace: >>>>> >>>>> - The account is active and not suspended. >>>>> - It recorded a successful sign-in today at 3:55 PM CT, just >>>>> before this ticket was created. >>>>> >>>>> To fix the right authenticator, I need one detail: >>>>> >>>>> 1. Which system is asking for the 2FA code? For example: >>>>> Google/Gmail sign-in, Amazon Business, a bank or payment >>>>> portal, or another app. >>>>> 2. What exactly happens when you enter the code? For >>>>> example: 'code is rejected', 'no code is generated', or 'no >>>>> prompt appears'. >>>>> >>>>> A screenshot of the error screen would also help. >>>>> >>>>> Once you confirm, I will take it from there. >>>>> >>>>> Best regards, >>>>> EDU Support Team >>>>> >>>>> This ticket (#60488180 >>>>> [https://support.alpha.school/conversation/view/60488180]) >>>>> will stay open for one week unless you reply with "This >>>>> ticket can be closed" or update the status to Completed in >>>>> the portal. We will write to you again to remind you. >>>>> >>>>> ------------------------- >>>>> >>>>> This response was generated by AI. How we use AI: >>>>> aiterms.trilogy.com [https://aiterms.trilogy.com/] >>>>> >>>>>> On Thu, Sep 24, 2026 at 1:58 AM, Alpha Billing >>>>>> <billing@alpha.school> wrote via Helpcenter: >>>>>> >>>>>> --- Ticket generated by Alpha Education AI chat on behalf >>>>>> of Cathrina SIS --- >>>>>> >>>>>> Issue description: >>>>>> >>>>>> * The 2FA code authenticator for Alpha Billing is not >>>>>> working. Please help to fix the issue. Sent with Kayako [https://kayako.com]
No attachments.
| Campus | not_campus_specific |
|---|---|
| Confidence | 100% |
| Display label | not_campus_specific |
Approximates the text state fed to the classifier
(subject, from, body, attachment filenames) — see
classify_locations_jev.py's build_state() for
the exact logic; PDF text extraction is not re-run here.
Subject: Re: Alpha Billing 2FA Code Authenticator Issue From: "Carlo Koh (EDU Support)" <support@alpha-school-support.kayako.com> Body: You are receiving this email because request [#60488180] [https://support.alpha.school/conversation/view/60488180] has received the below update: Dear Alpha Billing, Thank you for joining me in a quick call to address this problem. Feel free to reach out to us again if you encounter any further issues logging in to the Google account. Best regards, Carlo Koh EDU Support Team > On Thu, Sep 24, 2026 at 3:22 AM, Alpha Billing > <billing@alpha.school> wrote via Helpcenter: > > Any update? > >> On Thu, Sep 24, 2026 at 2:25 AM, Alpha Billing >> <billing@alpha.school> wrote via Helpcenter: >> >> Hi Logan, >> >> Same error. >> >>> On Thu, Sep 24, 2026 at 2:20 AM, Logan >>> <support@alpha-school-support.kayako.com> wrote via Mail: >>> >>> Hi Cathrina, >>> >>> Thanks for the screenshot. That confirms the prompt is Google's >>> own 2-Step Verification challenge for billing@alpha.school, >>> asking for a code from the Google Authenticator app. >>> >>> Your account itself is healthy. It is active, not suspended, and >>> it recorded a successful sign-in today at 3:55 PM CT, so your >>> password and the sign-in path are working. Only the >>> second-factor code is being rejected. >>> >>> Google Authenticator codes are time-based. When the clock on the >>> phone running Authenticator drifts even slightly, every code it >>> produces is rejected as "Wrong code", even though the app looks >>> normal. That is the most common cause when an authenticator that >>> worked before suddenly stops. >>> >>> Please try these steps on the phone that has Google >>> Authenticator: >>> >>> 1. Open the Google Authenticator app, tap the three-dot menu, >>> then Settings, then "Time correction for codes", then "Sync >>> now". Retry with a fresh code straight away. >>> 2. If your app does not show that option (Authenticator 7.0 and >>> newer removed it), open your phone settings instead and turn on >>> automatic date, time, and time zone. On Android: Settings > >>> System (or General Management) > Date & Time. On iPhone: >>> Settings > General > Date & Time > Set Automatically. Then retry >>> with a fresh code. >>> 3. Confirm you are reading the code from the >>> billing@alpha.school entry in Authenticator, not another >>> account, and enter it before the 30-second timer runs out. >>> >>> Please reply and let us know whether the code is accepted after >>> the time sync. If it is still rejected, tell us and we will >>> clear the existing 2-Step Verification enrolment on our side so >>> you can set up the authenticator again from scratch. >>> >>> Best regards, >>> EDU Support Team >>> >>> This ticket (#60488180 >>> [https://support.alpha.school/conversation/view/60488180]) will >>> stay open for one week unless you reply with "This ticket can be >>> closed" or update the status to Completed in the portal. We will >>> write to you again to remind you. >>> >>> ------------------------- >>> >>> This response was generated by AI. How we use AI: >>> aiterms.trilogy.com [https://aiterms.trilogy.com/] >>> >>>> On Thu, Sep 24, 2026 at 2:10 AM, Alpha Billing >>>> <billing@alpha.school> wrote via Helpcenter: >>>> >>>> Gmail sign-in. >>>> The error is wrong code. >>>> Previously, the authenticator is working fine. Then, I am >>>> getting the "wrong code" error when I tried to generate back >>>> up codes yesterday. >>>> >>>>> On Thu, Sep 24, 2026 at 2:05 AM, Logan >>>>> <support@alpha-school-support.kayako.com> wrote via Mail: >>>>> >>>>> Hi Cathrina, >>>>> >>>>> Thanks for reaching out. I checked the Alpha Billing account >>>>> (billing@alpha.school) in Google Workspace: >>>>> >>>>> - The account is active and not suspended. >>>>> - It recorded a successful sign-in today at 3:55 PM CT, just >>>>> before this ticket was created. >>>>> >