Back to Explore
GuideVibeFix editorialUpdated Nov 11, 2026

Sending It Isn't the Job: Notification Email Templates for Vibe Projects

A notification email is not a marketing email. This guide covers the five-part structure, six template types, variable fallbacks, layout rules, and a twelve-item pre-send check — with exact limits you can copy into your spec.

A woman sending an email at a public computer in an internet cafe

Start with a very specific scene. Xiao Man built a budgeting app called Shiguang Ledger — the product and person in this guide are fictional. After the first release, she got two kinds of complaints that read almost identically. The first: "I registered and waited forever, but no verification email arrived." The second: "I found the password-reset email in my spam folder. Its subject was 'System Notification' and I thought it was an ad."

Xiao Man spent hours checking the send logs: not a single email had gone missing, and the delivery rate looked fine. The problem was not whether the emails were sent, but whether they were written right. The verification email had the subject "Please verify your email address", its first line was three lines of product introduction, and the code was buried in the third paragraph. The password-reset email had the subject "System Notification" and a sender address nobody recognized. Users were not failing to receive the emails — they could not tell which email was hers in the inbox.

A woman sending an email at a public computer in an internet cafe

1. First, separate them: notification email is not marketing email

Notification email and marketing email are two completely different things, and mixing them up hurts both. A marketing email says "I want you to know something": it can tell a story slowly, carry three images, and wait until the user has time. A notification email says "you just did something, and now you need to know the result": the user is waiting for it, looking for it, and relying on it to take the next step. Verification, password reset, transaction confirmation, bills and receipts, and expiry reminders are all notification emails.

This guide only covers how notification emails are written: how to write the subject line, how many parts the body has, how to fill in variables, and what to test before sending. How delivery itself works — sender domains, SPF, DKIM, DMARC, subdomain isolation — is covered by the transactional email deliverability guide on this site; that is infrastructure work. How on-site push works is covered by the notification system guide; how to build a subscriber list and send product-update sequences is covered by the email marketing guide. This guide assumes your emails already reach the inbox normally, and solves what happens after that: can users recognize the email within three seconds, find the key information, and finish the next step?

There is a crude but reliable test for whether a notification email is well written: looking only at the subject line and the first sentence, can the user say what the email wants them to do? If not, the email has failed, no matter how promptly it was sent. Before writing, ask yourself one question: is this an email the user is actively waiting for, or one I want them to see? The first is notification, the second is marketing — do not mix the two jobs into one email.

2. A notification email has only five parts

Notification emails do not need creativity; they need structure. I use a structure with five parts, each with a length limit. Go over the limit and you cut; if you cannot cut it down, the email is trying to say too many things and should be split into two.

The first part is the subject line, capped at 50 characters. It has one job: let the user recognize what the email is for at a glance in the inbox list. Write it as "action + object", for example "Please verify your email address", "Password reset link sent", or "Your October bill is ready". Do not write "Dear user, hello!" — that says nothing. And do not pile exclamation marks and emoji into the subject line: exclamation marks do not make users take it more seriously, they only make the email look more like spam.

The second part is the preview text, capped at 90 characters. Preview text is the small line shown after the subject in the inbox, and many people do not even know it exists — they let the mail client auto-snip the start of the body. The right move is to write it yourself, finishing what the subject line left unsaid: "Your 6-digit code is valid for 10 minutes." Note that preview text must not repeat the subject line; repeating it wastes your only chance to add information.

The third part is the opening sentence, capped at 40 words. This is the first line the user sees after opening the email, and it must give the conclusion directly: "Your verification code is 482913, valid for 10 minutes." No pleasantries first, no product introduction first, no "Thank you for using Shiguang Ledger" first — the user did not open this email to catch up, they came to get the code. Conclusion first, small talk never.

The fourth part is the body, capped at 300 words. The body carries only what the user truly needs to complete the next step: what the code is, where to click, how much it costs, when the deadline is. A notification email longer than 300 words has almost certainly smuggled in marketing content: new feature introductions, usage tips, invite-a-friend offers. Those have their own emails; do not let them hitch a ride in a notification.

