> ## Documentation Index
> Fetch the complete documentation index at: https://content-designer-ux-writing-skill-26.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Writing success messages

> Create clear, encouraging success messages that confirm completed actions

Success messages confirm that an action completed successfully. They reassure users and provide positive feedback at key moments.

## The pattern

```
[Action] [result/benefit]
```

Success messages should:

* Confirm what happened
* Be brief and specific
* Use past tense
* Match the importance of the action

## Examples

<CardGroup cols={2}>
  <Card title="Good examples" icon="check" color="#16A34A">
    * Changes saved
    * Email sent
    * Profile updated
    * File uploaded
    * Password changed
  </Card>

  <Card title="Avoid" icon="xmark" color="#DC2626">
    * Success!
    * Done
    * OK
    * Operation completed
    * Your request was processed
  </Card>
</CardGroup>

## Format guidelines

### Use past tense

Confirm the action is complete:

* **Good**: "Password changed"
* **Avoid**: "Changing password" or "Password has been changed"

### Be specific

Tell users exactly what happened:

* **Good**: "Profile photo updated"
* **Avoid**: "Update successful"

### Keep it concise

Success messages should be brief (2-5 words ideal):

* **Good**: "Message sent"
* **Avoid**: "Your message has been successfully sent to the recipient"

### Match the stakes

Scale your language to the importance of the action:

<Tabs>
  <Tab title="Low stakes">
    **Simple, brief confirmations**

    * "Saved"
    * "Updated"
    * "Theme changed"
    * "Settings saved"

    For routine actions users perform frequently, keep it minimal.
  </Tab>

  <Tab title="Medium stakes">
    **Clear, specific confirmations**

    * "Email sent to 12 contacts"
    * "Report exported to CSV"
    * "Team member invited"
    * "Payment method added"

    For important but reversible actions, provide specific details.
  </Tab>

  <Tab title="High stakes">
    **Detailed, celebratory confirmations**

    * "Account created! Check your email to get started."
    * "Subscription activated. You now have access to all features."
    * "Project published. View your live site."

    For major milestones, add next steps or celebrate the achievement.
  </Tab>
</Tabs>

## Tone by context

### Routine actions

For frequent, low-stakes actions, be efficient:

* "Saved"
* "Updated"
* "Deleted"

### First-time actions

For users completing something for the first time, be encouraging:

* "First project created! Add your team to get started."
* "Profile complete. You're all set."

### Milestones

For significant achievements, celebrate proportionally:

* "100 tasks completed! You're on a roll."
* "Account upgraded. Welcome to Pro."

<Note>
  Don't overdo celebration for routine actions. "Amazing! You changed your theme!" feels excessive.
</Note>

## Adding value to confirmations

Sometimes success messages can do more than just confirm:

### Include next steps

<Accordion title="Example: File uploaded">
  Instead of: "File uploaded"

  Consider: "File uploaded. Share the link or keep editing."

  This guides users to logical next actions.
</Accordion>

### Show results

<Accordion title="Example: Bulk action">
  Instead of: "Users imported"

  Consider: "24 users imported successfully"

  Quantifying results helps users verify the action worked as expected.
</Accordion>

### Provide context

<Accordion title="Example: Scheduled action">
  Instead of: "Post scheduled"

  Consider: "Post scheduled for March 15 at 9am"

  Adding context reassures users the action is set up correctly.
</Accordion>

## Timing and placement

<Steps>
  <Step title="Show immediately">
    Display success messages right after the action completes. Don't make users wonder if it worked.
  </Step>

  <Step title="Make them visible">
    Use clear visual indicators (checkmark icon, green accent) but don't rely on color alone.
  </Step>

  <Step title="Auto-dismiss for routine actions">
    Simple confirmations ("Saved") can fade after 2-3 seconds.
  </Step>

  <Step title="Require dismissal for important actions">
    Major confirmations ("Account created") should stay until user acknowledges.
  </Step>
</Steps>

## Before and after examples

### Example 1: Form submission

| Before                                      | After                                             | Why it's better               |
| ------------------------------------------- | ------------------------------------------------- | ----------------------------- |
| "Success!"                                  | "Application submitted"                           | Specific about what succeeded |
| "Your form has been successfully submitted" | "Application submitted. We'll respond in 2 days." | Concise + sets expectation    |

### Example 2: Settings change

| Before                             | After                         | Why it's better            |
| ---------------------------------- | ----------------------------- | -------------------------- |
| "Operation completed successfully" | "Notifications enabled"       | Specific action confirmed  |
| "Done"                             | "Email notifications enabled" | Clarity about what changed |

### Example 3: File operation

| Before              | After                           | Why it's better    |
| ------------------- | ------------------------------- | ------------------ |
| "File saved"        | "Report.pdf saved to Downloads" | Location included  |
| "Upload successful" | "3 images uploaded"             | Quantity confirmed |

## Accessibility

<Check>Use checkmark or success icon alongside text</Check>
<Check>Ensure sufficient color contrast (4.5:1 minimum)</Check>
<Check>Don't rely on color alone to indicate success</Check>
<Check>Make success messages programmatically identifiable for screen readers</Check>

## Quick reference

**Format**: Past tense + specific action

**Length**: 2-5 words for simple actions, up to 10 for complex/important actions

**Tone**: Proportional to action importance (minimal → encouraging → celebratory)

**Timing**: Immediate display, auto-dismiss routine actions

## Related resources

<CardGroup cols={3}>
  <Card title="Error messages" icon="triangle-exclamation" href="/guides/error-messages">
    Learn to write helpful error messages
  </Card>

  <Card title="Voice and tone" icon="comments" href="/concepts/voice-and-tone">
    Match success messages to your brand
  </Card>

  <Card title="Quality standards" icon="star" href="/concepts/quality-standards">
    Apply the four quality standards
  </Card>
</CardGroup>