On this page

Jump to any section using the links below

Hubhus provides a unified messaging system that handles both Email and SMS—using the same template logic, placeholders, and automation engine. Understanding how messages are created, sent, and personalized will help you build efficient communication flows across your campaigns.

Messaging templates

A template defines:

• The message content (email or SMS)

• Dynamic placeholders (e.g. %lead_name%)

• Conditional logic (@if … @endif)

• Sender identity (email sender or SMS sender name)

• Recipient placeholder

• Spam-protection rules

• Whether the message is manual, automated, or both

Templates ensure consistency, reduce manual work, and keep communication predictable.

Manual vs. automated messages

Manual messages

Sent directly by a user from inside a lead.
Use when communication must be personal or adjusted before sending.

Automated messages

Triggered by:

• Status changes

• Select-field updates

• Booking creation

• Time-based automations

• Workflow logic

Use for confirmations, reminders, follow-ups, and notifications.

Message history and tracking

Inside each lead’s History, you can see:

• All sent messages (email + SMS)

• Whether they were sent manually or automatically

• Delivery status

• Open tracking (email only)

• Which automation triggered them

This is essential for troubleshooting and verifying delivery.

Sender configuration

For Email

A Sender Identity defines:

• From-name

• From-email

• Reply-to email

Notes:

• Cannot be changed dynamically using placeholders

• Must be verified for deliverability

• Ensures consistent branding and reduces spam issues

For SMS

Your messaging setup defines the sender name (short alphanumeric name).
SMS messages are always plain text, with no HTML.

Recipient placeholders (To-field)

Hubhus supports dynamic recipients using placeholders. Common options include:

• %lead_email% / %lead_phone%

• %assigned_person_email% / %assigned_person_phone%

• %event_resource_email%

• %brand_contact_email% (fallback)

• Custom email/phone fields using {{api_name}}

You can apply conditional logic inside the recipient field.

Example: Assigned person if available, otherwise fallback

@if(%assigned_person_email%){
  %assigned_person_email%
}@else{
  %brand_contact_email%
}@endif

This is the correct way to define dynamic recipients in Hubhus messages.

Using HTML components (Email only)

HTML components provide structure, branding, and reusable building blocks.

They do not control sender or recipient logic—only layout and reusable content.

Button example (correct syntax)

<hh-email.button url="@page[offer,url]" color="%brand_color%">
  Go to offer
</hh-email.button>

Common uses and recommendations

We strongly recommend using components for:

• Signatures

• Footer text

• Marketing blocks

• Branding sections

• Reusable formatting (e.g., card layouts, spacing, headers)

Reusable components appear like this:

<hh-component.assigned-person-signature />

Or the legacy version:

@include(assigned-person-signature)

Email vs. SMS in the messaging system

Email

• Supports HTML components

• Ideal for confirmations, instructions, reports

• Tracks opens

• Supports extensive placeholders and conditional logic

SMS

• Plain text only

• Best for short reminders and time-critical messages

• No HTML components

• Uses the same placeholders for dynamic content

Both channels work manually and via automations.

Learning outcome

After reading this, you should understand:

• How the Hubhus messaging system handles both email and SMS

• How templates define content and behavior

• How sender identities and dynamic recipients work

• How HTML components support reusable, branded content

• When to use email vs. SMS in your workflows

Related articles

Understanding @if/@else conditional logic
Understanding placeholders and dynamic content
What is the Hubhus API?
Building workflows in Hubhus
Understanding action listeners