skills.rest
delta-and-beta
delta-and-betaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architect-subscription-management

Manage subscription groups and consent flows for email and SMS in Braze.

Updated Apr 6, 2026
Search Tags:#compliance#email#sms#consent#subscription-management#double-opt-in#fuzzy-opt-out
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill architect-subscription-management
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect-subscription-management
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/architect-subscription-management
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill architect-subscription-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reduce legal and operational risk when sending email and SMS by centralizing subscription group design, consent collection, opt-in/opt-out handling, and preference management so messaging programs remain audit-ready and regulation-compliant.

Core Features & Use Cases

  • Subscription group design: Define per-channel subscription groups that separate transactional and promotional traffic and map sending numbers to consent scopes.
  • Consent workflows: Configure double opt-in prompts, fuzzy opt-out detection, and required auto-responses to ensure explicit and defensible consent signals.
  • Preference center & API integration: Implement hosted or custom preference centers and synchronize CRM or SDK consent changes via Braze REST APIs and User Update steps.
  • Compliance decision framework & audits: Apply a fail-closed sequence (channel → geography → message type → consent signal → group assignment → suppression) to review sends, migrations, and segment targeting with audit trails and exportable evidence.
  • Use Case: Migrate a promotional SMS list into segmented subscription groups while preserving consent records, verifying double opt-in where required, and establishing suppression checks before any campaign send.

Quick Start

Audit a subscription design for SMS and email by mapping channels, geographies, message types, consent signals, subscription group assignments, and suppression rules into a fail-closed checklist.

Frequently Asked Questions about architect-subscription-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design double opt-in and fuzzy opt-out workflows for SMS and email compliance?▼

Design compliant subscription flows by configuring double opt-in prompts and fuzzy opt-out detection to ensure explicit, defensible consent signals. This enforces per-channel consent and required auto-responses for regulatory compliance.

How do I handle TCPA and GDPR compliance when migrating promotional SMS lists?▼

Handle TCPA and GDPR compliance during list migration by preserving consent records, verifying double opt-in where required, and establishing suppression checks before campaigns. This ensures per-channel consent and audit trail readiness.

What is a fail-closed compliance decision framework for subscription groups?▼

A fail-closed compliance framework sequences checks from channel to geography, message type, consent signal, group assignment, and suppression rules. This sequence ensures only legally verified messages reach users.

Does Braze support API-driven subscription state updates for custom preference centers?▼

Yes, Braze supports API-driven subscription state updates via REST APIs and User Update steps. This synchronizes CRM or SDK consent changes with hosted or custom preference centers for real-time compliance.

Why do I need separate subscription groups for transactional and promotional traffic?▼

Separate subscription groups are needed to isolate transactional traffic from promotional messaging, mapping sending numbers to specific consent scopes. This separation maintains regulatory compliance and targeting accuracy.

What are the limitations of fuzzy opt-out handling in subscription management?▼

Fuzzy opt-out handling limitations include the necessity to enforce fail-closed suppression checks and audit trails for defensible consent signals. It requires continuous alignment with carrier rules and regulatory reviews.

Related Skills

Explore More Legal & Compliance Skills→
havingautismhavingautism
190

using-git-worktrees

Create isolated git worktrees for feature development.

Community
Intermediate
bcharlesonbcharleson
8

bison-blacklist

Manage email and domain suppression lists for cold outreach platforms.

Community
Intermediate
delta-and-betadelta-and-beta

strategist-subscriptions

Manage subscription states and preference center configurations via Braze REST APIs.

Community
Advanced
trycouriertrycourier
13

courier-notification-skills

Implement multi-channel notification systems with Courier for email, SMS, push, Slack, Teams, and WhatsApp.

Official
Advanced