Interactive Email for Post-Purchase Satisfaction Check-Ins

A check-in works best once the parcel is open. A journey sends it a few days after each order, the customer rates it with one tap, anyone less than happy gets a follow-up question, and your team hears about a low score in time to put it right.

Subject

How's your House Blend?

Ask how each order went once it has arrived: one tap on a rating, a follow-up question for anyone less than happy, and an alert so your team can put it right the same day.

Ask too soon and the parcel is still on its way. A journey that waits for delivery asks at the moment the customer has an opinion, and a one-tap rating makes giving it effortless.

What to build

  • Rating: "How's your new camera?" with stars or emoji faces.
    • Ask a follow-up when rating is at most asks "What could we have done better?" on the next page.
    • Alert when rating is at most emails your team as each low score arrives.
    • Save answer to contact field keeps the score on the customer's contact.
  • Poll: "What stood out?" with Allow several answers: the packaging, delivery speed, the product itself.
  • Coupon: a thank-you code for the next order, with a button to your shop.
  • Product: the item they bought, or one that goes with it, ready to buy again.

Every customer can rate, whatever app they read your email in.

To collect reviews of the product itself, which customers can publish on your store, see post-purchase review requests.

Send it after each order

  • Orders through your emails. A journey with the Purchase trigger starts for each MailInApp checkout, and for each Shopify or WooCommerce order that came from one of your emails. The Post-purchase check-in starter journey installs it with the email ready to edit.
  • Every store order. Zapier or n8n takes each new order from your store, adds the customer to your contacts with Create or Update Contact and starts a journey with Trigger Journey, through the journey's API call trigger. Turn on Allow re-entry (each time the trigger fires), so a repeat customer goes through again.
  • A Wait step of a few days, your usual delivery time, sends the check-in once the order has arrived.

Each customer rates each check-in email once. For repeat customers, point the send step at a fresh copy of the check-in each season, made with Save as template.

Put a low score right

The Post-purchase check-in starter adds a second journey on the rating: a Branch step sends a score of 2 or less to a Create ticket step, so the customer is in your support inbox with their score. Add a Notify me step for a push, email or Slack message as well. See support tickets.

What comes back

  • Insights › Blocks shows the average with its range, how scores are spread, how they change week by week and who gave a low score. See CSAT, CES and NPS rollups.
  • The follow-up answers sit with each score, and the poll shows what customers mention most.
  • The coupon's button counts its clicks in Insights › Engagement, and your store's reports show the orders that used the code.

Getting started

Install the Post-purchase check-in starter from the Journeys page, edit its email to your brand with a Rating follow-up and a Coupon, and turn both journeys on.

Watch: cart and thank-you journeys with Mia AI

Describe a journey in your own words, and Mia AI plans it and writes its emails: a cart reminder and a last nudge, then a thank-you with a star rating after each shipped order.

A typical build-and-send sequence

  1. 1

    Build the check-in

    Add a Rating with a follow-up question and a low-score alert, and a Poll on what stood out.

  2. 2

    Start a journey on each order

    Use the Purchase trigger for MailInApp checkout and store orders from your emails, or let Zapier or n8n start the journey for every store order.

  3. 3

    Wait for delivery

    A Wait step of a few days, your usual delivery time, sends the check-in once the order has arrived.

  4. 4

    Follow up on low scores

    A second journey on the rating branches on the score and opens a support ticket or alerts your team.

Frequently asked questions

Where do the answers go?

To the email's Insights: the average with its range, how scores are spread, how they change week by week and who gave a low score. Save answer to contact field also keeps each score on the customer's contact.

Can the check-in wait until the order has arrived?

Yes. The journey's Wait step counts from the order, so set it to your usual delivery time, such as five days. When your shipping tool can tell Zapier or n8n about each delivery, start the journey on delivery instead and wait a day.

How does my team hear about an unhappy customer?

Alert when rating is at most emails the addresses you choose as each low score arrives. The Post-purchase check-in starter also opens a support ticket after a low score, and a Notify me step can alert you by push, email or Slack.

Do customers need to leave the email to answer?

A rating takes one tap and a short confirmation page, in every email app. For a low score, the follow-up question appears on the next page.

What about customers who order again?

Each customer rates each check-in email once. To hear about later orders, point the journey's send step at a fresh copy of the check-in each season, made from your template.

Build this in the studio

Start on the free plan — every interactive block and the full fallback engine are included on every tier.