Knowledgebase

Designing Confirmation and Success States Print

  • uiuxdesign, guide, howto, solution, zillionkinghost, hosting, support
  • 0

After something is done.

WHY THEY MATTER

Doubt after an action causes repeat submissions and support requests.

WHAT TO CONFIRM

What happened What it means What happens next How to get help

WHAT TO INCLUDE FOR A TRANSACTION

A reference What was bought or submitted The amount The expected timescale Contact details

WHY THE REFERENCE

It is what people quote when something goes wrong.

WHAT TO SEND AS WELL

A message, so there is a record.

WHAT TO OFFER NEXT

A sensible following action.

Not a dead end.

WHAT TO AVOID

A bare confirmation with no detail Confirmation that disappears before being read Assuming the person remembers what they did

WHAT TO DESIGN FOR PARTIAL SUCCESS

Where some of an action worked and some did not.

State precisely which.

WHAT TO TEST

Whether the confirmation alone tells the person everything they need.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot