UX Writing for SaaS: Microcopy that Clarifies and Converts

Kun Yang-Tolkachev
UX Designer
Read Time
5 min read
Published On
June 12, 2025

Microcopy, those concise snippets of text like button labels, error messages, or tooltips, is the unsung hero of SaaS platforms. Seamlessly woven into user interfaces, microcopy guides, reassures, and empowers users, transforming complex interactions into intuitive experiences. When crafted thoughtfully, it aligns with a brand’s voice, eliminates confusion, and drives conversions by making every click feel effortless.

In SaaS platforms, users need to make critical decisions, manage complex datasets, and often complete high-stakes tasks. Clear and unambiguous guiding content can make them feel confident in the actions they take. This post focuses on how UX microcopy can greatly enable an experience with actions, tooltips, and toast messages. Let us walk through examples and best practices for each of these.

1. Actions

When users are about to take an action—especially an irreversible one—microcopy plays a critical role in guiding decision making and preventing errors.

A modal, a window that appears on top of a page section or underlying content, is a prime location for microcopy to reinforce clarity. Best practices for modal microcopy involve confirming the action, clarifying the outcome, or offering an escape hatch.

Example

Title: “Are you sure you want to delete this report?”

Body: “This action is permanent and cannot be undone.”

Buttons: Cancel | Delete report

Tip

Use modifiers like “permanently,” “from this team,” or “revoke access” to clarify scope and consequences.

Bonus Tip

Remove User or Delete User—Which one to use?

There’s a big difference between removing a user from a project and deleting their account entirely. Your microcopy must reflect that distinction.

  • Remove from project (non-permanent)
  • Permanently delete user and data (destructive)

2. Reverse actions

Action labels like “Cancel,” “Back,” “Discard changes,” and “Undo” may seem interchangeable, but they serve distinct purposes. Using the incorrect term can confuse users, interrupt task flow, or even cause accidental data loss. Here is examples of the usage.

  • Cancel
    • Used to exit a process or multi-step action entirely, reverting to the state before the process began. For example, canceling a purchase or canceling the creation of a new account.
    • A "Cancel" button is essential in modal dialogs to allow users to dismiss the dialog and return to the main application without making any changes.
  • Discard Changes
    • Specifically used to revert changes made on the current screen, without navigating to a previous screen. It is often used in conjunction with "Save" or "Apply" buttons.
    • For example, if a user has edited a document and then decides not to save the changes, they can use "discard changes" to revert to the original state.
  • Back
    • Navigates the user to the previous screen or page.
    • Often used in a navigation context, like returning from a detail page to a list view or from a settings page to the main menu.
  • Undo
    • Used to provide users with control and freedom to experiment without fear of making irreversible changes. It allows users to revert specific actions, like deleting text, changing a setting, or modifying a document.

Tip

Use “Cancel” to exit a flow, “Back” to navigate, “Discard changes” to revert edits, and “Undo” to reverse a specific action—each label should match the user's mental model to avoid accidental loss.

3. Tooltips

A tooltip is a small, interactive UI element that appears when a user hovers over, clicks, or focuses on a specific part of a user interface. It provides brief, contextual information or guidance to help users understand the element’s purpose or functionality without cluttering the main interface. A well-placed tooltip reduces user uncertainty without cluttering the interface.

Example

Field: “Billing Email”

Tooltip: “Invoices and payment confirmations will be sent here.”

Do

  • Use clear, conversational language
  • Keep it brief—one sentence is often enough

Don’t

  • Repeat the label
  • Use technical jargon

Tip

Make tooltips informative to reduce the learning curve for users to achieve their goals.

4. Toast Messages

A toast message (or simply "toast") is a brief, non-intrusive notification that appears temporarily on a user interface to inform users about an action’s status or a system update. Toast messages are quick, transient, and often overlooked—but they’re key to reinforcing feedback loops in SaaS. There are two types of toasts—with or without an action. Here are some examples:

Examples

  • Toasts Without Action: Used for passive feedback—no user input needed.
    • Success: “Profile updated.”
    • Auto-save: “Draft saved at 2:32 PM.”
    • System Status: “Connection restored.
  • Toasts With Action: Include a button for undo or follow-up.
    • Undo: “Task deleted. [Undo]
    • Retry: “Upload failed. [Try again]
    • Next Step: “Report ready. [View]

Do

  • Confirm success
  • Guide next steps
  • Use plain language

Don’t

  • Use only icons or “Success!” without context
  • Overload with details—save those for in-line alerts

Tip

Write toast messages like headlines—one sentence with a clear message and no guesswork.

Conclusion

From modals to tooltips to toast messages, microcopy steers behavior, reduces mistakes, and makes enterprise software feel human. At Perpetual, we create microcopy carefully as an integral part of the product experience from day one.

Want to learn more about best practices when designing SaaS platforms? Check out our posts “How to Design a Better SaaS User Management Experience” and “How to Design SaaS Onboarding Flows that Boost Adoption.”

Looking for a team to help you build SaaS platforms that bring clarity and confidence? Let’s connect.