Customer onboarding emails — 7-email sequence

Set up a 7-email post-purchase sequence that walks a new customer from confirmation through the 30-day check-in

The 30 days after purchase are when the customer decides if the buy was a good call. If those days are quiet, the doubt grows. If the support load is too high, the customer feels stranded. The right onboarding sequence sits in the middle — present enough to guide, light enough to stay out of the way.

This recipe sets up a 7-email onboarding sequence in SGEN that runs from purchase through day 30. Each email has one job. Each one earns the next one. By the end, the customer either has the product working or has named the blocker out loud.

What is this for?

Use this recipe to design and run a customer onboarding email sequence — the emails that go out automatically after a purchase. The output is seven emails sent on a defined cadence, tied to a real post-purchase pipeline (delivery, setup, first value, deeper use, check-in).

The end state after setup:

• A purchase-triggered automation that fires on every paid order.
• Seven emails spread across 30 days, each with a clear job and a clear next step.
• A segmentation hook that lets the team filter the cohort by product, plan, or order value.
• A check-in email at day 21 that catches the customer who has gone quiet.
• A 30-day review email that closes the onboarding window and invites the next step.

Good use cases

SaaS subscription product. New customer needs to log in, set up the account, and reach first value. Sequence guides each step and catches the drop-offs.

Digital product or course. Customer bought a course or a digital download. Sequence helps them start, work through the material, and reach the outcome promised.

E-commerce physical product. Customer bought a physical good. Sequence covers delivery expectations, unboxing experience, and post-arrival use guidance.

Service business with recurring billing. Customer bought a retainer or ongoing service. Sequence sets expectations for cadence, communication channels, and the first deliverable.

What NOT to use this for

• One-time low-ticket purchases with no follow-on. A $5 download does not need 7 emails. Send one confirmation and one thank-you.
• Enterprise sales with a dedicated CSM. The CSM owns the onboarding. The email sequence would step on the human relationship.
• Free-trial signups (no purchase yet). A free trial uses a different sequence — the focus is on conversion to paid, not on activation. Use a separate trial-onboarding sequence.

How this connects to other features

• Forms + Integrations — the trigger for the sequence is a paid order or a form submission. The integration handles the actual send.
• E-commerce — for product purchases, the e-commerce module is the source of the trigger event. The order completion fires the sequence.
• Blog — most onboarding emails link to a help post or a tutorial. Maintain those posts as part of the same content backbone.
• Media library — onboarding videos and PDFs live in the Media library and link from the emails.
• Pages + SG-Builder — the welcome page and the help-portal page are SG-Builder pages. The first email links to the welcome page.

Before you start

You are signed in as an Administrator. You have the email service integrated with SGEN — the automation lives in the email service and the trigger comes from SGEN.

You have the 7-email content drafted or at least outlined. You have alignment with whoever owns customer success — the onboarding sequence is the public face of how the brand treats new customers. You have the help-portal URL, the support email, and any first-value links (account login, course access page, tracking page) ready.

Where to find it

Steps

1. Map the post-purchase pipeline

Before writing any email, sketch the customer's first 30 days. Five questions answer the shape:

1. What does the customer do in the first hour after purchase? (Log in, download, wait for shipping.)
2. What do they need to do in week 1 to reach first value?
3. What is "first value" for this product? (First successful use, first send, first arrival, first session.)
4. What deeper use case applies in week 2 to 3?
5. What does a 30-day-good outcome look like?

The 7 emails map to these five touchpoints — one per gap, with overlap where the gaps are long.

The shape of the 7 emails:

2. Set the trigger

Navigate to Forms → Integrations. Pick the email service. Set up an automation triggered by:

• For SaaS — a paid order with a specific product or plan SKU.
• For e-commerce — order status changing to Paid or Fulfilled.
• For services — a form submission on the onboarding intake form.

Tag the customer on entry with the product slug — onboarding-product-x. The tag stays on the contact and feeds later segmentation.

Send a test trigger event to confirm the automation fires. If the automation does not fire, the trigger condition is wrong — usually the SKU does not match or the order status field is named differently in the integration than in SGEN.

3. Write email 1 — purchase confirmation (day 0)

Email 1 fires within minutes of purchase. The customer is at peak interest. Use the email to:

• Confirm what they bought, by name and quantity.
• Confirm what comes next (delivery date, access link, login URL).
• Set the expectation that more emails follow — "Over the next 30 days, you will get six more emails from us covering setup, first use, and a 30-day check-in."

Tone is direct and warm. No fluff. Subject line: "Your order is in" or "Welcome to " — clear, no hype.

Include the support email and the help portal link in every email's footer. The customer should never have to hunt for help.

4. Write emails 2 and 3 — get started and reach first value (day 1, day 3)

Email 2 (day 1) walks the customer to first action. Pick the one most important thing they need to do — log in, set up the account, place the first item, choose the first project — and walk them there in one email.

