Prompts

Prompts alert users to system-related issues and updates.

Note: If you’re a partner building an app that appears within Salesforce, don’t use this component.

Usage

• Visual: Pronounced
• Voice & Tone: (Varies per circumstance)
• Motion: Dramatic
• Duration: Permanent
• Audio: Loud

Prompts appear when the system needs to communicate a message to the user; it doesn’t show up as a result of user action. Prompts should appear rarely and generally should not be a part of a typical user flow.

Prompts do not have a close (×) button. To dismiss a prompt, the user needs to hit the action button inside of the prompt.

A prompt can show one of the following states:

• Error: when the system is running into a system issue that may prevent the user from moving forward properly.
• Informational: when the system needs to relay system-related information that isn’t necessarily work-stopping.

Prompt in Context

Dos and Don’ts

Do

• Do use prompts sparingly. They should not be your first choice to display system messaging because they interrupt the user and block everything else on the page.
• Do solicit user feedback in prompts when it makes sense. When an unexpected system error happens, for example, user feedback may be a good way to identify the issue.

Do Not

• Do not use prompts as a confirmation for user action, e.g. warning before user deletes an item. Use a standard modal instead for this.
• Do not stack multiple prompts.

Variants - Component

Variants - State

Variants - Screen Size

• Smaller title
• Full-width button

UI Text

UI text can vary greatly case to case, depending on the context. The guidelines below serve as examples, but you are not limited to them.

Recommended Specs

Refer to this code sample for the prompt markup.

Use the default prompt component specs plus the animation specs below.