The fifth part is the footer, capped at 60 words. The footer says three things only: why this email was sent to you, where to unsubscribe from or turn off this kind of notification, and one line saying "If you did not request this, please ignore this email." The footer is the last line of defense for trust: when users receive an email they do not remember triggering, they check the footer first to judge whether they triggered it, and then decide whether to click the link.

Five-part structure of a notification email: subject line max 50 characters, preview text max 90 characters, opening sentence max 40 words, body max 300 words, footer max 60 words

These five numbers — 50, 90, 40, 300, 60 — belong in your project's email template spec. Every time you add a new kind of notification email, check it against this table first: over the limit, rewrite it; if it cannot be rewritten, split it. That is the value of a template: nobody has to reinvent the format each time, and writers and AI-generated code alike measure against the same ruler.

3. Six template types, taken apart one by one

Almost every notification email in a vibe project falls into six types, and each one is written differently. Get one wrong and you can lose users directly.

The first type is the welcome email, sent the moment registration succeeds. Its job is not to introduce the product, but to help the user finish the first step after registering: verify the email, complete the profile, create the first record. Give exactly one clear next step: "Click here to verify your email, then log your first expense today." Do not list five feature entry points in a welcome email — the user has not used any feature yet, and the more entries you offer, the fewer get clicked.

The second type is the verification-code email, where timing matters most. The code is always 6 digits, valid for 10 minutes, and the first sentence of the body states the code, bold and large, with only one code per email. Never put a verification code and another notification in the same email — users will not know which number is the code. Verification emails should carry no images and no links; plain text is best, because every image raises the odds of landing in spam.

The third type is the password-reset email, where security matters most. The reset link is valid for 30 minutes and can be used only once — used means expired. The body must state three things: who requested it, that it expires in 30 minutes, and that you should ignore it if you did not request it. Do not paste the link as a long bare URL; use a button that says "Reset password". And a password-reset email must never contain the user's old password, nor tell the user "your password is such-and-such". A reset is a reset, with no exceptions.

The fourth type is the transaction confirmation email, where accuracy matters most. Users must receive it within 5 minutes of paying. It says four things only: what was bought, how much it cost, the order number, and where to view it. The amount and order number must match the payment page character for character — users treat this email as the receipt for reconciliation, and a mismatch becomes a support ticket. Do not use a transaction confirmation to recommend other products; the user has just spent money and is feeling sensitive, and a recommendation only reads as a rush to earn more.

The fifth type is the bill and receipt email, where retrievability matters most. Send one when each monthly bill is generated, stating the billing period, the amount, the charge date, and the next renewal date, with a "Download receipt" link. Do not paste the receipt itself into the body; the body carries the summary, the details live behind the link. An email is a notification, not a filing cabinet.

The sixth type is the product-update notification, the easiest to get wrong. It only goes to users genuinely affected by this update: a feature changed, notify the people who use that feature; a price changed, notify paying users. Do not blast "we have something new" to everyone — that is already marketing email's job. Write an update notification as three sentences: one saying what changed, one saying what it means for you, and one link for details. Three sentences, then stop.

4. Variables and data: do not write the template as a fill-in-the-blank

Notification emails are full of variables: user name, amount, date, order number, links. A broken variable hurts more than a badly written body — when a user receives an email saying "Dear {{name}}, your order {{order_id}} is confirmed", their first thought is not "the template is broken", it is "this product is unreliable".

The first rule: every variable needs a fallback value. When the user name is empty, show "Hello" — do not leave a blank and do not expose the variable name. When the amount is missing, do not send the sentence at all; never send an email saying "Your bill amount is ." Fallback values must be hard-coded in the template, not left to the caller to always pass correctly.

The second rule: show numbers and dates the way your users expect. Write an amount as "¥128.00", not "128"; write a date as "8 November 2026", not "2026-11-08" or "11/08/2026". On date formats, users only recognize their own country's convention — a wrong format confuses more than no date at all. Time zones work the same way: show expiry times in the user's own time zone, not server time.