• One headline action.
• Three to five short bullets of context.
• One link, one CTA. ("Set up your account →")
• A line on what happens next.

Email 3 (day 3) walks the customer to first value. First value is the moment the product proves itself — the first send, the first session, the first finished output. If they have not reached first value by day 3, the email helps them get there.

• A short story or example of what first value looks like.
• One specific use case the customer probably has.
• A walkthrough or link to a help post.
• A check-in question: "Stuck? Reply to this email."

The check-in question is real. Replies route to whoever owns customer success. A reply that gets a personal answer in 24 hours saves more accounts than three more automated emails.

5. Write email 4 — week-1 check-in (day 7)

Email 4 is the light-touch check-in. The customer has had a week. They have either reached first value or they have not. The email's job is to find out.

• Short — 100 to 150 words.
• One question: "How is it going?"
• One specific offer of help — a 15-minute support call link, or a reply-to-this-email path.
• One link to a deeper resource for the customers who are humming along.

Subject line: "Quick check — how is your setup going?" Conversational, not corporate.

6. Write email 5 — deeper use (day 14)

By day 14, the customer who is engaged is ready for a deeper use case. Pick the second most-common use the product supports and walk them through it.

• A short story or example of what the deeper use looks like.
• Concrete walkthrough — 3 to 5 steps.
• A link to a help post or video for the full walkthrough.
• A line on what comes next ("Next week we will check in on how things are going.")

For customers who have not reached first value yet, this email is too advanced — but the day-21 check-in catches them. Do not try to make one email serve both segments; the 7-email cadence handles the split through pacing.

7. Write email 6 — week-3 quiet-customer catch (day 21)

Email 6 catches the customer who has gone quiet. Three weeks in, they are either active (great), drifting (saveable), or gone (already churned).

The email's job is to surface the drifting ones. Send a direct check-in:

• Open with the honest observation: "We have not seen you log in this week."
• One specific question: "Is there a blocker we can help with?"
• A path to a real human — a reply, a support email, a calendar link.
• A line on the value the customer is leaving on the table.

The customer who replies is saveable. The customer who does not reply is mostly already gone — and that signal is itself useful. Build a tag for "no-reply-at-day-21" and run a quarterly review on the cohort.

For active customers, the email reads slightly differently — they confirm everything is fine and the sequence moves on. The same email body works for both segments because the framing is care, not sales.

8. Write email 7 — 30-day review (day 30)

Email 7 closes the onboarding window. The customer has either reached the 30-day-good outcome or they have not. Either way, the email's job is to acknowledge the milestone and set up what comes next.

For customers who reached the outcome:

• Acknowledge the milestone explicitly. Name what they achieved.
• Invite the next step — a deeper plan, a referral, a case study, an advanced feature.
• Ask for feedback — a 2-minute survey, a reply with one sentence, a NPS link.

For customers who did not reach the outcome:

• Acknowledge it honestly. No corporate cover.
• Offer a real conversation — a 20-minute call with whoever owns customer success.
• Make sure the path to cancel or downgrade is also visible if that is the right move.

Subject line: ", your first 30 days with " or similar. Direct.

9. Test the full sequence

With all 7 emails set up in the email service, run a test cohort:

