Two linked journeys keep every customer looked after. The first waits a few days after a purchase and sends a Rating. The second reads the score from that answer and opens a support ticket when it is low, so your team follows up on its own.
A single satisfaction send asks once and stops. Two always-on journeys make the low score itself start the follow-up, so every unhappy customer hears from you quickly and every happy one is counted.
What to build
- A Rating email. Customers tap a score in the email. Turn on Ask a follow-up when rating is at most and a customer who scores low is asked "What could we do better?" on the next page, and the answer joins the score in your responses.
- A same-moment alert. Alert when rating is at most emails your team the moment a low score arrives, in addition to the ticket.
Every customer sees the same row of scores to tap.
Journey one: ask, a few days later
The first journey starts on purchase: a checkout completed from a Product block, or a paid order from your connected Shopify or WooCommerce store that MailInApp can trace to an email you sent. A wait step gives the order a few days to arrive, then a send step mails the Rating.
Journey two: watch the answer, follow up on low scores
The second journey starts on an interaction: the rate action of the first journey's email. The moment someone taps a score, the run begins with that score. From there:
- An update-field step writes the rating onto the contact record.
- A branch step checks whether it is 2 stars or below.
- A create-ticket step, on the low-score path, opens a support ticket with the contact's email and the exact score.
A high rating ends the run and still counts toward your satisfaction average.
Why two journeys
A purchase and a later answer are two different moments. Two linked journeys keep each trigger clear, and the Post-purchase check-in starter creates both together with the check-in email.
What comes back
- Tickets. The ticket in your account-wide Tickets inbox already names the customer and the score, so a person can reply straight away.
- Insights. Insights shows the score distribution and the average over time.
- Contact fields. The saved score is there for a segment of every customer who rated 2 or below.
How to automate and tune it
The 2-stars-or-below limit is the starter's default, and you can change it like any other condition. The same pattern fits any answer a journey can start from: a form, an RSVP or a poll vote can feed the same update-field, branch and create-ticket steps. Mia AI can build the pair from a description.
How to improve it
To learn which ask gets more answers, compare two paths with a journey experiment on response rate.
Getting started
Install Post-purchase check-in from the Journeys list for both journeys and the Rating email together. Or build it yourself: a purchase journey that waits and sends a Rating, plus a second journey that starts on that email's rate action. See Journeys for every step. To ask by purchase history instead, see win back past buyers with purchase-history segments.