SMS triggered by the real fulfillment event
A shipping confirmation text fires the moment your warehouse or 3PL actually hands off the package, not an estimate based on order date.
Mailchimp does offer SMS marketing, but it's a separate paid add-on with its own opt-in requirements, credit system, and country availability, not a built-in feature of every plan. It works well for a straight SMS blast or a simple automation off a purchase or signup; it runs into the same wall email automations do the moment the trigger lives outside Mailchimp.
SMS sending is priced on credits, purchased separately from your email plan, and consumed per message sent. Compliance is stricter than email too: every recipient needs explicit SMS-specific opt-in (an existing email subscriber isn't automatically opted in to texts), and availability is limited to a specific list of countries, the US and Canada most reliably.
Once someone's opted in, SMS can trigger off the same kinds of events email automations do: a signup, a purchase on a connected store, a specific tag being applied. You can mix SMS and email steps in the same automation or Customer Journey, sending a text follow-up a day after an email that didn't get opened, for instance.
An SMS confirming a shipment that hasn't actually shipped yet is worse than useless, it actively damages trust. Mailchimp's SMS, like its email automations, can only trigger off events it can see: a purchase on a connected storefront, a tag change inside Mailchimp. It has no way to know your warehouse just handed a package to a carrier unless that fact gets synced in.
We build that sync, so an SMS fires off the real shipping, renewal, or appointment event in your actual systems rather than an approximate trigger inside Mailchimp. Same approach as our Mailchimp automation work described on the automations page →, just applied to the channel where a wrong or late message is more visible and more annoying.
A shipping confirmation text fires the moment your warehouse or 3PL actually hands off the package, not an estimate based on order date.
SMS consent captured at checkout, in a loyalty program, or anywhere else outside Mailchimp syncs in as a real opt-in flag, so compliance doesn't depend on someone remembering to re-enter it.
If the trigger lives outside Mailchimp, that's a sync, not a limitation you have to accept.
Tell us what event your SMS automation is actually trying to react to, and where that event really happens. We'll connect it so the text goes out when the real thing occurs. SMS is one example; n-frames automates whatever's manual, any channel, any system.
Let's talk →Yes, as a separate paid add-on with its own credit-based pricing, distinct from your email plan. It supports standalone SMS campaigns and SMS steps inside automations, but it isn't included automatically with every Mailchimp subscription.
Pricing runs on purchased credits consumed per message, separate from your email send allowance. Exact rates depend on volume and country, so Mailchimp's own pricing page is the only reliable current source.
Not automatically. SMS requires its own explicit opt-in, separate from email consent, since text message marketing has stricter legal requirements. An email subscriber has to opt in to SMS specifically before you can text them.
Coverage is limited to a specific list of countries, most reliably the US and Canada, rather than every country Mailchimp supports for email. Check Mailchimp's current documentation before building an SMS program for an audience outside that list.
Yes, both channels can be steps inside the same Customer Journey or classic automation, so you can follow an unopened email with an SMS, or vice versa, based on the same underlying trigger.