Beta

Confirmation Messages

A confirmation dialog informs a person about the consequences of an action to make sure that they want to complete it. For example, if the user is about to undertake a destructive action or an action that cannot be reversed, it is helpful to confirm that they want to proceed before completing it. Confirmation messages should pose a question to the user, explain the consequences, and provide options to reaffirm their decision or to back out.

Beta

Confirmation Messages

A confirmation dialog informs a person about the consequences of an action to make sure that they want to complete it. For example, if the user is about to undertake a destructive action or an action that cannot be reversed, it is helpful to confirm that they want to proceed before completing it. Confirmation messages should pose a question to the user, explain the consequences, and provide options to reaffirm their decision or to back out.

Beta

Confirmation Messages

A confirmation dialog informs a person about the consequences of an action to make sure that they want to complete it. For example, if the user is about to undertake a destructive action or an action that cannot be reversed, it is helpful to confirm that they want to proceed before completing it. Confirmation messages should pose a question to the user, explain the consequences, and provide options to reaffirm their decision or to back out.

Header

Header

Header

The header should state the main action that we want to confirm. It should take the form of a question. Keep it short and simple. Don’t include unnecessary introductions like “Are you sure…” or “Do you want to…”.

The question posed in the header should be specific and clear with only two unambiguous answers, like Yes and No or Continue and Go Back. Include a verb that describes the action the user just took, preferably the same verb as the button they just clicked.

Do

Do

Do

Delete campaign?

Exit without saving?

Don't

Don't

Don't

Confirm deletion

Do you want to leave?

Body

Body

Body

The body should describe the consequences of the action. Try to limit the explanation to one or two sentences. If there is a lot of information that cannot be condensed, use progressive disclosure (“See more”). Don’t use language that sounds intimidating or scary.

Don’t restate or rephrase the question from the header. The body text should elaborate so the user understands why the action requires confirmation. If there are alternative options, they can be included in the body.

Do

Do

Do

Delete campaign?

You cannot access or recover this campaign after deleting it.

Exit without saving?

All of your changes will be lost. You can also save a draft instead.

Don't

Don't

Don't

Delete campaign?

Are you sure you want to delete the campaign?

Exit without saving?

You’ll lose all of your changes. Are you sure you want to do that? You might regret it later.

Buttons

Buttons

Buttons

The buttons should present two distinct options. One option should be for continuing the action, and the other should be for cancelling. Limit the labels to two or three words maximum.

The button that confirms the action and continues the process should align with the language used in the header. Include a verb and a noun that specifies what is affected by the action.

The cancel action can be the generic “Cancel” but can also be more specific and contextual, like “Keep editing”.

Do

Do

Do

Delete campaign?

You cannot access or recover this campaign after deleting it.

Delete campaign / Cancel


Exit without saving?

Your changes will not be saved.

Exit without saving / Keep editing

Don't

Don't

Don't

Delete campaign?

You cannot access or recover this campaign after deleting it.

Yes / No


Exit without saving?

Your changes will not be saved.

I guess so / Nevermind

Need more guidance?

Suggest an addition or an edit.

Need more guidance?

Suggest an addition or an edit.

Need more guidance?

Suggest an addition or an edit.

© 2025 Basis Technologies
© 2025 Basis Technologies
© 2025 Basis Technologies