An email and SMS customer journey should follow the customer's situation, not two separate sending calendars. Someone who has just completed a Shopify order should not receive a text asking them to finish that purchase. Map the event, the useful next message, and the exit rule together so that each channel adds something and the sequence knows when to stop.
Draw the journey before opening the editor
Write down the event that begins the journey, what the customer needs, and what success looks like. For checkout recovery, success is a completed purchase. For a review request, success is an honest review after enough time to use the product.
Add the conditions that should prevent a message. These might include a completed order, an unsubscribe, an ineligible phone number, or an offer that no longer applies. Use Sendvio's confirmed automation presets as the starting point rather than assuming every behavior on your site can trigger a message.
Map one journey from event to exit
Take a refillable household product. The relevant event is a qualifying purchase, the later need is replenishment, and the exit is a subsequent purchase or loss of eligibility. The journey map should include the product, the expected usage interval, the message, the channel permission, and the condition checked before sending.
An illustrative plan might use an email near the expected refill period with advice on choosing the right quantity. A later SMS, only for eligible subscribers, could offer a convenient return link. Those delays must come from the product's use and the store's purchase history; they are not interchangeable with the timing of checkout recovery or a review request.
Record what happens when the customer bought several units. They may not need the same reminder as someone who bought one. If the available data cannot support that distinction reliably, use tentative wording such as “Ready for a refill?” instead of asserting that the customer has run out. The copy should reflect the certainty of the rule behind it.
Give each channel a reason to appear
Email can explain options or answer a concern. SMS can make a timely next step convenient for subscribers who have asked for texts. Avoid using SMS simply because a person did not open an email; open tracking is imperfect, and the missing open does not establish channel permission.
For a reorder journey, an email might explain the typical replacement interval and link to the correct product. A later eligible SMS could provide a concise reminder. Check for a new purchase before continuing, and give customers a clear way to stop marketing on either channel.
Write a priority rule for competing messages
A customer can qualify for a refill reminder, a promotion, and a thank-you in the same week. Choose which message has the strongest reason to arrive. Necessary service information and the customer's explicit requests need their own treatment; a generic promotion may be the easiest message to move or exclude.
Document the decision in practical terms: “If a customer purchases the refill before the next reminder, stop the sales reminder. If the scheduled promotion offers the same item, review whether the reminder adds anything.” Then translate that policy into the audience conditions and schedules your account supports. Writing the rule does not by itself make it automatic.
Keep a simple ownership map as well. Someone should know which automation sends each message and who can pause it. Cross-channel problems often persist because the email and SMS are reviewed by different people, each looking only at a reasonable individual message.
Test people, not just individual messages
Create a small scenario sheet: email-only subscriber, SMS-only subscriber, subscriber to both, customer who purchases during a delay, and customer who opts out. Walk each through the configured journey and record which messages they should receive.
Review the campaign calendar alongside the automation. A major sale can overlap a perfectly reasonable reorder reminder. Adjust the audience or schedule so the total experience remains sensible. After launch, investigate unexpected combinations before changing copy. The most useful improvement may be removing a redundant message rather than adding a more persuasive one.
For the purchase-during-delay scenario, record an expected result before testing: the customer receives no later refill sales reminder for the purchase they just made. For an email-only subscriber, the SMS step must not create eligibility. For someone who opts out of one channel, verify that channel's future treatment instead of assuming every permission changes together.
After launch, review a few complete customer timelines, including exclusions and skipped steps. If the observed sequence differs from the plan, investigate conditions, data timing, and overlapping campaigns before editing the headline. A well-coordinated journey feels simple to the customer because the decisions behind it are explicit, testable, and maintained as the store changes.