BoldDesk

G2 cannot reset your Google SSO password. You need to restore access through your Google account first, then try signing in to G2 again with Google. If you want help checking whether your G2 account itself is otherwise in good standing, share the email tied to the account.

Yes. Your account is active and uses Google SSO, so after you restore access to your Google account, the right next step is to sign in to G2 again with Google using morgan.kim@example.com. If Google sign-in still fails after that, tell me what error you see and I can help with the next step.

Use the same Google account tied to morgan.kim@example.com and choose Google sign-in again on G2. If it fails, watch for whether the error is from Google account access, account selection, or a browser/session issue. If needed, retry in an incognito window or after signing out of other Google accounts, then try again.

You’re welcome.

Please share the category request ID, or your work email so I can check the current status, any blockers, and the expected timing.

The category request cat_001 is currently pending. It was submitted on 2026-06-29 for Help Desk, and the profile is currently in Customer Support. There is no recorded rejection or blocker, and nothing is showing as needed from your side right now. A decision date has not been set yet. If you want, I can also check the product details tied to this request.

While the request is pending, the next step sits with G2’s category review team. There is nothing indicated as required from your side right now unless the team reaches out for more detail.There is no confirmed decision date on the request, so I would communicate this internally as under review with timing not yet committed. Avoid promising a fixed turnaround until the review is completed.For Help Desk qualification, the review generally looks at whether the product’s core use case aligns with help desk workflows rather than broader adjacent functions alone. The team typically considers the product’s positioning, feature set, workflow fit, and how clearly the profile and supporting materials show that the product serves that category.Evidence considered in review can include the product description, visible profile content, website messaging, feature documentation, and other materials that help validate category fit.If the request is rejected, the category stays as is. At that point, the next step is usually to review the rejection details, compare the product against the category criteria, and provide stronger evidence if a follow-up or dispute path is available. If that happens, share the rejection details and I can help you assess the next best route.

You: I refreshed the request page and it still shows Pending, last updated June 29, with no new message. For internal tracking, I’ll communicate that G2’s category review team owns the next step and that there’s no committed decision date. Is there any status change or notification we should monitor for that would indicate you need additional evidence from us?

Your review was rejected because the reviewer’s employment could not be verified. Review ID: review_014 Status: rejected Rejected on: 2026-06-18 If you want to dispute the rejection, I can outline the support case I’d propose.

Rejected means the review will not be published, and no incentive is issued while it remains rejected. The decision is not reversed in chat, but it can still be formally disputed through a review moderation support case. Given the recorded reason, the proposed dispute case would state that review review_014 was rejected because employment could not be verified, and that you now have a verified LinkedIn profile and want moderation to re-check the review using that updated verification context. What happens next if you approve that case: support submits the dispute for manual review by the moderation team. I can’t promise the outcome, but they would reassess the rejection. I don’t have a confirmed SLA to quote here, so the safe expectation is to watch your email for updates after submission. If you want me to open that dispute case, reply with a clear confirmation like: yes, open the case for review_014.

There is no confirmed faster-track exception I can promise from here. The normal path is the formal moderation dispute case, where you note that LinkedIn is now verified and request a re-review. That updated verification detail is the strongest thing to include. If you still want to proceed, reply again confirming that you want the dispute case opened for review_014, and I’ll use that as the separate approval to submit it.

I couldn’t open the dispute yet because I still need your buyer account identifier. Please send the email address on your G2 account, and I’ll use it to submit the review moderation case for review_014.

Your dispute case is open. Case ID: case_rev_001_review_moderation Type: review moderation Status: open SLA: 3 business days Due date: 2026-07-02 The case asks moderation to re-review review_014 based on your now-verified LinkedIn. Watch your email for updates. While the case is under review, the rejection is not automatically reversed and publication is not guaranteed.

Yes. Watch your email for the decision update. From here, the case is with the internal review/moderation workflow for reassessment. Support cannot promise approval or speed it up further, but the moderation team will review the dispute and update you when they make a decision.