BoldDesk

G2 can’t reset your Google SSO password. If you sign in with Google, you’ll need to recover access through your Google account first, then return and try signing in to G2 again. If you want, I can help you figure out whether this is a Google account issue or a G2 sign-in issue — are you trying to log in as a buyer/reviewer or as a vendor?

Yes — for a buyer/reviewer using Google sign-in, recovering your Google account is the right first step. G2 can’t reset a Google-managed password, so you’ll need to restore access with Google, then retry signing in to G2. If Google account recovery works but G2 still won’t let you in, tell me what happens when you try — for example whether you see an error message, get redirected back to sign-in, or land in the wrong account — and I’ll help you narrow down the next step.

Yes — when you retry G2 after recovering your Google account, watch for these specific behaviors:

• Make sure you choose the same Google email address that you previously used for G2.
• Check whether G2 signs you in successfully, loops you back to the login page, or shows a specific error message.
• Notice whether you land in the expected buyer/reviewer account or appear to enter a different account.
• If your browser has multiple Google sessions open, try selecting the intended account carefully or retry in an incognito/private window to avoid session mix-ups. If it still fails after Google recovery, send me the exact error or describe what the page does, and I can help you determine whether it looks like an account-access issue on G2’s side.

You can usually retry G2 as soon as your Google account recovery is complete and you’re able to sign in to Google successfully. There generally isn’t a required waiting period on the G2 side. If Google has just restored access and you still see odd behavior, it can help to refresh the session first by signing out of other Google accounts, opening a private/incognito window, and trying again right away. If it still loops or errors after that, send me the exact message or behavior and I’ll help you narrow it down.

I can check that, but I need one identifier first: what is the category request ID?

The category request is currently pending review, not blocked or waiting on evidence. I confirmed request cat_001 is still in a pending state for the product, with the requested category set to Help Desk and the current category still listed as Customer Support. For internal timing, I’d communicate that the request has been submitted and is awaiting category review, with no rejection or evidence hold recorded at this time. I can confirm it was submitted on 2026-06-29, but I can’t confirm a decision date yet from the current status. If you want, I can also help you draft a concise internal status note based on this update.

The next step is with G2’s category review team, since the request is already submitted and currently pending review. I can confirm the request is still pending and there is no rejection or evidence hold on it right now. I can share that it was submitted on 2026-06-29, but I can’t confirm a standard SLA or decision range from the current request data alone. While it’s pending, your team usually does not need to take additional action unless G2 requests clarification or supporting evidence. So the best internal update is: the request is in review, no blocker is currently recorded, and the team should monitor for follow-up rather than submit anything new. If you’d like, I can also help you word that as a short internal stakeholder update.

Thanks — that matches the current state. Category request cat_001 is pending, last updated 2026-06-29 12:00, and there is no latest message recorded. That means it is still with G2’s category review process, with no visible blocker, rejection, or evidence request at this time. The safest internal guidance is:

• Status: pending review
• Owner of next step: G2 category review team
• Current blocker: none visible
• Action for your team: no new action unless G2 requests more information
• Timing: no confirmed SLA is shown on the request, so communicate that it is under review and timing is still to be determined If you want, I can turn that into a one-paragraph internal update for your team.

I looked up review_014. It was rejected on 2026-06-18, and the recorded rejection reason is: Unable to verify reviewer employment. That means the moderation team could not confirm your employment details based on the information available with the submission. If you want, I can also explain what this usually means and the proper next step if you’d like to dispute it.

The proposed dispute case would be a review moderation case for review_014 stating that your review was rejected for unable to verify reviewer employment, and that you now have a verified LinkedIn profile you want moderation to consider as supporting evidence for a re-review. If I open it after your confirmation, the case would ask the team to manually review the rejection and reassess whether your employment can now be verified. This would not guarantee approval, but it would route your dispute for investigation. Would you like me to open that dispute case?

I couldn’t complete that because I don’t have a valid buyer account identifier tied to this conversation yet. To open the dispute case, please share the email address used for your G2 account. Once I have that, I can look up your account and create the review moderation dispute for review_014.

Your dispute case has been opened successfully. Case ID: case_rev_001_review_moderation Status: open SLA: 3 business days Due date: 2026-07-02 I requested a manual moderation review of review_014 based on your note that your LinkedIn is now verified. This does not guarantee the review will be approved, but the moderation team will reassess the rejection. Please watch your email for updates, and if you want, I can also summarize what to expect during the review process.

The current next step is the manual moderation review already opened for your dispute case, and the stated SLA is 3 business days. I can’t promise an earlier escalation or exception before that window. In most cases, the correct path is to wait for the moderation team’s review within the SLA rather than opening duplicate follow-up work. If the case goes past the 3-business-day SLA without an update, I can help check the status and advise on the next step.

Sounds good. Please watch your email for the moderation team’s update, and if there’s no progress after the 3-business-day SLA, come back and I’ll help you check the case status and next step.