Templates

Templates decouple creative from delivery. The same template can be used by a campaign today and a journey next month. Any update to the template flows through immediately to every consumer of it.

Anatomy

• Channel — email, push, SMS, WhatsApp, in-app, on-site.
• Category — organizational tag (e.g. welcome, transactional, win-back).
• Subject (email) — supports Liquid variables.
• Preview text (email) — the snippet shown in inbox lists.
• Content — HTML for email, plain text for SMS, JSON payload for push.
• AMP HTML (email, optional) — see AMP for Email.

Liquid variables

Templates use a Liquid-like syntax for personalization. Pulse exposes:

• Customer fields: {{first_name}}, {{email}}, {{country}}
• Attributes: {{attributes.wallet_balance_ngn}}
• Event properties (inside journeys): {{event.properties.sku}}
• Workspace branding: {{workspace.name}}
• Conditional blocks: {% if attributes.is_premium %}…{% endif %}

Live preview

The composer renders a live preview as you type. Pick a sample customer from the dropdown to see variable substitution applied.

Versioning

Saves overwrite in place. For stable audit trails, duplicate the template before a major rewrite. Audit log rows record the editing user, timestamp, and a diff of changed fields.

Best practices

• Always include an unsubscribe link in email templates (Pulse blocks sending otherwise).
• Keep subject lines under 70 characters.
• Use preheaders — the preview text is often as impactful as the subject.
• For SMS, keep content under 160 characters to avoid multi-part charges.