Post-Purchase Satisfaction Journeys With Automatic Ticket Escalation

A one-off satisfaction send asks once and moves on. Two always-on journeys keep going: the first mails a Rating a few days after a purchase, and the second starts on that answer and opens a support ticket the moment the score is low enough to need a person, while your team is alerted at the same time.

Subject

How did we do?

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:

  1. An update-field step writes the rating onto the contact record.
  2. A branch step checks whether it is 2 stars or below.
  3. 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.

A typical build-and-send sequence

  1. 1

    Trigger the first journey on purchase

    Set the trigger to purchase for any project. It fires for a Product block checkout and for a paid order from a connected Shopify or WooCommerce store that MailInApp can trace to one of your emails.

  2. 2

    Wait, then ask for a rating

    A wait step gives the order a few days to arrive, then a send step mails the Rating.

  3. 3

    Start a second journey on the rating

    Point a second journey's trigger at the Rating email's own rate action. It starts the moment someone taps a score, carrying that score.

  4. 4

    Save the score and open tickets for low ones

    An update-field step saves the rating on the contact, a branch step checks whether it is 2 or below, and a create-ticket step opens a support ticket for those that are.

Frequently asked questions

Does the ticket include the rating and who left it?

Yes. The create-ticket step carries the contact's email and the exact score, so the ticket in your queue is ready for a person to answer.

Why two journeys instead of one longer one?

The first starts on a purchase and the second on an answer to the email the first one sends. Two linked journeys keep each moment clear, and the Post-purchase check-in starter creates both together.

What happens to a high rating?

The run ends there, and the score still counts toward your satisfaction average. Tickets are opened only for the scores that need attention.

Can I change the low-score limit or who gets the ticket?

Yes. The branch step's condition is an ordinary rule you can edit (2 stars or below is the starter's default), and tickets arrive in your account-wide Tickets inbox whichever journey opened them.

Does this replace a recurring check-in send?

It is the always-on version of the same idea. A recurring send suits a periodic check-in, and the journeys add an immediate follow-up on every low score.

Build this in the studio

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