Emails

Contents

– User needs
– How it works
– Status
– Accessibility statement
– Examples
– Research into this pattern
– Discuss this pattern

---

User needs

This pattern informs the user of a successful process; it is to reassure users that they have completed a transaction and helps them understand what to expect next.

How it works

The content should mirror the success page detailing key information for the user.

Emails must include:

• H1 stating the success of the action
• body text explaining the success

Emails could include:

• a reference number below the body text if the service requires it - ref number must be bold
• H2 of 'What happens next'
• a paragraph stating what happens next - this is bespoke to each form and Service

Content rules

General content rules for Emails: Axure mock-up - Email success mobile

Email subject line:

"We've received your... "

• application
• report
• claim
• booking
• request

Same as the H1 in the email

H1: in most cases, it would say:

"We've received your..."

• application
• report
• claim
• booking
• request

Body text 1 - examples:

• Thanks for applying...
• Thanks for letting us know...
• Thanks for reporting...

Your reference number is xxx

H2 - this is usually:

'What happens next'

Status

Working progress

Accessibility statement

This pattern has a rating of AA.

Please see our accessibility statement.

Improvements

To make it AAA, we need to:

• Add...

Examples

Axure mock-up - Email success desktop

Axure mock-up - Email success mobile

Axure mock-up - Email success page

Research into this pattern

For the development of this pattern, we looked closely at: GOV.UK Design System - Confirmation pages

Discuss this pattern