Skip to main content
Short answer: no. Flowella doesn’t check a contact’s HubSpot marketing contact status. It sends WhatsApp messages to marketing and non-marketing contacts alike. You stay responsible for having each person’s opt-in before you message them on WhatsApp.

What the marketing contact status controls

In HubSpot, marketing contacts are the contacts you pay to market to. HubSpot’s marketing tools, such as marketing emails, ads audiences and marketing workflow actions, only work for contacts set as marketing. HubSpot doesn’t charge for contacts set as non-marketing. See HubSpot’s guide to marketing contacts. WhatsApp messages from Flowella aren’t HubSpot marketing emails. Flowella sends them through the WhatsApp Business Platform, so the marketing contact status doesn’t block them. This applies to every way Flowella sends: Flowella doesn’t read or change the marketing contact status, including on contacts it creates in HubSpot.

You are responsible for WhatsApp opt-in

Meta requires you to get each person’s opt-in before you message them on WhatsApp. Flowella doesn’t collect or store opt-ins, so keep your own record. Meta’s rules say that when you ask for opt-in, you must:
  • Make it clear that the person is agreeing to receive messages from your business.
  • Name your business.
  • Follow the laws that apply to you.
Meta accepts any method that meets these rules, for example a form on your website, SMS, a phone call or a paper form. See Meta’s Get opt-in for WhatsApp. Local data protection and direct marketing laws may ask for more, so check what applies to you. Record the opt-in in HubSpot, so your workflows can check it. For example:
  • A contact property, such as a WhatsApp opt-in checkbox and the date it was given, filled by your forms or imports.
  • A HubSpot subscription type for WhatsApp, if you manage consent through HubSpot’s subscription preferences.
Then use it in the workflow’s enrolment criteria, or in a branch before the Flowella action, so only contacts who opted in get a message.

How Flowella opt-outs work

Flowella records opt-outs, not opt-ins. An opt-out stops Flowella sending to a phone number from one of your WhatsApp numbers.
  • Keywords. When a contact sends STOP, UNSUBSCRIBE, CANCEL, END or QUIT as the whole message, Flowella records an opt-out for the WhatsApp number they messaged. START or UNSTOP opts them back in. See How keyword opt-outs work.
  • Your team. You can add opt-outs one at a time, or import a CSV file, on the Opt-outs page. See Opt-outs.
  • What it blocks. Flowella blocks every send to that phone number from that WhatsApp number. The HubSpot workflow actions fail with CONTACT_OPTED_OUT. See What an opt-out blocks.
  • Each number separately. An opt-out on one of your WhatsApp numbers doesn’t stop messages from your other numbers.
Flowella doesn’t write opt-outs to HubSpot. It doesn’t change subscription types, the marketing contact status or any opt-out property. To keep a record in HubSpot, build a workflow that enrols on the Text Reply trigger. Branch on the Last WhatsApp reply message property being one of the opt-out keywords, then set your own opt-out property. Opt-outs your team adds or imports in Flowella don’t fire a HubSpot event, so update HubSpot for those yourself.
WhatsApp also lets people stop marketing messages from your business inside the WhatsApp app. Meta then refuses your Marketing templates to them with error 131050. Flowella doesn’t add these people to your Opt-outs page. See Error 131050.

Should you mark WhatsApp contacts as marketing contacts?

Flowella works the same whichever option you choose. Pick the one that matches how you use the marketing contact status.

Mark them as marketing

Use this if the marketing contact status is your record of marketing consent. Contacts who opted in to WhatsApp marketing then count towards your HubSpot marketing contact tier.

Keep them non-marketing

Use this if you only message these contacts on WhatsApp. HubSpot doesn’t charge for non-marketing contacts, and Flowella still messages them.

Track WhatsApp separately

Keep the marketing contact status for email, and record WhatsApp opt-in in its own property or subscription type. This works best when people agree to each channel separately.

Marketing emails and WhatsApp in the same workflow

In a HubSpot workflow that sends both a marketing email and a WhatsApp template:
  • The marketing email only goes to contacts set as marketing.
  • Send WhatsApp Template goes to every contact who reaches the step, whatever their marketing contact status.
To limit the WhatsApp send, add a branch before the Flowella action that checks your WhatsApp opt-in property, subscription type or marketing contact status.
  • Opt-outs: keywords, manual opt-outs and what they block
  • Workflow actions: the HubSpot actions Flowella adds
  • Bulk send: send a template to a list from a file
  • Plans and limits: Flowella message costs are separate from HubSpot’s marketing contact billing
Last modified on October 24, 2026