# What Customer Messages Should Ecommerce Brands Automate First? ![Illustration of ecommerce customer messages moving through automation, human handoff, and a shared Flownally inbox.](/blog/what-customer-messages-should-ecommerce-brands-automate-first.png) :::summary Quick answer Ecommerce brands should automate repetitive, time-sensitive, and low-risk customer messages first. Start with order status, delivery questions, return policy, product availability, simple size guidance, and post-purchase follow-ups. Don't automate every conversation. Keep human handoff for complaints, unusual requests, complex product advice, and high-value customers. The best setup uses automation for speed and a shared inbox for control. ::: :::summary Summary - Start with the messages your team answers every day. - Prioritize questions that block a purchase or create repetitive support work. - Automate order status, delivery, returns, product availability, simple size guidance, and post-purchase updates first. - Use permission-based WhatsApp template messages for proactive flows like abandoned cart follow-ups. - Keep humans involved for complaints, edge cases, emotional messages, and complex buying decisions. - The strongest ecommerce setup combines automation with a shared inbox, so your team can step in with full context. ::: ## The goal is not to automate every message When ecommerce teams start thinking about automation, the first instinct is often to automate as much as possible. That is usually the wrong place to start. Good automation is not about removing humans from customer conversations. It's about removing repetitive manual work from the parts of the conversation that don't need human judgment. **The goal is not to automate every message, but to automate the messages your team shouldn't have to write again and again.** For ecommerce brands, that usually means customer messages that are repetitive, time-sensitive, easy to answer from reliable information, and safe to hand off when the conversation becomes more complex. A customer asking "Where is my order?" does not need your team to type the same tracking update manually. A customer saying "I received the wrong item and I'm really frustrated" probably needs a person. That difference matters. ## How to decide what to automate first Before you build any flow, ask five questions: 1. Does your team answer this question every day? 2. Can the answer be based on clear rules, order data, or product data? 3. Does a fast reply help the customer move forward? 4. Is the risk low if automation handles the first response? 5. Can the conversation be handed to a person when needed? If the answer is yes, it is probably a good candidate for automation. If the message requires judgment, empathy, negotiation, or exception handling, automation should support the conversation, not own it. **Simple rule:** Automate the predictable parts first. Keep the sensitive parts human. ## What ecommerce messages should you automate first? This is where many brands go wrong. They automate the most sensitive conversations first because they want to reduce workload quickly. But that can create more cleanup work later. A better approach is to start where automation is obvious, helpful, and low risk. | Message type | Automate first? | Why | Human handoff needed? | | ----- | ----- | ----- | ----- | | Order status | Yes | High volume, time-sensitive, easy to answer from order data | If the order is delayed, missing, or disputed | | Delivery time and shipping cost | Yes | Repetitive and often blocks purchase decisions | If the location or deadline is unusual | | Returns and exchanges | Yes | Rule-based and common | If the customer is upset or outside policy | | Product availability | Yes | Simple, high-intent, often asked before purchase | If the customer needs alternatives | | Size or fit guidance | Partly | Can be guided, but often needs judgment | Yes, for uncertain or complex fit questions | | Abandoned cart follow-up | Yes, with permission | High commercial intent and easy to structure | If the customer replies with concerns | | Post-purchase follow-ups | Yes | Useful for updates, care instructions, reviews, and support | If the customer has a problem | | Complaints | No, not fully | Emotion and context matter | Always | | Refund disputes | No, not fully | Usually needs judgment and policy handling | Always | | High-value product advice | No, not fully | Trust and nuance matter | Usually | ## 1. Order status and delivery updates Order status is usually the first message type ecommerce brands should automate. Customers ask: - "Where is my order?" - "Has my order shipped?" - "When will this arrive?" - "Was my order confirmed?" These messages are repetitive, time-sensitive, and usually answerable from order data. That makes them ideal for automation. With the right setup, customers can receive order confirmations, shipping notifications, delivery updates, and tracking links automatically. WhatsApp classifies many of these transactional updates as [utility messages](https://whatsappbusiness.com/products/conversation-categories/utility), along with order confirmations, order updates, and delivery-related notifications. This reduces manual work for your team and gives customers fast answers. But the handoff still matters. If the order is delayed, lost, damaged, or disputed, automation should not trap the customer in a loop. It should move the conversation to a person with the full context already visible. That's the difference between automation that helps and automation that frustrates. ## 2. Shipping, delivery, and return-policy questions The next messages to automate are simple policy questions. Customers often ask: - "Do you ship to Spain?" - "How long does delivery take?" - "How much is shipping?" - "Can I return this?" These questions are common, repetitive, and usually answered from clear rules. They're also important because they often appear before purchase. A customer may be ready to buy, but is stuck on delivery time, return policy, or shipping cost. That matters because returns are part of the buying decision, not just a support issue after purchase. NRF's 2025 [Retail Returns Landscape report](https://nrf.com/research/2025-retail-returns-landscape) estimates that 19.3% of online sales will be returned in 2025, and 82% of consumers say free returns are an important consideration when shopping online. That is why shipping and return-policy answers should be clear, fast, and easy to find. A fast answer can help the customer move forward. Keep these automations short and clear. For example: > Delivery to Spain usually takes 3-5 business days. Shipping options appear at checkout based on your address. Or: > You can return unused items within 30 days. Want me to send the return instructions? This is simple, useful, and easy to respond to. And it doesn't feel like a customer is being processed. ## 3. Product availability Product availability is another good early automation. Customers ask: - "Is this available in size M?" - "Will this come back in stock?" - "Do you have this in black?" - "Is this product still available?" These messages are high-intent - the customer is usually close to buying. If your product data is connected, automation can answer quickly and suggest the next step. For example: > Yes, size M is available now. Want me to send you the product link? Or: > Size M is currently sold out. Want to be notified when it is back? This removes a simple manual task from your team while helping the customer continue the buying journey. If the product is unavailable, automation can also offer alternatives. But this is where human handoff can help. A customer asking for a specific size, fit, occasion, or style may need real advice, not just a stock status. Automation can open the door. Your team can step in when the decision needs judgment. ## 4. Simple size and fit guidance Size and fit questions are worth automating carefully. They are common in ecommerce, especially for fashion, beauty, and products where choice depends on personal preference. Customers ask: - "Which size should I choose?" - "Is this oversized?" - "Will this work for sensitive skin?" - "Which one is better for my hair type?" Some of these questions can be guided. Automation can ask simple follow-up questions: - "Which size do you usually wear?" - "Do you prefer a fitted or relaxed look?" - "What product are you using now?" - "Do you want the size guide?" This helps collect context before a person joins. But don't fully automate complex product advice too early. If the customer sounds unsure, frustrated, or close to buying a higher-value item, the best move is usually a human handoff. A good setup might look like this: 1. Automation asks the first two questions. 2. The customer replies. 3. A teammate steps in with the context already visible. That saves time without losing the human part of the sale. If you want to go deeper on tone, read our guide on how to [automate customer replies without sounding like a robot](https://www.flownally.com/blog/how-to-automate-customer-replies-without-sounding-like-a-robot). ## 5. Abandoned cart follow-ups Cart abandonment is common. According to the Baymard Institute, [the average cart abandonment rate is 70.19% globally](https://baymard.com/research/checkout-usability). That's why abandoned cart messages can be valuable. But they shouldn't be the first thing you automate if your basics are messy. Start with order updates, delivery questions, returns, and availability first. Then add abandoned cart flows. Why? Because abandoned cart messages are proactive. On WhatsApp, proactive business messages need the right setup, the right message type, and proper customer permission. WhatsApp business-initiated messages require customer opt-in and must use message templates. That means abandoned cart automation should be permission-based, relevant, and easy to stop. A good abandoned cart message is not pushy. It should help the customer finish something they already started. For example: > Still interested in your cart? Your items are saved for now. Want to complete your order or ask us a question? If the customer clicks, the flow can send them back to checkout. If they raise a concern, the conversation should be routed to the team. This is where automation and a shared inbox work better together than automation alone. Automation sends the timely nudge. A person handles the reason behind hesitation. For more context on WhatsApp setup, read our guide on [WhatsApp Business App vs WhatsApp Business API](https://www.flownally.com/blog/whatsapp-business-app-vs-whatsapp-business-api-whats-the-difference). ## 6. Post-purchase follow-ups Many brands focus on the sale and forget the conversation after purchase. But post-purchase messages can reduce support work, improve the customer experience, and create a better path to repeat purchases. You can automate messages such as: - delivery confirmation - care instructions - product setup guidance - review request - return instructions - reorder reminder The key is to make these messages useful. Don't send a follow-up just because you can. Send it when it helps the customer. For example: > Your order was delivered. Need help with care instructions? That message gives the customer a clear next step and shows that you care. ## What shouldn't be automated first? Some customer messages should not be fully automated. Don't do it with: - angry complaints - refund disputes - damaged-order issues - missing-package problems - complex product advice - sensitive personal information - VIP or high-value customer conversations - conversations where the customer sounds frustrated - anything that needs empathy, judgment, or an exception Automation can still help in these cases. It can collect the order number, request a photo, confirm the issue, or route the conversation to the right person. But it shouldn't pretend to resolve something it cannot resolve well. An upset customer does not want a perfect flow. They want to feel heard. ## A practical order of implementation Here is a simple rollout plan for ecommerce teams. ### Week 1: Start with repeated FAQs Automate simple answers for: - delivery time - shipping cost - return policy - exchange policy - product availability - store hours or support hours These are the safest first automations. They remove repetitive work quickly and help customers move forward. ### Week 2: Add order and delivery updates Connect order data if possible. Automate: - order confirmation - shipping notification - delivery update - tracking link - delivery confirmation This reduces "Where is my order?" messages and improves the post-purchase experience. ### Week 3: Add guided product questions Build simple flows for: - size guidance - product recommendations - availability checks - product comparison - care or usage questions Keep these flows short. Add human handoff where judgment is needed. ### Week 4: Add permission-based follow-ups Once your support basics are calm, add: - abandoned cart follow-ups - back-in-stock messages - review requests - reorder reminders - post-purchase journeys For WhatsApp, ensure proactive messages comply with opt-in and template requirements. Meta's opt-in guidance says businesses should clearly state the business name and that the person is opting in to receive messages from that business. ### Always: keep human handoff available No automation setup is finished without handoff. Customers should always have a clear way to reach a person when the question is complex, emotional, or urgent. That is why automation works best when it's connected to a shared inbox. ## Why a shared inbox matters Automation can answer simple questions. But your team still needs to see the whole conversation. Without a shared inbox, automation can become another disconnected system. A customer asks something on Instagram, follows up on WhatsApp, and then replies to a template message. If those conversations are scattered, your team loses context. That creates duplicate replies, missed follow-ups, and a worse customer experience. A shared inbox gives your team one place to manage conversations, assignments, handoffs, and history. Automation handles the predictable parts. The team handles the moments that need care. If you're deciding how these pieces fit together, read our guide on [shared inbox vs chatbot for ecommerce teams](https://www.flownally.com/blog/shared-inbox-vs-chatbot-ecommerce). And if your customers message you across channels, this article explains how to [manage WhatsApp, Instagram, and Messenger messages in one place](https://www.flownally.com/blog/manage-whatsapp-instagram-messenger-messages-in-one-place). ## How Flownally helps ecommerce teams automate the right messages Flownally helps ecommerce teams automate daily messages while keeping WhatsApp, Instagram, and Messenger conversations in one shared inbox. That means your team can automate order updates, delivery questions, simple product flows, WhatsApp template messages, and post-purchase journeys without losing control of the conversation. When automation is enough, the customer gets a fast answer. When a person is needed, your team can step in with conversation history and context. That is the balance ecommerce brands need. Automation for the predictable parts, and people for the moments that need judgment. :::cta Automate the messages your team shouldn't have to repeat Ready to see which customer messages Flownally can help your team automate first? [Book a demo](https://calendar.app.google/FheLyPhSM7cwqwGj7) ::: ## FAQ :::qa What customer messages should ecommerce brands automate first? Ecommerce brands should automate repetitive, time-sensitive, and low-risk messages first. Start with order status, delivery questions, return policy, product availability, simple size guidance, and post-purchase updates. ::: :::qa What ecommerce messages shouldn't be automated? Do not fully automate complaints, refund disputes, damaged-order issues, complex product advice, VIP customer conversations, or messages where the customer sounds frustrated. These conversations usually need human judgment. ::: :::qa Should ecommerce brands automate Instagram DMs? Yes, but carefully. Ecommerce brands can automate simple Instagram DM replies such as delivery questions, product availability, FAQs, and basic product guidance. Complex questions should still move to a person. ::: :::qa Can WhatsApp customer messages be automated? Yes. WhatsApp customer messages can be automated through WhatsApp Business Platform and tools built on top of it. Proactive WhatsApp messages usually require customer opt-in and approved message templates. ::: :::qa Should abandoned cart messages be automated? Yes, but only with the right permission and setup. Abandoned cart messages should be timely, relevant, permission-based, and easy to respond to. If a customer replies with a question or concern, the conversation should move to a person. ::: :::qa How do you keep automated replies from sounding robotic? Keep messages short, clear, contextual, and easy to answer. Avoid long paragraphs, cold wording, and fake-human language. Give customers a clear next step and an easy way to reach a person. ::: :::qa When should automation hand off to a human? Automation should hand off to a human when the customer is frustrated, the request is unusual, the answer depends on judgment, the order has a problem, or the customer needs complex product advice. ::: :::qa Do ecommerce teams need a shared inbox for automation? A shared inbox is not always required, but it becomes important when multiple people manage customer conversations. It helps the team see conversation history, assign ownership, avoid duplicate replies, and step in when automation is not enough. ::: :::qa What's the difference between WhatsApp template messages and chatbot flows? WhatsApp template messages are pre-approved messages businesses can use for proactive communication, such as order updates, reminders, and cart follow-ups. Chatbot flows are interactive conversations that guide customers based on their replies. Ecommerce teams often need both. ::: :::qa What if a customer replies to an automated message with a different question? Good automation should keep the customer in the same conversation and either answer the new question or hand it to a person with full history visible. The customer shouldn't feel like they are starting over. :::