HVAC email marketing

Send from the customer record. Receive the reply on the job.

Run one-time or automated email and SMS campaigns from CRM-backed segments, check readiness before sending, and keep the response connected to the same customer conversation and operating record.

Sending depends on configured sender identity, channel consent, suppression handling, quiet hours, content, provider readiness, and the selected campaign or workflow mode.

Book a demo
Campaign composerMarketing · Campaigns
ONE-TIME CAMPAIGN

Spring maintenance reminder

Audience: Maintenance due — no visit booked

Draft saved
EmailSMS available
Subject
Your spring maintenance visit
Preview
Choose a service window that works for your property.

Hi {{customer.first_name}},

Your equipment is due for seasonal maintenance, and there is no future visit booked for this property.

Choose a service window

SenderReady

Audience1,106 eligible

SuppressionChecked

ContentReady

ScheduleTuesday · 10:00 AM local time
Schedule campaign

Illustrative campaign — recipients, content, timing, and states demonstrate the interface, not a live send.

A CRM-backed audience, email content, preflight checks, and schedule connect to a delivery and reply path.

Direct answer

What is HVAC email and SMS marketing software?

HVAC email and SMS marketing software lets a contractor send one-time or automated campaigns to CRM-backed customer segments. The campaign connects its audience, channel, content, sender identity, consent, suppression, quiet hours, schedule, delivery state, and replies. A response returns to the unified Inbox, where the office can continue the conversation and turn accepted work into a booking or job record.

The relationship

A campaign is the path between an eligible audience and an operational response.

Segment and audience → Campaign → Preflight for sender domain or A2P 10DLC, consent, unsubscribe or STOP request, suppression, quiet hours, content, and timing → Email or SMS delivery state → Reply in the Unified Inbox → Booking → Job. Delivery, reply, booking, and job associations remain observable without being labeled causal ROAS.

How it works

Compose the message only after the audience and channel are explicit.

The campaign workflow separates who should receive the message, whether the channel is ready, what will be sent, and what the office does when someone replies.

  1. Select the audience and campaign mode

    Choose a CRM-backed segment, then decide whether the campaign is a one-time broadcast for the current eligible audience or an automated sequence that enrolls future matches through configured logic.

  2. Choose email, SMS, or a coordinated sequence

    Use email for the longer explanation and SMS for a short channel-appropriate nudge. Each channel keeps its own sender, consent, unsubscribe or STOP, suppression, and delivery requirements.

  3. Pass preflight before scheduling

    Confirm sender identity, A2P 10DLC where required, eligible recipients, suppression checks, quiet hours, content, links, and schedule. A campaign that is not ready remains visibly blocked rather than implied sendable.

  4. Route the response into operations

    Delivery status remains a provider event. A reply becomes a conversation in the unified Inbox. When the customer accepts the next step, the office can create a booking or job without rebuilding context in another tool.

State model

Delivery, conversation, and booked work are different events.

Separating these states prevents a delivered message from being reported as a response, a response from being reported as revenue, or a booked job from being treated as causal attribution.

StateWhat it provesWhat it does not prove
ScheduledThe campaign has an audience, content, channel, and send timeThat a provider accepted the message
DeliveredThe provider reported deliveryThat the customer read or acted on it
RepliedA customer response reached the unified InboxThat the reply became revenue
Job bookedThe accepted response became an operational job recordIncremental or causal ROAS
Delivery and responseMarketing · Campaigns
STATE, NOT ATTRIBUTION

Delivery is not a reply. A reply is not yet booked work.

Each event states only what the underlying record can prove.

  1. 01Campaign event
    Scheduled

    Tue · 10:00 AM

  2. 02Provider event
    Delivered

    Delivery reported

  3. 03Conversation event
    Replied in Inbox

    Customer asked for a visit

  4. 04Operational record
    Job booked

    Service window confirmed

The connected records show an observed path. They do not establish incremental or causal ROAS.

Illustrative campaign — recipients, content, timing, and states demonstrate the interface, not a live send.

A CRM-backed audience, email content, preflight checks, and schedule connect to a delivery and reply path.

Product boundary

