Why does adding channels increase opt-outs faster than conversions?
Because app push alone cannot reach customers who uninstalled the app or turned off OS notification permissions, many teams progressively add Kakao AlimTalk, SMS/LMS, email, and in-app messages. Yet connecting channel tools without a shared governance rule quickly leads to a single customer receiving a cart push, a coupon SMS, and a promotional email on the same afternoon.
Multi-channel incidents typically happen at three points. First, a workflow fires a paid SMS or AlimTalk immediately without waiting long enough to confirm whether the app push arrived. Second, informational notices (orders, shipments) and promotional campaigns are mixed into the same fallback rule, causing regulatory violations or template blocks.[6] Third, a user enrolled in multiple concurrent Journeys bypasses per-campaign frequency limits.[1][2]
The objective of multi-channel CRM is not blasting every available channel. The core discipline is selecting the single most cost-effective, lowest-friction channel that matches the user's current reachability and message intent, and immediately canceling queued fallback channels once the goal is met.[1]
Diagnosing single-channel push delivery and comparing messaging operating models are covered in Why push says "Sent" but the customer never gets the notification and Should you run FCM directly or adopt a messaging platform like OneSignal?. Here we focus on channel fallback rules, webhook relay architecture, frequency capping, and consent synchronization when combining push, in-app, email, and domestic SMS/AlimTalk in one workflow.
Why must informational alerts and promotional campaigns split from step one?
The first step in multi-channel design is separating transactional or operational informational alerts from commercial promotional campaigns. Those two categories differ completely in expected delivery latency, statutory consent requirements, and permissible fallback channels.[6]
For example, a payment confirmation or password-reset alert must reach the customer via AlimTalk or SMS even if marketing push consent is off. Conversely, a first-purchase coupon or win-back promotion may only go to users who opted into marketing on that specific channel, and must never fall back to Kakao AlimTalk, which is strictly reserved for informational notices.[6]
| Message category | Typical business examples | Primary channel | Permitted fallback channel | Mandatory compliance check |
|---|---|---|---|---|
| Urgent informational and security | OTP codes, suspicious login alerts, payment or refund confirmation | AlimTalk or immediate push | Immediate fallback to standard SMS/LMS | Independent of marketing opt-in; minimize latency and verify vendor receipt |
| Standard informational and fulfillment | Shipment dispatch, booking reminders, upcoming subscription renewal notice | App push or AlimTalk | SMS or email on non-delivery | Strictly follow approved informational template; zero promotional copy |
| Action-driven promotional | Cart abandonment reminders, first-purchase perks, repeat-order coupons | App/web push + in-app message | Opted-in marketing email or promotional SMS | Channel-specific marketing consent, ad prefix and free opt-out, quiet hours |
| Content and relationship nurturing | Monthly usage summaries, feature digests, newsletters | Email or in-app feed | App push (digest summary) | Separate subscription preferences; avoid paid SMS fallback on non-open |
Adding even a single promotional discount line to an informational notice reclassifies the entire message as commercial advertising under Korean information-network regulations, subjecting it to prior opt-in and night-time sending restrictions.[6] Separate informational and promotional tracks at the template-approval stage before building journeys.
A consistent rhythm for planning and verified sending — Plan the campaign calendar, verify audiences before sending and use experiment results in the next operating plan.
How should you set the wait window before falling back from push to AlimTalk or SMS?
Implementing "send an app push, and if unread, send an SMS" without a careful wait model causes most users to receive both. The timestamp when your server hands a request to FCM or APNs (Sent), the timestamp when the device confirms receipt (Confirmed Delivery), and the timestamp when the user taps the notification (Clicked) measure different stages.[3]
When a user is in a meeting or has their screen off, a push notification that arrived cleanly on the device may not be opened for hours. Fallback rules should therefore distinguish immediate routing based on subscription state from delayed fallback after delivery or conversion checks.[1][3]
- No active push subscription at entry (immediate branch): If the user has no valid push subscription or OS notifications are disabled at journey entry, branch immediately to the next permitted channel (email or opted-in SMS/AlimTalk) without waiting.[5]
- Push sent but device delivery unconfirmed (short wait before fallback): For time-sensitive informational notices where reach matters, wait a short window and fall back if
Confirmed Deliveryis not recorded or the token returns invalid.[3] - Push delivered but target action incomplete (extended wait before fallback): For promotional journeys such as cart reminders or expiring coupons, insert a wait step of several hours to a day and trigger a secondary channel only if the purchase or conversion event still has not occurred.[1]
Architectural patterns for suppressing queued messages as soon as a purchase completes are covered in Why customers who already bought still get cart reminders.
How do you connect OneSignal Journeys webhooks to Korean SMS and AlimTalk vendors?
The OneSignal solution provides app/web push, in-app messaging, email, and global SMS natively, while allowing Journey webhook steps to pass user attributes and event context to external HTTP endpoints.[1][4] To keep existing contracts with Korean domestic SMS/LMS or Kakao AlimTalk/FriendTalk vendors while orchestrating unified journeys, placing a lightweight relay server behind the Journey webhook is the most reliable pattern.
Routing webhooks through an internal relay server rather than calling vendor APIs directly lets you centralize credential protection, payload translation, just-in-time consent re-verification, and duplicate-send prevention.[4]
| Relay layer control | Why it is required | Recommended implementation | Behavior on failure or exception |
|---|---|---|---|
| Webhook authentication and signature check | Prevent unauthorized external requests from draining SMS/AlimTalk budget | Verify dedicated auth headers/secret tokens and restrict allowed routes | Reject immediately with 401/403 and raise a security alert |
| Idempotency key enforcement | Prevent duplicate SMS sends when network latency triggers webhook retries | Enforce uniqueness on journey_id + step_id + external_id + date_bucket | Return the cached result without re-calling the vendor if key exists |
| Just-in-time consent and exit re-check | Account for purchases or opt-outs that occurred during a journey wait step | Query latest order status, marketing opt-in, and KST quiet hours in DB | Log suppression reason and complete the webhook step cleanly |
| Vendor response and fallback collection | Feed AlimTalk-to-SMS fallback outcomes and delivery status back into CRM | Persist vendor receipt IDs and ingest delivery callbacks as events | Retry transient vendor errors or isolate template and phone-number errors |
Decouple webhook acknowledgement latency from vendor dispatch queues
When a large segment hits a Journey webhook step simultaneously, tens of thousands of HTTP requests arrive within seconds. If the relay server waits synchronously for the external SMS or AlimTalk vendor API to finish each call, webhook timeouts occur and automatic retries multiply the load.[4]
Have the relay endpoint validate the payload and idempotency key, persist the job to an internal dispatch queue, and return 200 promptly, while background workers call the vendor API within contracted rate limits. Detailed channel and data integration guides are available in the OneSignal Channels Guide and Integration Guide.
How do you align frequency caps and campaign priority across concurrent journeys?
As lifecycle automation matures, a single customer can easily qualify for an onboarding journey, a cart-abandonment journey, and a seasonal category blast on the same day. Each campaign owner sees one message per day, but the customer experiences three notifications.
OneSignal's Frequency Capping controls the maximum number of messages a user can receive within a time window and the minimum gap between sends.[2] In practice, three additional rules keep frequency control watertight:
- Exempt transactional and informational notices from marketing caps: Reaching a promotional push limit must never block an order receipt or shipping notice. Apply frequency caps to promotional and reminder campaigns while routing transactional alerts through an exempt path.[2]
- Order campaigns by conversion contribution: When the daily cap is one message, sending a low-priority sitewide announcement first blocks a high-converting cart reminder later that day. Prioritize behavioral lifecycle triggers first, following the framework in Which lifecycle campaign should you automate first: first purchase, repeat purchase, or win-back?.
- Share fatigue state between native channels and webhook channels: Record the latest promotional send timestamp (
last_marketing_sent_at) in user attributes or the relay database so a customer who already hit today's push cap does not receive an extra promotional SMS via webhook.[4][5]
You can structure entry, exit, and frequency-cap rules across campaigns using the OneSignal Journey Workbook.
Messages connected to customer behavior — Use lifecycle stages and behavior to connect channels and timing, then refine journeys through experiments.
How should you synchronize night-time quiet hours and per-channel consent?
Article 50 of Korea's Information and Communications Network Act requires separate prior consent to send commercial advertising between 21:00 and 08:00 KST, and mandates clear (Ad) labeling, sender identification, and a free opt-out mechanism on channels such as SMS and email.[6]
If a journey simply uses a relative Wait 6 hours step after a 17:00 KST cart event without a timezone window guard, the promotional push or SMS fires at 23:00 KST.
| Control area | Common design gap | Recommended governance standard | Evidence to verify |
|---|---|---|---|
| Night-time ad restriction (21:00–08:00 KST) | Relative 6-hour wait fires promotional push or SMS late at night | Enforce a KST daytime send window in both Journey steps and the relay server | Logs showing night-time arrivals deferred to 08:00 KST or suppressed |
| Per-channel marketing consent separation | Treating app-push opt-in as permission to send promotional SMS or email | Store push, email, SMS, and FriendTalk marketing consent as distinct attributes | Customer profile audit trail with per-channel consent flags and timestamps |
| Bidirectional opt-out synchronization | 080 toll-free SMS unsubscribes or profile changes lag behind CRM segments | Update application DB and messaging platform subscription state immediately | Reconciliation log comparing opt-out timestamp against subscription disable time |
| Shared-device and logout identity isolation | Previous user's marketing push appears on a shared device after logout | Decouple external_id binding/unbinding rules from device subscription state | Test logs verifying account-switch and logout subscription behavior |
Aligning customer identifiers, events, and attributes is detailed in Why you adopted CRM but cannot launch campaigns: checking events, attributes, and identifiers first, and preserving subscription states during platform transitions is covered in How to preserve customer identifiers, subscription state, and campaigns when switching CRM tools.
Which multi-channel QA scenarios must run before launching a campaign?
Proofreading message copy alone cannot prevent multi-channel delivery incidents. Before activating a journey for live customer segments, run five boundary scenarios with test accounts.
| QA scenario | Test condition | Expected result | Verification method |
|---|---|---|---|
| Suppress fallback when push arrives | Enter journey with a test device that has push notifications enabled | Only 1 app push arrives; AlimTalk/SMS webhook is never called after wait | Compare Journey execution history against relay server request logs |
| Immediate exit upon purchase during wait | Trigger order-completed event while test user sits in pre-SMS wait step | Journey exit rule fires and queued reminder SMS is canceled | Match order event timestamp against Journey exit log |
| Quiet-hour deferral at night | Enter a 6-hour wait promotional journey at 16:00 KST (due at 22:00 KST) | No message sends at 22:00 KST; delivery holds until after 08:00 KST next day | Inspect Journey wait state and relay server time-window guard logs |
| Deduplicate retried webhook calls | Send the identical Journey step webhook payload twice to the relay server | First request dispatches to vendor API; second request is ignored as duplicate | Check relay idempotency table and confirm vendor send count equals 1 |
| Block send immediately after opt-out | Revoke marketing consent while the user is waiting inside a journey step | Pre-send check blocks dispatch across all promotional channels | Verify subscription state change log and relay suppression record |
Standardized pre-launch and ongoing verification tables are available in the CRM Campaign QA Resource and the Campaign Send Checklist.
Operating standards to agree on before adding more channels
Multi-channel CRM succeeds not by connecting the most channels, but by agreeing on which channel fires under which condition, when it stops, and how fatigue and consent are enforced. Once those boundaries are fixed, adding domestic messaging channels drives repeat conversions instead of opt-outs.
Before expanding your journeys, check whether your team has documented (1) an informational-versus-promotional channel boundary table, (2) fallback wait windows that distinguish non-delivery from non-open, and (3) webhook relay deduplication and KST quiet-hour guards.
As an official OneSignal partner in Korea, IXC supports app/web push, email, and in-app journey buildouts as well as webhook relay development for Korean SMS and Kakao AlimTalk vendors, pre-send QA, and monthly campaign operations. Discuss your scope through our CRM Campaign Operations Service, CRM Marketing Automation Service, and CRM Migration Service.


