Page MenuHomePhabricator

Improve verification email - copy changes to consider prior to full release
Closed, DeclinedPublic

Description

User Story

Primary user story:
As a newly registered account holder, I want to receive a clear and welcoming verification email from my home wiki so that I understand the benefits of confirming my email and feel confident in taking the next step.

Edge case user story:
As someone who received a verification email but did not register for a wiki account, I want the message to clearly explain how to disassociate my email address from the account so I can easily remove my email from the account.

Designs:

We've received feedback in T396155: [Epic] Improve verification email (WE1.1.22 FY2025-26) and on enwiki with suggestions for improved copy.

This task is meant to implement any copy changes that are agreed on:

Original copy & design (as released in current experiment):

image.png (1×750 px, 126 KB)

Proposed copy & design:

image.png (1×750 px, 131 KB)


Details:

We have intentionally kept this email short and focused, including the text on the call to action button.

This approach is based on two considerations:

  1. First, verification emails are often scanned quickly rather than read in full. Clear and concise language helps users immediately understand the purpose of the message and the next step they are being asked to take.
  2. Second, the copy and button design were informed by a comparative review of confirmation emails used by many other platforms. Users develop expectations based on their experiences elsewhere, and aligning with familiar patterns reduces cognitive effort and increases confidence in taking action.

For this reason, we did not simply revise the original email text:

Screenshot 2025-12-18 at 12.59.48 PM.png (1×778 px, 372 KB)

Instead, we aimed to align the structure, tone, and brevity of the message with common verification email conventions, while still clearly explaining the benefits of confirming an email address and providing a straightforward path to disassociate an email in error cases.

"Confirm your email address" was not a common call to action, generally this is shorted to "Confirm your email" or simply "Confirm email" or "Verify email":

Screenshot 2025-12-18 at 1.06.49 PM.png (140×596 px, 32 KB)

Screenshot 2025-12-18 at 1.06.03 PM.png (128×256 px, 21 KB)

Screenshot 2025-12-18 at 1.04.13 PM.png (130×462 px, 25 KB)

Screenshot 2025-12-18 at 1.04.31 PM.png (112×572 px, 14 KB)

Screenshot 2025-12-18 at 1.05.04 PM.png (146×472 px, 35 KB)

Screenshot 2025-12-18 at 1.05.13 PM.png (112×562 px, 29 KB)

Screenshot 2025-12-18 at 1.05.35 PM.png (144×290 px, 25 KB)

Screenshot 2025-12-18 at 1.04.51 PM.png (128×364 px, 33 KB)

Screenshot 2025-12-18 at 1.04.40 PM.png (142×628 px, 33 KB)

Acceptance Criteria:

Implement copy changes after the initial experiment is complete (T400843) and consensus is reached.

Event Timeline

Hi @Jonesey95 & @GhostInTheMachine, I'm moving our conversation to this new task, since T396155 is resolved.

The button should also say "Confirm your email address".
It makes no sense to confirm an email.

@GhostInTheMachine I understand that this may be technically accurate, but this phrasing is widely used for this type of email and is therefore familiar to most users.

I added additional context in the task description. The proposed language is based on a thorough review of verification emails across a range of platforms and websites.

I am happy to discuss alternative copy options if helpful. However, I strongly believe we should align with established language and conventions that users already recognize from other websites.