The system can preserve the path without pretending every path is causal.

Campaign readiness, delivery, replies, and booked records are concrete states. Performance conclusions require evidence beyond a sequence of timestamps.

Available campaign structure

  • CRM-backed audience segments, one-time broadcasts, and automated enrollment through configured workflows or sequences.
  • Email, SMS, reusable message templates, delivery states, and replies returned to the unified Inbox.
  • Observable connections among the campaign, recipient, conversation, booking, and job record.

Requires account configuration

  • A verified sender domain for email and a registered phone identity or A2P 10DLC setup where SMS rules require it.
  • Consent, unsubscribe and STOP handling, suppressions, quiet hours, audience fields, content, and provider readiness.
  • A selected one-time or automated mode with reviewed schedule, message, and operational reply ownership.

Owned by connected pages

  • Outbound voice belongs to Voice Agents and is linked as a connected channel rather than duplicated here.
  • Customer conversation ownership belongs to the Unified Inbox after an email or SMS reply arrives.
  • Dispatch assignment and work execution belong to the AI Dispatcher, Front Office, and Back Office records.

Not claimed

  • Every account is ready to send before sender, consent, suppression, and provider setup is complete.
  • Every response is automatically qualified, booked, invoiced, or collected without human or configured workflow decisions.
  • Observed delivery, reply, booking, or job records prove incremental revenue, causal ROAS, or a guaranteed result.

Connected work

The campaign begins with a segment and ends in the operating system.

Audience selection, channel execution, reply handling, booking, dispatch, and invoicing remain distinct responsibilities connected by the same customer and job context.

  • HVAC customer-retention segments

    Define the matching and sendable audiences that a one-time or automated campaign can use.

  • Unified Inbox

    Receive and continue customer email and SMS replies in the operational conversation.

  • Voice Agents

    Run shop-owned outbound or inbound voice on the connected front-office workflow instead of treating voice as an email feature.

  • HVAC workflow automation

    Connect record events, conditions, delays, supported communication actions, and follow-up tasks around the campaign.

  • AI Dispatcher

    Carry accepted work into the job and assignment flow after the customer response becomes a real service need.

Questions about HVAC email marketing

What is HVAC email marketing software?

HVAC email marketing software connects a contractor’s customer records and segments to email campaigns, delivery states, replies, and follow-up work. A useful system does more than send a newsletter: it keeps the audience definition, sender readiness, consent, suppression, message, conversation, and booked-job path attached to the same operational records the office already uses.

Should HVAC companies use email or SMS marketing?

HVAC companies can use email for a longer explanation and SMS for a short, timely nudge, provided each contact is eligible for that channel. Email sender identity and unsubscribe handling differ from SMS registration, consent, STOP handling, and quiet hours. A coordinated campaign keeps the customer and purpose consistent without treating the two channels as interchangeable.

What is the difference between a one-time campaign and HVAC marketing automation?

A one-time campaign sends once to the eligible audience at the scheduled moment, while HVAC marketing automation can enroll future records when configured segment or workflow conditions are met. Automation does not remove channel safeguards or operational ownership. Sender readiness, consent, suppression, quiet hours, content, scheduling, and reply handling still need explicit configuration.

What should an HVAC campaign preflight check?

An HVAC campaign preflight should verify the audience, sender identity, provider readiness, consent, unsubscribe or STOP handling, suppressions, quiet hours, message content, links, and schedule before sending. For SMS, phone registration such as A2P 10DLC may also apply. A failed or unknown readiness check should block the send rather than be treated as a warning the system can ignore.

How does a campaign reply become a booked HVAC job?

A campaign reply becomes a booked HVAC job only after the response reaches the unified Inbox and the office or a configured workflow confirms the service need and next step. Delivery is not a reply, and a reply is not automatically revenue. The useful continuity is that the customer, conversation, booking, and job remain connected instead of being retyped from a separate mail tool.

Product reviewed .

Book a demo

See one campaign move from audience to Inbox to booked work.

Walk through a CRM-backed segment, email or SMS composition, sender and consent preflight, a delivery state, the customer reply, and the operational handoff to a booking or job.

Book a demo