Skip to content

Update the ‘Confirm your service is unique’ guidance#5967

Open
karlchillmaid wants to merge 4 commits into
mainfrom
update-confirm-service-is-unique-guidance
Open

Update the ‘Confirm your service is unique’ guidance#5967
karlchillmaid wants to merge 4 commits into
mainfrom
update-confirm-service-is-unique-guidance

Conversation

@karlchillmaid

@karlchillmaid karlchillmaid commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

One of the mandatory tasks we make users complete before they go live is ‘Confirm your service is unique’.

We introduced this page as part of the ‘onboarding’ epic. It was good enough for MVP, but now it needs to change.

It’s biggest weaknesses are:

  • the concept of a ‘unique service’ is abstract
  • we don’t explain why we want your service to be ‘unique’ (the free allowance)
  • there’s a disconnect between the title/h2 and the interaction (text field, green button)

The new page design:

  • makes a stronger connection between the title/h1 and the interaction
  • explains that this is all about the free allowance

It’s not perfect, but it’s a reasonable first step and sets us up well for the work we’ll do in Q2.

This PR also changes the link on the ‘Make your service live’ task list page, so it matches the new h1.

Explain that this is important because of the free text message allowance.
Comment thread app/templates/views/confirm-your-service-is-unique.html Outdated
@karlchillmaid karlchillmaid marked this pull request as ready for review June 17, 2026 13:31
Comment thread app/templates/views/confirm-your-service-is-unique.html
Comment thread app/templates/views/confirm-your-service-is-unique.html

@saimaghafoor saimaghafoor left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reviewed - comment on service being one of its kind

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants