Automate transactional responses in tickets based on channel: email, WhatsApp, chat

The Problem

Service Hub can automate many things, but it can’t do something every professional ticketing system does: send an automatic response when a ticket goes unanswered for X hours—and do it in the right format for that channel.

Yes, there’s a transactional email add-on. But for basic multi-channel use cases, you shouldn’t need to pay extra or add complexity to your stack.

Here’s what happens now:

  • Customer emails asking for a refund status. No reply for 48 hours. Silent.
  • Customer DMs on WhatsApp asking for invoice details. No auto-acknowledgment.
  • Customer uses live chat asking for password reset. Still waiting.
  • You either buy the add-on, route through Make/n8n, or let them hang.

For something this fundamental, it should be native and free tier capable.

What This Should Do

Add a workflow action: “Send transactional response on ticket” that:

Detects the channel automatically:

  • Email → sends email reply to the thread
  • WhatsApp (via API) → sends a WhatsApp message
  • Chat → sends a chat message
  • Phone → SMS or skip

Triggers based on:

  • Ticket unanswered for X hours
  • Ticket in specific stage
  • Custom ticket property conditions

No marketing contact needed. It’s transactional, not marketing.

Why This Matters

  1. Customers expect auto-acknowledgment. Zendesk does this free. Intercom does this. HubSpot locks it behind an add-on or forces you into external automation.
  2. Transactional email add-on is expensive and incomplete. It’s email-only. What about WhatsApp, chat, SMS? Multi-channel is the reality now, not a future feature.
  3. This drives people to Make, n8n, or third-party apps. Every team building anything beyond basic support ends up stitching together external tools because HubSpot won’t do it natively.
  4. It’s table stakes, not a premium feature. Basic transactional responses should be free tier capable. You’re already in Service Hub.
  5. You already have the infrastructure. Multi-channel integrations exist. Workflow engine exists. Channel detection exists. Just connect the dots.

Use Cases

  • E-commerce: Auto-reply with tracking number on email after 4 hours
  • SaaS: Send WhatsApp template with support hours if chat goes unanswered
  • Agencies: Auto-acknowledge requests within 2 hours or escalate
  • Support teams: “We’re looking into this” transactional message after 24 hours

This Is Different From Marketing Automation

Marketing automation = permission-based, consent-driven, about nurturing.

Transactional responses = keeping your customer in the loop about their own ticket, on their own channel, at the right time.

This should live in Service Hub, not Marketing Hub.

This is a great suggestion and I fully support it

I’d like to add an important use case that goes beyond tickets in Service Hub.

Many small businesses and teams use WhatsApp as their main communication channel, not only for support tickets but also for general inquiries, sales conversations, and first contact with potential customers.

In this context, having simple automated responses for WhatsApp is essential, such as:

- Instant welcome messages when a new conversation starts
- Away or out-of-office messages
- Basic acknowledgment like “We’ve received your message and will get back to you shortly”

Currently, this is not possible natively in HubSpot unless using external tools or complex setups, which creates unnecessary friction.

It would be incredibly valuable to have this functionality available directly within the WhatsApp integration, even outside of ticket-based workflows, similar to how chatflows work for live chat.

This would greatly improve response times and customer experience, especially for small teams managing high volumes of messages.

Thanks again for bringing this up!