Plain-text email deserves a real edit
Treat the text version as a complete message, with clear structure and usable links—not just HTML with the tags removed.

On this page
Keep the same promise in both versions
An email can carry plain-text and HTML alternatives using multipart/alternative. These parts represent the same information in different formats; a receiving client chooses the representation it can use. The text version should therefore offer the same essential message and destination.
Do not make the plain-text part a placeholder telling someone to view the HTML version. If the email confirms an invitation, it should identify the workspace and include the invitation link in both versions.
Edit structure as well as words
Removing HTML tags is a starting point, but it can leave headings, buttons, and footer links jammed together. Read the generated output from top to bottom. Add sensible paragraph breaks, meaningful link labels, and a clear separation between the action and supporting information.
Your workspace is ready.
Open your workspace:
https://app.example.com/workspace
Need a hand? Reply to this email.Test links and personalization
Use a test fixture with missing optional values. The text output should never say ‘Hello undefined’ or include an empty destination. Check that links survive line wrapping and that any security-sensitive link is handled according to your application’s rules.
Keep the two representations tied to the same content inputs. When the HTML copy changes, review the text version in the same change. Otherwise an old deadline or button destination can remain hidden in the less frequently previewed alternative.
Plain text does not need to imitate the visual layout. It needs to let the recipient understand the message and finish the same task with confidence.
