architect-channel-architecture

What problem does it solve?

Architects and campaign owners struggle to choose the right combination of messaging channels, delivery types, and orchestration patterns for scalable, compliant campaigns across Braze workspaces. This Skill concisely maps urgency, content richness, and platform capabilities to practical topology and sequencing decisions so teams can design reliable cross-channel journeys without reworking implementation details later.

Core Features & Use Cases

• Channel taxonomy & selection: Converts urgency × richness tradeoffs into recommended channels (push, in-app, email, SMS/RCS, WhatsApp, LINE, KakaoTalk, webhooks, content cards, banners).
• Orchestration patterns: Provides Canvas-level patterns (fallback chains, coordinated timing, cross-surface persistence, webhook orchestration) and how to implement them safely.
• Platform capability mapping: Identifies when BrazeAI, delivery types, RCS, or partner integrations affect architecture and cross-workspace copying constraints.
• Use case: Design a re-engagement flow that uses push as primary, falls back to email after 24 hours, persists content via content cards, and flags SMS compliance checks for international markets.

Quick Start

Use the architect-channel-architecture skill to produce a channel topology and Canvas orchestration plan for a given campaign brief.