1. Trigger the sequence with a test purchase.
2. Confirm email 1 arrives within minutes.
3. Confirm email 2 arrives on day 1 (use the email service's test mode to compress the schedule for the test).
4. Walk through each email's link and CTA. Confirm every link resolves.
5. Confirm the segmentation tag is applied at trigger time and stays on the contact.
6. Confirm replies route to a monitored inbox.

If any email's link is broken or the trigger does not fire, fix before launching to real customers. A broken email in the first 30 days reads as careless and the customer remembers it.

What success looks like

After 30 days running with real customers:

1. Every paid order triggers the sequence and email 1 lands within minutes.
2. Open rates on email 1 run 70 to 90% — purchase confirmation is anticipated.
3. Open rates on emails 4 and 6 (the check-ins) run 30 to 50%.
4. The reply rate on email 4 runs 5 to 15% — those are the savable accounts surfacing.
5. The 30-day customer retention rate is measurable and trending. Compare cohorts before and after the sequence launched.
6. Support load on first-week questions drops because the sequence pre-empts the common questions.

What to do if it does not work

The trigger does not fire. The trigger condition is wrong — usually the SKU mismatch or the order-status field name. Open the integration, confirm the trigger condition matches what SGEN sends. Run a test order.

Email 1 lands in spam. The sending domain is not authenticated. Confirm SPF and DKIM records for the sending domain. Avoid all-caps subject lines and excessive punctuation.

Open rates drop after email 3. The early emails are too long, or the subject lines are not landing. Shorten emails 4 onward. Test subject-line variants. The check-ins should read like a real person sent them.

No one is replying to the check-ins. The check-in questions are too generic ("How can we help?"). Make them specific ("Is there a blocker on your first project?"). Replies follow real questions.

Customers complain about email volume. Seven emails in 30 days is generally fine for engaged customers but can feel like too much for low-engagement ones. Track the unsubscribe rate per email. If unsubscribes spike on email 5 or 6, the cadence is too dense — stretch to days 17 and 25 instead of 14 and 21.

The 30-day review email goes to customers who have already churned. The sequence does not check the customer's current status before sending. Add a condition on email 7 that checks for active status. If they have cancelled, the email reads as tone-deaf.

Variations

Branching by product type. When the brand sells both digital and physical products, email 2 forks. Tag the customer at trigger time with the product type (onboarding-digital or onboarding-physical). The automation branches at email 2: digital customers receive an access link and a setup walkthrough; physical customers receive a shipping update and an arrival expectation. Emails 4 through 7 rejoin as a single shared path once the product-specific context is covered.

Compressed 14-day sequence. For lower-ticket purchases where 30 days is too long, run a 5-email sequence in 14 days. Day 0 confirmation, day 1 get started, day 3 first value, day 7 check-in, day 14 review. Skip the deeper-use and quiet-customer catches. Suitable for purchases under $50 where the support expectation is lower.

Referral ask at day 14 instead of day 30. For products with a high early-satisfaction rate, insert a referral ask at day 14 — after first value, before the novelty fades. Email 5 (deeper use) doubles as a referral ask: "Enjoying it? Share with one person who'd benefit." Day 30 review then skips the referral and focuses on retention.

Customer success handoff at day 7. For high-value accounts with a dedicated CSM, the automated sequence runs only through email 4 (day 7). At that point, the automation creates a task for the CSM to reach out personally. Emails 5 through 7 are deactivated for accounts tagged onboarding-enterprise. The personal touch replaces the automation from week 2 onward.

Anti-patterns

Too much in email 1. Email 1 fires within minutes of purchase and the customer is at peak interest — but that does not mean it should carry setup instructions, feature tours, a referral ask, and three links. Email 1 has one job: confirm the purchase and set the expectation that more emails follow. Every other job belongs in a later email.

Generic check-in questions. "How can we help?" produces no replies. "Is there a blocker on your first project?" produces replies. The check-in emails earn their replies by asking a specific question tied to where the customer should be at that point in the sequence. Generic questions feel automated even when the rest of the email does not.

Sending the 30-day review to churned customers. The automation fires regardless of the customer's current status unless a condition is added to email 7. A 30-day review email to a customer who cancelled on day 15 reads as careless. Add a condition check on email 7: if the customer's account is cancelled or downgraded, suppress the email or route to a win-back flow instead.

No monitored inbox for replies. The check-in emails ask for a reply. If replies go to an unmonitored address, the exercise is performative. Route replies to whoever owns customer success and set an SLA of 24 hours. A real reply that gets a personal answer saves more accounts than any automated follow-up.

Examples

SaaS subscription product. Customer buys a monthly plan. Day 0 confirmation, day 1 setup walkthrough, day 3 first-project walkthrough, day 7 check-in, day 14 advanced feature deep-dive, day 21 quiet-customer catch, day 30 review with referral CTA.

Digital course product. Customer buys a 6-week course. Day 0 access details, day 1 week-1 module link, day 3 first-assignment encouragement, day 7 progress check-in, day 14 mid-course deep-topic, day 21 finishing-strong message, day 30 review with next-course invitation.

E-commerce physical product. Customer buys a branded merchandise bundle ($54.99). Day 0 order confirmation with shipping ETA, day 1 shipping started notification, day 3 arrival expected, day 7 unboxing follow-up + care guide link, day 14 accessory recommendation, day 21 review request, day 30 reorder invitation.

Service business retainer. Customer signs a 6-month retainer. Day 0 welcome with team intros, day 1 onboarding intake form, day 3 kickoff call confirmation, day 7 first-deliverable preview, day 14 first-month report, day 21 mid-month check-in, day 30 monthly review and renewal-track confirmation.

Mixed product portfolio. Brand sells both digital and physical. The sequence forks at email 2 based on product type — digital customers get an access walkthrough, physical customers get a shipping update. Tag at trigger time, branch in the automation.

Related recipes

• Newsletter signup flow — the form and double opt-in wiring used in the signup flow is the same integration pattern as the order trigger here
• Lead-magnet funnel — if onboarding customers also receive a lead magnet (guide, template), wire it into email 3 using the same delivery pattern
• Black Friday playbook — the re-engagement email at day 30 can carry a campaign CTA if the 30-day mark falls during a sale window

Related reading

• Form integrations
• Orders overview
• Create and manage blog posts

Last updated: 2026-05-25