Overview
Keep message templates, versions, localisations, variables, components, approval events and provider mappings separate from source applications.
Problem
Business apps need stable message codes without hardcoding provider template identifiers and channel-specific content rules.
Solution
Bind source-app message codes to PulseGate templates by channel and locale, then resolve the correct template at send time.
How it works
Template administration supports reusable content, variables, localization, source-app bindings, provider mappings, and approval state while applications send using their own business message codes.
Who is this for
Communications Administrator
Product Engineer
Expected outcomes
- Stable business message codes across applications
- Central template lifecycle, localization, variables and provider mapping
Key metrics
Security impact
- Template content, variables, source-app binding, localization and provider template references · PII: yes where recipients, messaging identities, message content, consent, media, or external identity mappings contain personal data
Compliance
- Template permissions, source-app authorization, communication policy, and audit controls
Availability & next steps
Starter
Team
Enterprise