Part 3 · Operate
The emails we send
Every email the product sends, in the brand, listed on Admin, Emails, where an admin can change its words.
01What it is
Every email the product sends to a founder, a visitor or the admins goes out in one frame: the mark, the name, a violet button and the address at the foot. Admin, Emails lists each one with when it goes and to whom. Open one to read it as it will arrive, change its words, send yourself a test and put it back on the default with one press. The sign-in emails are sent by Supabase, so they sit on the same screen ready to paste into Supabase.
02Why it exists
The words in an email are product copy and change as often as the product does. Keeping them in the code meant every change waited for a deploy and an engineer. Names, dates and links stay in the code, so a rewording can never send a broken link, drop an unsubscribe or invent a number.
03How to use it
- 01Open Admin, Emails and pick an email. The preview on the right is drawn by the same code that sends it, from sample data.
- 02Change the subject, the grey preheader, the paragraphs, the button label or the footer note. A {{token}} stands for data from the real send, such as a name, a date or a link; move it or write around it.
- 03Send me a test sends the draft to your own address. Save puts it into every send within a minute.
- 04Restore default puts the words in the code back. Every change, and every restore, stays in the history with who made it.
04What good looks like
- You give it
- The admin changes the plan email's subject to "{{subject}}: read it before Monday" and keeps the paragraphs.
- You get
- Every plan email from then on carries the company's own name in the subject, with the new words after it, and the plan link unchanged.
- Why
- The data stays a token, so each send fills it with its own company, and only the wording changed.
Example data, from the demo workspace
05What weak looks like, and what it costs
- You give it
- The admin deletes the paragraph of a recovery email that holds the link to run the plan.
- You get
- Saving is refused with "Paragraph 3 carries a link. Keep {{p3}} as a paragraph of its own."
- Why
- A paragraph or footer holding a link must keep its token, so a rewording can never send an email whose link went missing.
Example data, from the demo workspace