The third rule: never put sensitive information in an email. Do not write the full card number, only the last 4 digits; do not write passwords, full ID numbers, or any credential other than a one-time verification code. Email travels in plain text, and a stolen inbox leaks everything in it. When users need to verify their identity, give them a link back to the site instead of laying the sensitive details out in the email.

5. Layout: make sure it reads with all images off

There is one iron rule for notification email layout: with every image blocked and every style stripped, the email must still be readable. Many mail clients block images by default, and AI-generated email templates love using images for headings, buttons, and decoration. Once images are blocked, the user sees an email full of empty boxes.

Be specific: single-column layout, no side-by-side columns; body text no smaller than 14px; buttons built from text plus a background color, never image buttons, with a button height of at least 44px so a finger can tap it on a phone; link text that says where it goes — "View bill", not "Click here"; and a plain-text version that must exist, with the same content as the HTML version. The plain-text version is not optional, it is the baseline of an email template — some users, some clients, and some screen readers only read plain text.

Dark mode deserves attention too. More and more users read email in dark mode: light text on a dark background is fine, but dark text on a transparent background turns into a smear. Give the body and buttons explicit colors instead of relying on defaults, and test once in dark mode before launch. Ten minutes of testing saves a whole category of "I cannot read the email" complaints.

6. What to test before sending: a twelve-item check

Do not rush a finished template into production. Run through this list first — every item is a real mistake someone has made.

Send it to three of your own inboxes first: one Gmail, one Outlook, one Apple Mail. Rendering differs wildly across the three — a button that looks fine in Gmail can fall apart in Outlook. Opening it once in all three beats reading the code ten times. Then check the spam folder: the first time a new template goes out, confirm it landed in the inbox, not spam. The causes are often tiny: a "free" in the subject line, one exclamation mark too many, a template with no plain-text version.

Then click every link in the email, one by one. Links are the part that breaks most easily: a test-environment domain never swapped for production, a variable left unreplaced so the link contains {{}}, a button link and a text link pointing to different addresses. These three errors are hard to catch in code review and obvious the moment you click them in an inbox.

Then test the unsubscribe link. Click it once and confirm it really unsubscribes you — and only from this kind of notification, not from everything. A broken unsubscribe is expensive: users who cannot unsubscribe click "Report spam" instead, and enough reports drag down the whole domain's deliverability. Unsubscribe is not decoration; it is the valve that keeps you alive.

Finally, test the variable fallbacks. Deliberately send one email with an empty user name, one with an empty amount, and one with an extremely long user name, and check whether any variable name leaks, any layout breaks, or any amount shows up as "¥NaN". AI-generated template code is most likely to cut corners on fallbacks, so these edge cases must be tested by hand.

The list, in short: test in three inboxes; confirm it reaches the inbox; subject line within 50 characters; preview text does not repeat the subject; code is 6 digits and valid for 10 minutes; reset link valid for 30 minutes and single-use; amounts and dates in the user's format; every link clicked through; unsubscribe clicked once and works; empty variables have fallbacks; a plain-text version exists and matches; and it reads clearly in dark mode. Pass all twelve, then launch.

Even then, do not push to everyone at once. Send it to the internal team and 5% of users first, run it for 24 hours, and watch the four numbers for anomalies: an open rate falling off a cliff usually means the email went to spam; a rising complaint rate means stop sending and investigate first; an unsubscribe rate doubling overnight means the recipient list was wrong. If nothing looks off after 24 hours, roll out to everyone. Once an email is sent it cannot be taken back — those 24 hours of gradual rollout are your last chance to change your mind.

7. Four numbers to watch after sending

Sending is not the end; watch four numbers, and only these four. Open rate: the share of users who opened the email. Welcome and verification emails are naturally high, product-update notifications naturally low — comparing across types is meaningless, so compare only with your own previous version. Click rate: the share who clicked the main button in the body. Lower than the open rate is normal; what matters is the trend — did the click rate go up after the rewrite?

Unsubscribe rate: the share who unsubscribed. A sudden rise for one type of notification means that type is sent too often or its content has drifted. Complaint rate: the share who clicked "Report spam". This is the most dangerous of the four — when it rises, stop sending first and investigate, do not wait until the domain lands on a blocklist.

