Reading Time: 5 minutes

A Note Before You Read

This is an issue I’ve dealt with for a while, and I suspected others might be running into it too. So I decided to document it properly.

I started by working through the problem with the WordPress.com support chatbot, testing each suggestion along the way. Once I had those results, I ran the entire conversation through ChatGPT, Gemini, and Claude to cross-check the accuracy of the support responses, fill in any technical gaps, and help produce a clear, easy-to-read document.

The bottom line: the advice from the WordPress.com chatbot was accurate and did solve the problem. The AI models added useful context around some of the technical details and identified a few areas where the support responses were oversimplified or incomplete.

What you’ll find below is the result of that process — my testing, the support exchange, and how the AI analysis either confirmed or expanded on what the chatbot told me.

A breakdown of what support got right, what AI filled in — and what both missed

If you’ve ever clicked a blog post link from an email on your phone, typed a thoughtful comment, and then hit Submit — only to be bounced to a login screen, sent back to a blank form, and left wondering whether your comment even posted — you’re not alone.

This exact scenario played out in a recent WordPress.com support exchange, and running that conversation through an AI analysis revealed some instructive gaps in both the official response and the AI review. Here’s what happened, what was right, what was wrong, and what actually explains the problem.

The support conversation, annotated

The support exchange covered three rounds: the initial question, a follow-up about email links specifically, and a final question about session length. Here’s how each response held up.

Round 1 — What causes the login loop?

Question	Why does WordPress behave inconsistently when commenting from a phone? Sometimes it accepts the comment, sometimes it asks for login via Jetpack, and sometimes the comment appears twice.
WP Support	Attributed the problem to how login sessions and cookies work across different browsers and apps, and suggested the Jetpack app as the most reliable fix. → Partly right.
AI Review	Agreed that the session/cookie explanation is correct as far as it goes, but noted the Jetpack app recommendation is an unrealistic workflow. Also identified that expired tokens, in-app browsers, and third-party cookie restrictions could all be contributing factors that support skipped. → Accurate.

Round 2 — What about clicking from email?

Question	The original question clarified: the problem starts from an email notification link, not from a browser already open to WordPress.
WP Support	Identified that clicking an email link opens your phone’s default browser with no WordPress session — a good observation. Also suggested the Jetpack workaround of copying the URL and pasting it into the app. → Mostly right.
AI Review	Agreed on the core explanation, but correctly flagged that email apps often use their own in-app browser — meaning even if you’re logged into Chrome, the email link may open in Gmail’s or Outlook’s embedded browser, which has a completely separate cookie jar. This key distinction was missing from the support answer. → Adds important nuance.

Round 3 — How long does the session last?

Question	If I log into WordPress.com in my browser first, will that solve it — and how long will the session stay active?
WP Support	Confirmed the approach would work and stated that WordPress.com sessions typically last 14 days. → Oversimplified.
AI Review	Flagged the “14-day” claim as the biggest factual problem in the conversation. Session length actually depends on browser settings, cookie expiration, security policy, device behavior, and whether you clear browsing data. A flat number is misleading. → Correct to flag this.

AI scorecard — where the analysis landed

Accuracy: 7/10   ·   Logic: 8/10   ·   Completeness: 5/10

What support got right

• Sessions and cookies are the root cause of the login loop
• Logging in before clicking email links is good practical advice
• Duplicate comments happen because the first submission usually succeeded

What support got wrong

• The Jetpack app workaround is impractical for the email-to-comment workflow
• The “14-day session” is an oversimplification that can mislead users
• In-app email browsers weren’t mentioned — arguably the most important detail

What AI added correctly

• The in-app browser problem: Gmail, Outlook, etc., use their own sandboxed browsers
• Multiple possible causes — not just one explanation
• A more accurate framing of session length as a variable, not fixed

Where neither was complete

• Neither response suggested checking whether the comment actually posted before resubmitting — the most direct way to avoid duplicates

What’s actually happening — the real explanation

When you click a comment link in an email notification, here’s what your phone does behind the scenes:

1. Your email app receives the tap and decides which browser to open the link in.
2. If your email app (Gmail, Outlook, Apple Mail) has an in-app browser, it may open there — completely separate from Chrome or Safari, with its own cookie storage.
3. WordPress.com checks for a valid login session using cookies in that browser.
4. No cookie found → login prompt appears, often redirecting to Jetpack authentication.
5. After logging in, the browser may not return cleanly to the comment form, so you’re not sure whether Submit went through.
6. You resubmit. The first comment was already stored. WordPress sees a duplicate.

Why it feels random: Your phone likely has Chrome, Safari, your email app’s browser, and possibly others — all with separate login states. WordPress looks authenticated in one, like a stranger in another. The behavior changes based on which browser opens the link.

The fix that actually works

Before clicking any WordPress comment link from email: Open your preferred browser, visit wordpress.com, and log in. Leave that browser open. Then return to your email and click the link — if it opens in that same browser, you’ll be recognized and the loop disappears.

The catch is that email apps often ignore your default browser preference and open links in their own built-in browser. If that’s happening:

• Long-press the link in your email instead of tapping it.
• Choose “Open in Chrome” (or Safari, or your preferred browser).
• That browser should already have your WordPress session active.

As for how long the session lasts, the honest answer is that it depends. In practice, sessions often persist for days to weeks if you don’t clear cookies or force-quit the browser — but there’s no reliable fixed number. If you find yourself logged out unexpectedly, clearing your browser cache is often the culprit.

Takeaway

The WordPress support response gave reasonable advice for the most common case, but missed the in-app browser issue, which is often what’s actually causing the problem on phones. The AI analysis correctly caught the oversimplification of the “14-day” session claim and the impracticality of the Jetpack workaround, and identified the in-app browser distinction as the missing piece.

Neither response told you the most practical thing to do when you’re not sure whether a comment posted: open the post directly in a browser and scroll to the comments before resubmitting. That alone would prevent most duplicate comments.

If you’ve experienced this problem, you’re certainly not alone. Mobile commenting on WordPress can feel inconsistent, but knowing what’s happening behind the scenes makes it much easier to work around.

Conclusion

I did do the test the way WordPress.com suggested. I opened a browser and logged in. I then went to the mail and tested several scenarios without any issues. The suggestion worked, and in my opinion, that is the goal of their chatbot; it solved the problem. The greater detail is nice since it removes the ecosystem of WordPress and Jetpack and deals with the technical issues of the whole, but I would say for the support in WordPress with no human and a conversation-style back and forth, it did the job and answered my question.