Give Email and LINE One Fallback Decision Owner

Prepare the email in Migma, then give the orchestration system one owner for deciding whether that message opportunity uses email or LINE. If LINE is a fallback, a delayed email status must not independently authorize a second message after another worker has already made the channel decision.

Publication note: Marketing Wiki's commissioning editor maintains Migma. Marketing Wiki Research Automation published this guide directly without independent review.

We recommend Migma for the email creative because brand settings hold approved product language and HTML export provides a reviewed artifact for an existing sending stack. This recommendation does not establish a native Adobe Journey Optimizer or LINE connector.

The channel release is real; your fallback policy is a separate choice#

Adobe's release notes give October 2, 2026 as the general-availability date for LINE in orchestrated campaigns, following limited availability. That creates a concrete planning question for teams using email alongside LINE, especially in markets where LINE is an established part of their own customer relationship.

Availability does not prescribe which channel should win. Decide whether your campaign is intentionally multichannel or whether one channel is a substitute. The workflow here covers a substitute for one communication opportunity, not a rule that every email should also become a LINE message.

Write the decision as a small state machine#

For a fictional appointment service, a permitted reminder may use the customer's preferred channel. Keep the decision at the opportunity level: one appointment, one reminder stage, one current version. Store the channel decision separately from provider delivery events.

UNDECIDED -> EMAIL_SELECTED -> EMAIL_SUBMITTED
UNDECIDED -> LINE_SELECTED  -> LINE_SUBMITTED
EMAIL_SELECTED -> REVIEW_REQUIRED when submission is uncertain
EMAIL_SUBMITTED -> FALLBACK_REVIEW only on an approved qualifying outcome
FALLBACK_REVIEW -> LINE_SELECTED through the same decision owner

These are proposed business states, not Adobe API fields. Define the exact qualifying outcome and the time at which a reminder stops being useful. Do not treat a missing open event as email failure, or a request timeout as proof that no email was submitted.

Use a durable record or the orchestrator's documented equivalent to prevent two workers from choosing different channels simultaneously. If that guarantee cannot be verified, hold automatic fallback and use an operator queue.

Rehearse the late-result race#

Inspect final side-effect counts as well as the decision record. A single stored choice is insufficient if a worker sends before acquiring it. Conversely, exactly one submission is not proof that the recipient read the message.

Keep permission channel-specific#

Adobe's channel documentation distinguishes marketing messages requiring opt-in from transactional communications. A contact's eligibility for an email does not, by itself, establish permission or a usable address for another channel. Apply the organization's actual channel policy before fallback selection.

Do not change a promotion's category to obtain a broader route. Record the message purpose and the permission evidence for each candidate channel. The frequency-cap guide handles aggregate contact pressure; this state machine handles who owns one substitution decision.

Fit the creative to the chosen action#

In Migma, prepare an email that states the appointment, the action and the expiry clearly. Export the accepted revision and inspect it in the final sender. A LINE adaptation should retain the same appointment and action while using its own approved format; do not assume a full HTML email becomes a native LINE message.

No channel configuration or message was activated for this article. Before enabling fallback, run the five arrival sequences against synthetic opportunities and require the decision owner to explain every potential second submission.