How does the messaging system work?

Modified on Tue, 5 May at 11:02 AM

How does the messaging system work?

Hubhus handles both email and SMS through a single unified template system — the same placeholder logic, conditional rules, and automation engine power every message you send. Whether confirming a booking, following up after service, or notifying a team member, it all flows from one place.

TL;DR

Templates define content + sender + recipient. Send manually from inside a lead, or automatically via automations. All sent messages appear in the lead's History tab with delivery status. Press Ctrl+K / Cmd+K to insert placeholders.

How messaging works — 4 essentials

1

Templates define everything: message content, dynamic placeholders, conditional logic, sender identity, and recipient. One template can be used both manually and via automations.

2

Manual vs. automated — send directly from inside a lead when communication needs a personal touch, or let automations trigger messages automatically based on status changes, bookings, or delays.

3

History & tracking — the lead's History tab shows all sent messages, whether manual or automated, delivery status, open tracking (email), and which automation triggered each message.

4

Email vs. SMS — email supports HTML components, branding, open tracking, and rich layouts. SMS is plain text only, best for short time-critical messages. Both use identical placeholder logic.

Templates: Campaign settings → Email/SMS templates  ·  History: Open any lead → History tab  ·  Placeholder search: Ctrl+K (Win) / Cmd+K (Mac)
Read more

Sender configuration

Email: A Sender Identity defines From-name, From-email, and Reply-to email. It cannot be changed dynamically with placeholders and must be verified before sending. This ensures consistent branding and reduces spam filtering.

SMS: Your messaging setup defines a short alphanumeric sender name. SMS messages are always plain text — no HTML or components.

Dynamic recipients (To-field)

Common recipient placeholders:

  • %lead_email% / %lead_phone%
  • %assigned_person_email% / %assigned_person_phone%
  • %event_resource_email%
  • %brand_contact_email% (fallback)
  • {{api_name}} for custom email/phone fields

Use conditional logic in the recipient field for fallback routing:

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

HTML components (email only)

HTML components provide reusable, branded building blocks. Recommended for: signatures, footers, marketing blocks, branding sections, and reusable card layouts.

Examples:

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

Components work with placeholders and conditional logic and can be reused across all templates.

Common searches

send email • send sms • email template • sms template • message history • email not sending • sender identity

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article