# Glossary: Flows, Segments and 8 Other Shopify Email Marketing Terms Support Teams Should Understand > A shared vocabulary isn't just marketing jargon; it's the bridge between your marketing emails and the support tickets they create. Source: https://arbyn.app/blog/glossary-flows-segments-and-8-other-shopify-email-marketing-terms-supp Published: 2026-08-29 --- A customer contacts support, confused and frustrated. They received an email with a 20% discount, but the code isn't working on their cart full of new-arrival sneakers. Your support agent, trying to help, has no idea why that specific customer received that specific offer, and the situation quickly deteriorates. They don't know if it was a one-time promotional blast, part of an automated welcome sequence, or an offer exclusive to VIPs. The agent can't see the marketing calendar, the audience segment, or the campaign's goal. This disconnect, the gap between the language of marketing and the reality of support, is where customer experiences break down, and it has a staggering cost; globally, businesses stand to lose an estimated $3.7 trillion annually from poor service. The agent spends valuable minutes context-switching between their helpdesk, the Shopify admin, and the store's email platform, asking repetitive questions. The customer gets more annoyed, and a potential sale turns into a brand-damaging interaction that can poison future revenue. This is significant when reports show that up to 32% of customers will leave a brand after just one bad experience. This isn't a failure of the support agent; it's a failure of shared language. This shopify email marketing glossary for support teams is designed to bridge that exact gap, translating the core concepts of email marketing into the practical language of customer support. Why Marketing Jargon Ends Up in Your Support Queue The root of many difficult support conversations lies in the separation between the team that sends the emails and the team that handles the replies. Marketing teams operate on a vocabulary of campaigns, flows, and segments, optimizing for clicks and conversions across thousands of users at a time. Their key metrics are often Acronyms like LTV (Lifetime Value) and ROAS (Return on Ad Spend). Support teams, on the other hand, operate on a vocabulary of tickets, escalations, and resolution times, optimizing for one-on-one customer satisfaction and efficiency with metrics like FRT (First Reply Time) and CSAT (Customer Satisfaction Score). When a customer replies to a marketing email, these two worlds collide, creating friction that directly harms the customer experience. The problem isn't just about knowing a few new words; it's about understanding the *intent* behind the communication a customer received. Was the email meant to welcome them, recover a sale, or reward loyalty? Each of these goals produces different customer questions and requires a different support response, and inconsistent service is a primary driver of customer churn. Without this context, agents are forced to work backward, trying to reconstruct the customer's journey from a single, confusing data point by asking them to forward emails or provide screenshots. This operational friction is more than just inefficient; it directly impacts your store’s bottom line, as research shows that 64.6% of businesses report that deliverability and email experience issues directly impact revenue. A support agent who understands basic email marketing principles can diagnose problems faster, provide more accurate answers, and deliver a more cohesive brand experience. They can recognize when a customer is likely in an abandoned cart sequence versus a general newsletter and tailor their response accordingly, turning a negative interaction into a positive one. This glossary provides the foundational vocabulary needed to turn your support team from reactive problem-solvers into proactive customer experience managers who understand the full context of the conversations they are having. The Two Pillars: Campaigns vs. Automations At the highest level, every marketing email a customer receives falls into one of two categories: a campaign or an automation. Understanding this distinction is the first step for any support agent trying to diagnose an email-related issue. A Campaign is a one-time, manual send, often described as a "blast" or "newsletter." Think of Black Friday announcements, new product launches, a weekly newsletter with curated content, or a holiday-specific promotion like a "Mother's Day Gift Guide." The marketing team builds the email, selects a specific list or segment of subscribers, and schedules it to be sent at a set date and time. This manual creation process is key; a human being actively decides on the content and audience for a specific moment in time. If a customer writes in about a "24-hour flash sale on all outerwear," they are almost certainly responding to a campaign. The key attribute is that it's a singular event, sent proactively by the store to a large group of people at once. These emails are tied to the calendar, not to an individual customer's behavior. Support questions related to campaigns often revolve around offer clarity ("Does the free gift apply to all orders?"), coupon code issues ("Is the flash sale code stackable with my welcome discount?"), or the terms and conditions of a limited-time promotion, and having clarity on these details is crucial for fast resolution. An Automation, often called a Flow in platforms like Klaviyo, is fundamentally different. It's an automated email or sequence of emails sent to an individual customer in response to a specific action they took, or didn't take. These are not sent manually; they run continuously in the background, triggered by customer behavior 24/7 like a silent, tireless salesperson. Common examples include the welcome series for new subscribers, abandoned cart reminders, and post-purchase follow-ups asking for a review. Because they are triggered by personal actions, flows are highly contextual and relevant to that one person at that exact moment. The email a customer receives is directly related to something they just did on your site. For support teams, this means the customer's recent activity is the most important clue. A question about an offer received "right after I signed up" points to a Welcome Flow. A message asking "Did you mean to send me this?" showing an image of a product they just looked at suggests a Browse Abandonment Flow. While campaigns generate revenue through volume, flows often have a much higher return on investment because they reach customers at moments of peak intent; some analyses show automated emails can generate 320% more revenue than non-automated ones. The "Who": Defining an Audience with Segments and Lists The second critical concept for support teams is understanding *who* receives an email. Marketing messages are rarely sent to every single subscriber. Instead, audiences are organized into smaller groups to make the content more relevant, a practice known as Segmentation. A segment is a dynamic group of subscribers defined by a set of rules based on their data and behavior. For example, a marketing team might create segments for "VIP Customers" (e.g., anyone who has spent over $500 and made at least 3 purchases in the past year), "Recent Buyers" (e.g., purchased in the last 30 days), "Potential Churn Risk" (e.g., opened an email in the last 90 days but hasn't purchased), or "Inactive Subscribers" (e.g., haven't opened an email in 6 months). When a customer writes in about an exclusive offer they can't access, it's often because they aren't in the correct segment. An agent who understands segmentation can ask better qualifying questions, such as, "When was your last purchase?" or "Have you purchased from us several times before?" to determine if the customer should have been eligible for a "Repeat Customers" discount. This turns a potentially frustrating "the code doesn't work" complaint into a clear-cut policy check and a much faster resolution, as the agent can confidently explain the criteria for the offer. Closely related to segmentation is the concept of List Hygiene. An email list is not a static asset; it requires regular maintenance to remain effective. List hygiene is the process of "cleaning" your subscriber list by removing invalid email addresses and, most importantly, unengaged subscribers. Email providers like Gmail and Outlook track how many people open, click, or mark your emails as spam to calculate your "sender reputation," a score that determines if your messages reach the inbox. Sending to a large list of people who never open your messages hurts this reputation, which can cause your emails, even important ones like order confirmations, to land in the spam folder for everyone. On average, a B2C email list degrades by 22.5% per year as people abandon old email accounts. Regularly cleaning the list is essential for good deliverability, as poor deliverability can cause long-term damage that is difficult to reverse. For a support team, this has two implications. First, if a customer complains they are not receiving emails they signed up for, a poor sender reputation caused by bad list hygiene could be the culprit. Second, win-back campaigns, which are designed to re-engage inactive subscribers before they are removed, often contain aggressive discounts. An agent aware of list hygiene practices will recognize that a customer asking about a "last chance" offer may be responding to one of these win-back emails, providing crucial context for the conversation. The "What": A Support Agent's Guide to Common Automated Flows Automated flows are the engine of modern Shopify email marketing, responsible for a significant portion of a store's email-driven revenue. For a support team, each type of flow generates a predictable set of customer questions. Understanding these common flows is like having a cheat sheet for diagnosing customer issues. The most essential is the Welcome Flow, a series of emails sent to new subscribers. This is often their first direct interaction with the brand post-signup, and it typically includes an introductory discount in the first email, followed by brand-story content and social proof in subsequent emails. Support tickets from this flow usually involve the new subscriber discount code not working or questions about the brand story mentioned in the emails. The Abandoned Cart Flow is another critical automation, triggered when a shopper adds items to their cart but leaves without purchasing. These emails are designed to recover the sale, often with a sequence of reminders, with the first typically sent shortly after abandonment for optimal results, and sometimes a small discount. Agents will see tickets from customers who were distracted and just need a link back to their cart, or from those questioning why they're being "followed" by a product. Knowing this is an automated reminder helps the agent frame it as a helpful nudge, not an error. Two other flows frequently create support inquiries. The Post-Purchase Flow is a sequence sent after a customer completes an order. These emails are not just simple receipts; they often include shipping updates, product care instructions, requests for reviews, and cross-sell recommendations for related products. For instance, a customer who buys a leather handbag might receive an email a week later with care instructions and an offer for leather conditioner. Post-purchase emails have incredibly high engagement, with open rates that can exceed 40%, far higher than typical marketing campaigns. A customer asking for tracking information or how to use their new product is likely interacting with this flow, and an agent who knows this can point them to the email they already received. Finally, the Win-Back Flow targets customers who haven't purchased or engaged in a long time (e.g., 90 or 180 days). Its goal is to reactivate interest, usually with a compelling offer like "25% off, just for you." These campaigns can be highly effective, with research showing that 45% of recipients who get a win-back email will read future messages from the brand. When a loyal, active customer contacts support asking for the same discount their friend received from a "We miss you" email, the agent's understanding of the win-back flow's purpose, to prevent churn, is essential to explaining the policy without alienating a good customer. Measuring What Matters: Email Metrics That Impact Support Marketing teams live by their metrics, but these numbers are not just internal performance indicators; they are direct measures of the customer experience that often predict future support tickets. The most well-known metric is the Open Rate, the percentage of recipients who open an email. However, due to Apple's Mail Privacy Protection (MPP), which preloads email content and tracking pixels, this metric has become artificially inflated and unreliable. With Apple Mail accounting for roughly 49% of all email opens, this feature has a massive impact on data accuracy. MPP automatically reports many emails as "opened" via a proxy server, even if the user never viewed them, making it a poor gauge of actual engagement. This means a significant portion of "opens" are generated by Apple's servers, not human readers. While a healthy reported open rate for an e-commerce brand might fall in the 30-35% range, a sudden drop could still signal a deliverability problem, meaning emails are going to spam, which will inevitably lead to customers contacting support to ask why they missed an order confirmation or shipping notification. Because of MPP, support agents should know that open rates are no longer the true measure of whether a customer saw an email. Because of this shift, many marketers now focus more on the Click-Through Rate (CTR), the percentage of recipients who click on a link within the email. This is a much stronger and more reliable signal of engagement, as MPP does not affect click tracking. An average CTR for an ecommerce campaign might be around 2-3%, while for highly relevant flows it can be 5% or higher. The ultimate goal, however, is the Conversion Rate, the percentage of email recipients who make a purchase. For ecommerce, this can be quite low for general newsletters, sometimes under 1%, but can be significantly higher for highly targeted flows like abandoned cart or win-back emails. A campaign with a high open rate, a high click rate, but a very low conversion rate often points to a problem on the website itself, such as a broken checkout page or a discount code that fails when applied, precisely the kinds of issues that land in the support queue. The final key metric is the Unsubscribe Rate, which should ideally be kept below 0.5%. A high rate is a clear sign that the marketing team is sending too frequently or that the content is not relevant, leading to customer annoyance that can easily spill over into support interactions. Advanced Tactics: How A/B Testing Can Create Confusion One final concept from the marketing world that directly impacts support teams is A/B Testing, also known as split testing. This is the practice of sending two or more different versions of an email to a small portion of the audience to see which one performs better before sending the winning version to the rest. Marketers test everything: subject lines ("15% Off Inside" vs. "A Gift For You"), discount offers (percentage off vs. dollar amount), hero images, and call-to-action button copy ("Shop Now" vs. "Claim My Discount"). For example, a store might test a "15% Off" offer (Version A) against a "$10 Off" offer (Version B) on a new product to see which one generates more sales. To do this, a portion of the audience is divided, with each group seeing a different version. Once a winner is determined based on clicks or conversions, the more effective version is sent to the rest of the email list. This is a powerful optimization technique, but it can be a source of significant confusion for customers and support agents alike if the context is missing. Imagine two friends, Maria and Jen, who both receive a promotional email from your store on the same day. Maria gets the 15% discount, and Jen gets the $10 discount. They talk to each other, and Jen contacts support, feeling she received an inferior offer. Without an understanding of A/B testing, a support agent might assume there's been a mistake or that one of the customers is misinformed. The agent might waste time trying to find a "correct" offer that doesn't exist, or worse, escalate the issue unnecessarily, creating a poor experience. An agent who knows that A/B testing is a standard practice can confidently explain that the store is running a test to see which offers customers prefer. This knowledge transforms a confusing and potentially frustrating situation into a transparent and understandable one. It allows the agent to explain the "why" behind the inconsistency, "We are always trying to learn what our customers find most valuable, and sometimes that involves testing different promotions", reinforcing the brand's credibility instead of undermining it. For a support team, knowing that variation is sometimes intentional is a critical piece of operational context that empowers them to de-escalate and educate. Ultimately, these terms are more than just marketing vocabulary. They are the building blocks of the automated and manual communications that shape your customer's experience. When a support team understands the difference between a campaign and a flow, or the purpose of a VIP segment, they are better equipped to handle the resulting conversations with context and confidence. From the first welcome email to a potential win-back offer years later, these marketing touchpoints form the primary narrative of your brand for many customers. This shared language reduces friction, shortens resolution times, and allows for a more cohesive strategy across departments. Tools that manage customer conversations, like Arbyn, operate most effectively when they are built on a foundation of clear, consistent store policies. Defining who gets what offer, and when, is a store-wide decision, and this glossary provides the framework for that alignment. When your entire team speaks the same language, you can move from just answering questions to creating a truly seamless customer journey. If your team is ready to stop guessing and start resolving, you can add it to your store and build a single source of truth for your support conversations. --- ## Pricing - **Arbyn Starter** - $0/month, permanently free. 150 conversations / month. Resets 1st of each month. - **Arbyn Growth** - $59/month flat. 500 conversations / month. Resets 1st of each month. Or $600/year (just under two months free, saves $108, 15% off). - **Arbyn Agent** - $99/month flat. Unlimited conversations. Or $990/year (two months free, saves $198, 17% off). - **There is no trial.** Billing starts immediately on any paid plan. The free Arbyn Starter plan is permanent. - The conversation cap is the only difference between plans. There is no feature gating. ## Channels Live today: **support email** and **on-site live chat**. That is the complete list. SMS, Instagram DMs, Facebook Messenger, WhatsApp and Voice are on the roadmap and are NOT live. Arbyn does not edit orders or change line items. Money-moving actions (cancel, refund, discount, gift card, reship, return) require the store owner's approval, and then Arbyn performs them. Running them fully autonomously is a beta authorization and is in development. Shipping address changes are already autonomous. ## What Arbyn does on a Shopify order - **Change the shipping address**: Live. Arbyn does this on its own. Arbyn updates the shipping address on the Shopify order itself, inside the conversation, and writes the change to the order timeline. - **Cancel an order**: Live. You approve it, then Arbyn cancels the order. Anything that moves money waits for the store owner's approval. That is a deliberate control, not a missing feature. Once you approve, Arbyn fires Shopify's order cancellation itself and confirms it to the customer. - **Issue a refund**: Live. You approve it, then Arbyn issues the refund. Arbyn prepares the refund against the original payment method and sends it to you. On approval it files the refund in Shopify. You can cap the value it is allowed to prepare, per channel. - **Apply a discount**: Live. Arbyn creates a real Shopify discount and applies it to the cart, handing the shopper a checkout with the code already on it. It can also issue a discount code on an order once you approve it. - **Send a gift card, or reship an order**: Live. You approve it, then Arbyn does it. Arbyn creates the gift card, or raises the replacement order, in Shopify once you approve. - **Start a return**: Live. You approve it, then Arbyn opens the return. Arbyn opens the return in Shopify on your approval. - **Look up a gift card or store-credit balance**: Live. Arbyn does this on its own. "Do I have store credit left?" is a question most support tools answer with a human. Arbyn reads the balance itself, for a verified customer or from the code they give you, and reports the masked card, the balance and the expiry. If there is no card, it says so rather than guessing. - **Handle a subscription question**: Live. You choose what it does. Arbyn knows which of your products are sold as a subscription, shows that on the product card in the conversation, and sends a subscriber to their subscription management page to pause, skip or cancel. It answers how your subscriptions work from your own knowledge, but it does not read an individual customer's contract, so it will not state their renewal date or status. Most cancels are a customer with product piling up, and the fix is getting them to the page where they can slow the cadence down. Reading the contract itself is on the roadmap. - **Answer support email and live chat**: Live. Arbyn reads every inbound support email and every chat, works out the intent, pulls the live Shopify context, and replies in your brand voice. Money-moving actions (cancel, refund, discount, gift card, reship, return) require the store owner's approval, and then Arbyn performs them. Running them fully autonomously is a beta authorization and is in development. Shipping address changes are already autonomous.