Autopilot
Emails that send themselves, and workflows that tag orders and customers or email your team when something happens.
In the admin Growth › Autopilot
Open Growth › Autopilot. These emails go by themselves, only to customers who agreed to receive your marketing emails, and each one carries a link to unsubscribe. The page says how many customers are subscribed.
If the page says Marketing emails cannot be sent yet, Storeloom’s sender for marketing emails is not connected. None of the emails on this page goes out then, every switch shows off, and none can be turned on until the sender is connected. Order emails are not affected.
What your emails did
At the top, What your emails did shows, for the period you choose, how many of each email went, and the visits, orders and sales that came through its links. A link in these emails carries a tag, so a visit is counted for the email it came from. An order counts for Abandoned checkout when the shopper came back to that checkout after the reminder. Opens are not counted: mail apps open emails by themselves, so the number says little.
Welcome email
Tick Send the welcome email and choose When: at once, or after 1, 3 or 12 hours, 1 day or 3 days. Each customer who subscribes (at checkout, in a signup form or the email sign-up pop-up, or when you add them with their agreement) gets one welcome. The pop-up is turned on in the theme editor, under Theme settings › Email sign-up pop-up. When you turn it on, those who subscribed in the last 7 days get it too; nobody gets it twice.
Win-back email
Tick Send the win-back email and choose how long After their last order: 60, 90, 120, 180 or 365 days. A subscribed customer whose last order is that old gets one win-back. If they order again, they can get another one when that order is that old in turn.
Browse reminder
Tick Send the browse reminder and choose When: after 1, 3 or 12 hours, 1 day, 3 days or 1 week. It reminds a shopper of the last product they looked at in your store, with its picture, its price and a link back to it; the price is the one of the market they looked in, in its currency, with the market’s own prices and price breaks, as the abandoned checkout reminder shows it. It goes only to a shopper your store remembers: someone who ordered before and agreed to your marketing emails, on a visit where they accepted cookies. It is not sent if they bought it or put it in their cart since, if it is no longer for sale, or if they unsubscribed; each shopper gets at most one a week. It is written in the language of their checkout.
Price drops
Tick Send price drop emails and set the Minimum drop (%): how far below the price the shopper saw a price must fall before they hear of it, a whole number from 1 to 90 (5 until you change it). It goes to the same shoppers as the browse reminder: someone your store remembers because they ordered before and agreed to your marketing emails. Your store remembers a shopper only when they order while abandoned checkout reminders are on (Orders › Abandoned checkouts); while those are off, the card says so, with a link to turn them on. It is about a product in their cart, or the last one they looked at on a visit where they accepted cookies, when it now costs at least that much less than when they saw it. The email shows the product’s picture, name and variant, the price they saw struck through, the new price and a link back to it, in the language of their checkout.
Each shopper gets at most one a day, about the product whose price fell furthest, and never twice for the same price: they hear again about that product only if the price falls below the one they were told. Nothing is sent if they unsubscribed or ordered since, took it out of their cart, if the product is no longer active or is sold out, or if the price is no longer that much lower. It works with your store’s own prices only: a shopper in a market with its own currency, exchange rate, price adjustment or rounding, or with a fixed price or price breaks for the product in that market (Markets › Catalogs), gets none. Your store knows a shopper’s market once their cart reaches the checkout or gets something; for a shopper who has only looked at a product, it does not, so they get one only while none of your markets prices that product differently. Gift cards are never included, since a gift card is sold at its value. Discounts and codes do not count as a lower price.
More emails
More emails has five more, each off until you tick it. They go only to customers who agreed to marketing emails.
- Second welcome follows the welcome email, 1 to 14 days later.
- Thank you thanks a customer 1 to 30 days after an order, at most once a month.
- Next order invites a customer back 7 to 60 days after their first order, if it is still their only one.
- Best customers thanks a customer once, when their orders add up to the amount you set.
- Birthday greets a customer on the day or up to 7 days before. Add the date under Edit on the customer’s page.
Each can name a Discount code, and Edit opens the email’s words. Turning one on does not write to everyone you ever sold to: only those due from now on, and those due in the last week.
Discount codes
The welcome and win-back emails can name a Discount code: create the code in Discounts first, then type it here. The email says to use it at checkout; leave it empty for none.
Apply in the bar at the top (it says Unsaved changes while something is not saved) keeps your choices. The page says how many of each went in the last 30 days.
The emails' words
Edit the email opens it in Emails, under Marketing, where you change its subject and text like any other email; turning it off there stops it too. Each is sent in the language of the customer’s last order, else your store’s; the browse reminder and the price drop email in the language of the shopper’s checkout. Use {{ discount_code }} for the code and {{ unsubscribe_url }} for the link to unsubscribe; keep the link in your own version. The browse reminder adds {{ product.title }}, {{ product.url }}, {{ product.price }} and {{ product.image_url }}. The price drop email has the same, with {{ product.variant_title }}, and its two prices as amounts to write with your currency: {{ product.was_price | money }} (the price they saw) and {{ product.price | money }} (the new one).
Unsubscribing
The link opens a page of your store that asks the customer to confirm with Unsubscribe; opening it alone changes nothing. Mail apps that offer their own unsubscribe button use it too. Once unsubscribed, the customer gets no more marketing emails from your store; emails about their orders still arrive, and their customer page shows them as not subscribed.
Workflows
Under the emails, Workflows do something by themselves when something happens in your store: “when an order is placed, if its total is at least 100, tag it *big order* and email the team”. Workflows come with the Grow plan and above; on Start (and during the trial) Add workflow is greyed out and says so, with a link to Plan. A workflow kept from a plan that had them stays, shows Paused by the plan and does not run; it cannot be turned on until the plan includes workflows again, and then it runs for the events from then on. Choose Add workflow, then:
- Name it, and tick On when it should start. It runs for each new event from then on; earlier ones are not run again.
- When: an order is placed, paid, fulfilled, cancelled or refunded in full; a return is started; a customer is created or subscribes to emails; or a product sells out or is back in stock.
- If (optional, all must hold): the order total is at least or less than an amount; it ships to some countries; it is paid by cash on delivery, bank transfer, card or gift card; it contains one of some products; it used a discount code (or a given one); it is the customer’s first order; the customer has a tag; the customer gets your marketing emails. A customer’s trigger offers only the customer’s conditions.
- Then, in order: tag the order, tag the customer (tags they have stay), or email the team: your message, sent to the staff recipients set in Emails › Email settings › Staff notifications, with a link to the order, customer or product it ran on; your message stays as you wrote it, and the rest of the email is in each recipient’s language (see Emails). While nobody is set to receive them the action says so, with a link to add someone, and a run says No email went instead of Emailed the team.
Ideas to start from fill in a whole workflow, such as tagging your best customers or hiding what sells out, for you to check and turn on. Conditions can also read the order’s tags, the customer’s number of orders and what they’ve spent, and a product’s tags. Besides tagging and emailing the team, a workflow can take tags off, comment on the order’s timeline, archive the order, and take a product off the store or put it back.
Wait is a step like any other: for example “wait 3 days, then email the team”. It can wait up to 30 days. Tick Stop if the conditions have changed by then to check again when the wait ends, so a reminder doesn’t go out for an order that has since been dealt with.
Otherwise holds what to do instead when the conditions do not hold, such as tagging small orders differently. Leave it empty to do nothing.
On a saved workflow, Try it shows what it would do with your latest order, customer or product. Nothing changes.
The save bar at the top saves the workflow and says first what is missing. Runs lists the latest runs: which order or customer, when, and what came of it: Done (with what it did), Waiting (it goes on when the wait ends; if you turn the workflow off or change it first, it stops), Skipped (with the condition that did not hold) or Failed (the order or customer was deleted first). Each event runs a workflow once; two workflows tagging the same order at once each keep their tags. Customer’s first order holds only when the customer has no earlier order that was not cancelled. When a workflow takes a product off the store, its run says so and Home shows how many products workflows took off the store in the last week, with a link to them. Remove workflow asks first, then removes it and its runs; tags it added stay.
Who can change it
Everyone on your team sees Autopilot; owners and admins change it.
A workflow changes orders, customers or products later, by itself. So with a role of your own (Settings › Users), saving or removing a workflow also needs the permission to change what it changes: orders for a workflow about orders, customers for one about customers or one that tags the customer, products for one about products. The page says which permission is missing, and the save bar waits until the trigger is one your role may change. Runs and Try it name the order or customer only to members who may see orders or customers; others see what happened without the name.
The assistant and AI connections cannot add, change or remove workflows.