Here is a set of fictional reference numbers to give you a sense of scale — the numbers below are fictional examples, not industry statistics: in its first month, Shiguang Ledger saw a welcome email open rate of about 72%, a verification email open rate of about 91%, a transaction confirmation open rate of about 68%, and a product-update notification open rate of about 31%. Verification emails open highest because users are waiting for them; product-update notifications open lowest because nobody is waiting for them. That ordering itself is the sanity check: if your product-update notification opens more than your verification email, the subject line probably reads like marketing, or it went to people who should never have received it.

Review once a month, not every day. People who stare at the numbers daily end up tweaking subject lines, adding exclamation marks, and stuffing marketing into notification emails — short-term numbers go up, and long-term unsubscribe and complaint rates follow. The KPI of a notification email is not the open rate; it is whether users can smoothly get the key information when they need it.

8. Pre-launch checklist

Ten minutes before launch, run through this list: are all six template types covered; can each email's job be stated from the subject line and first sentence alone; are the subject line, preview text, opening sentence, body, and footer within 50, 90, 40, 300, and 60 respectively; is the code 6 digits and valid for 10 minutes; is the reset link valid for 30 minutes and single-use; are amounts and dates shown the way users expect; is sensitive information reduced to the last 4 digits; does the email still read with all images off; have three inboxes been tested; does one click on unsubscribe actually unsubscribe; do empty variables have fallbacks; and has dark mode been checked?

Anti-patterns to fix on sight: a subject line that says "Dear user, hello!"; preview text repeating the subject line; a verification code buried in the third paragraph; two verification codes in one email; a reset link that never expires; product recommendations inside a transaction confirmation; update notifications blasted to everyone; image buttons; no plain-text version; a broken unsubscribe link.

One honest note to close: notification email is the easiest place in a vibe project to overlook, and the most direct determinant of whether users trust you. No matter how good the features are, if users cannot get a verification email after registering or a confirmation after paying, trust is zero. Templates are not glamorous work, but they are the base of product credibility: five parts, six template types, twelve checks. Do it once, and every new notification type after that is just copying the homework. And copying homework costs far less than the one time a user cannot find you in their inbox.

Views 4Comments 0

Comments (0)

ME
0/1000
Loading comments...
Browse projectsPublish your project

Related articles

Real photo: a laptop, tablet, and phone on a wooden table showing the same green-leaf website, the phone view with navigation in one column, a potted plant nearby
Guide
Squashed on phones? Responsive layout and media queries, explained plainly

One page should stand up on a phone, a tablet, and a computer. This guide follows MDN's Responsive web design, Using media queries, and the viewport meta reference: fluid HTML, the viewport tag, fluid grids and max-width, images that never burst their container, media query syntax, breakpoints set by content, mobile first, responsive type, testing capability instead of width, and a pre-launch checklist.

Mobile AppsDesign ExperienceFrontend Engineering
Real photo: a bank of light gray metal filing cabinets with one drawer pulled open, revealing rows of hanging file folders inside
Guide
A real database inside the browser: IndexedDB local storage, explained plainly

localStorage only stores strings and has no indexes. IndexedDB is a real database in the browser: structured data, far larger capacity, indexes, and transactions. Following MDN's Using IndexedDB, IDBDatabase, and IDBObjectStore: the five-step routine, opening, upgrades, keys, indexes, transactions, add versus put, get, cursors, ranges, and multi-tab upgrades.

Tool TipsData WorkflowsFrontend Engineering
Real photo: hands typing on a MacBook Pro showing JavaScript code that changes HTML content, with a white mouse, papers, and binders on a white desk
Guide
Functions without the confusion: JavaScript functions, parameters, and arrow functions, explained plainly

You already call functions every day; this guide names what you have been doing. Following MDN's Functions, Arrow function expressions, and Rest parameters: declarations versus expressions, parameters and arguments, default values, rest parameters, spread syntax, return values, arrow function shorthand, the this trap, callbacks, and scope.

Tool TipsFrontend EngineeringAI Coding