Hey @IManes. I don’t think with current HubSpot functionality that you could solve this cleanly with conversation-based workflows. The safest pattern I found with some light AI research is to use the WhatsApp channel’s own auto-reply/office-hours logic (where available) or an approved template plus a contact-creation step as a workaround.
Here’s how I’m understanding the limitations, and why you are where you are with this. Conversation-based workflows enroll the thread, but subscription status and WhatsApp actions live on the contact record, which does not exist for “unknown” visitors. Because there’s no contact, the workflow cannot set WhatsApp subscription or send a WhatsApp action, so your “weekend utility template” cannot fire reliably for unknown users. Based on that, here are a coupe of options you might explore.
Option 1: Use Inbox / Channel Automation (best within native limits). If your portal has the new Inbox automation for WhatsApp, use that instead of Workflows: Go to Settings → Inbox & Helpdesk → Inboxes → [Your WhatsApp inbox] → Automation.
According to a couple of resources I found, once there, you should be able to configure an automatic reply for new messages that arrive outside business hours (e.g., Friday 18:00–Monday 08:00) with copy like “Thanks for your message, our team will reply on Monday.” This runs at the channel level, not the contact level, so it works even when the sender is unknown and does not depend on subscription properties. But it gives you the weekend message you want, without touching subscription status or workflows.
Option 2: Template + contact creation workaround. If you must use a WhatsApp utility template (maybe because of language or compliance constraints), your flow has to include a contact:
- Detect new weekend conversations
- Keep your conversation-based workflow that enrolls new threads and checks timing (e.g., if conversation created on Saturday/Sunday or outside office hours, branch “Yes”).
- Create/associate a contact
- Manually: an agent creates a contact from the phone number in the first message and associates the conversation; this is what teams are doing today since auto-creation from WhatsApp is not supported.
- Or via custom code/integration: use a middleware (Tray/Zapier/Make/custom app) that listens to incoming WhatsApp messages, creates a HubSpot contact with the WhatsApp phone number, and associates the conversation.
- Send the approved weekend template from a contact-based workflow
- Once the contact exists, enroll it in a contact-based workflow that sends your “weekend / back on Monday” utility template, using the Meta-approved template ID.
- This respects the 24‑hour window: the user’s inbound message opens the session, and the template is used to respond automatically during that window.
This is more complex, but it’s currently the only way to use an actual template action rather than a plain channel auto-reply.
Given your goal (“we don’t reply weekends, but we need a WhatsApp message saying we’ll reply Monday”) and that your conversations are entering as unknown, here’s what I’d probably lean toward. Use WhatsApp inbox/channel automation for an “out-of-office/weekend” auto-reply at the channel level. Then, keep your conversation-based workflow for internal routing, tasking, or ticketing, but do not depend on it for sending WhatsApp messages to unknown users.
If you later decide you need more complex behavior (e.g., different messages by segment), invest in an integration that creates contacts and then switches to contact-based WhatsApp actions.
Because of the limitations you’re finding in HubSpot standard set-up, I think you’re probably looking at using a third-party integration or custom app to handle contact creation and template sending.