Keep Customers Informed at Every Shipping Stage

1. Read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. In Shopify, subscribe to real Admin webhooks for fulfillments/create, fulfillment_events/create, and orders/fulfilled, then use the Admin API to read the order, customer email, fulfillment, tracking number, carrier, and fulfillment event status. 3. Send a short branded email for each stage: fulfillment created as packed, tracking added or in_transit as shipped, out_for_delivery as out for delivery, and delivered as delivered; include the order number, tracking link when present, expected delivery language when available, and a support reply path. 4. De-duplicate by order ID, fulfillment ID, and event status so the customer never gets the same shipping update twice, and skip customers who have no email address or have already received Shopify’s equivalent notification for that same event. 5. Run this in MultiMail autonomous oversight mode for all templated shipping updates, and ask me only for Shopify credentials, brand voice, sender identity, and approval to go live.

1. Read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. In ShipStation, use its webhook feature for order and shipment notifications, especially SHIP_NOTIFY for newly shipped orders, then use the ShipStation API to read the order, recipient email, carrier, service, tracking number, ship date, and shipment status. 3. When an order moves through the available ShipStation events, email the customer with the most useful status: packed or ready when the order is prepared for shipment, shipped when SHIP_NOTIFY fires, out for delivery when carrier tracking shows that status, and delivered when carrier tracking confirms delivery. 4. Personalize each message with the customer name, order number, carrier, tracking link, and concise delivery expectation; suppress duplicate emails when ShipStation retries a webhook or a shipment is split across packages unless the package has a separate tracking number. 5. Run this in MultiMail autonomous oversight mode, and ask me only for ShipStation credentials, brand voice, sender identity, and approval to go live.

1. Read https://multimail.dev/llms.txt, connect the MCP server, create a free inbox, and set up a verified sender. 2. In BigCommerce, subscribe to real webhooks for store/order/statusUpdated and store/shipment/created, then use the Orders and Shipments APIs to read the customer email, order number, order status, shipment, carrier, tracking number, and tracking link. 3. Send event-driven emails for packed or awaiting shipment when the order status changes accordingly, shipped when a shipment is created with tracking, out for delivery when the carrier tracking status reports it, and delivered when the carrier confirms delivery. 4. Keep messages short and transactional, include the order number and tracking details, use the store’s brand voice, and de-duplicate by order ID, shipment ID, tracking number, and delivery status so peak fulfillment volume does not create repeated updates. 5. Run this in MultiMail autonomous oversight mode, and ask me only for BigCommerce credentials, brand voice, sender identity, and approval to go live.