Five settings you can control

WAGHL gives you several independent controls over what happens when a message or call comes in. On multi-user accounts, each is set per device — so every WhatsApp number can behave differently.

1. Incoming — stop messages reaching GHL

Turn Incoming off to make a number send-only: outbound messages and workflows still work, but no incoming WhatsApp messages reach your GHL inbox. Useful when:

  • You're using that number purely for marketing or transactional sends
  • Customer replies are handled by a different team or tool
  • You want to avoid GHL conversation clutter

2. Contact — stop creating new contacts

Turn Contact off and messages still arrive on WhatsApp, but no new contact is created in GHL for numbers that aren't already there. Useful when:

  • You only want records for existing leads/customers, not every new sender
  • Your WhatsApp number is shared with people who shouldn't become CRM contacts
  • You want to keep your GHL contact list clean

3. Calls — WhatsApp call events in GHL

Calls is on by default — WhatsApp call events for that number are posted into the GHL conversation, so a call shows up in the contact's timeline alongside their messages, and can even trigger workflows. Turn it off if you'd rather not log calls (messages are unaffected). See WhatsApp call events for what this looks like and an automation example.

4. Blocked — mute specific numbers

Add a number to the Blocked list and its messages and WhatsApp calls to this number are no longer posted to your GHL — nothing lands in the inbox or the conversation from that sender. The sender isn't notified; the messages simply don't reach your CRM. Useful when:

  • A spammer or a nuisance number keeps messaging and cluttering your inbox
  • You want to silence a specific contact on one number without affecting everyone else

Unlike the Yes/No switches, Blocked isn't a toggle — it's a list you manage. Group messages are not affected by it.

5. Tag — auto-tag the sending number

You can have an incoming message on this number tag the contact wa#<this number>, so that replies and workflow messages go back out from the same number. The Tag setting controls that behaviour, and it's off by default:

  • Tag = No (default) — incoming messages on this number never add or change a contact's wa# tag (whether they're a new or existing contact). This number doesn't "claim" contacts automatically.
  • Tag = Yes — an incoming message on this number tags the contact with this number, and the tag moves to another number if the contact later writes to that one. Turn this on when you want the number a contact messages to decide which number replies go out from.

Leaving Tag off doesn't take away your control of the sending number: you can still pick the number from the WhatsApp number picker in GHL, use {wa#…} in a message, and any wa# tag the contact already has still decides which number sends. See Number selection for the full order.

💡
Multi-user only

The Tag switch appears only on accounts with more than one WhatsApp number — with a single number there's nothing to tag to.

The settings are separate Incoming = No stops all messages on that number reaching GHL. Contact = No still lets messages arrive — it only stops a new CRM contact being created. Calls = Yes adds WhatsApp call events to the conversation. Blocked targets specific senders, keeping their messages and calls out of GHL. Tag = Yes lets this number auto-tag contacts (off by default). You can set each one independently on each device.

How to set it per device

On multi-user accounts these are set on each device in your number list, so every number can be configured on its own.

1

Open the sub-account's devices

Sign in at waghl.com/login. In the left menu, click Sub-accounts — you'll see a list of sub-accounts with a Users Action column. Under that column, click the view icon (the eye) for the sub-account to open its list of numbers (devices).

2

Find the Inbound Settings column

Each device row has an Inbound Settings column holding the controls — Yes/No switches for Incoming, Contact, Calls and Tag, plus a Blocked control. (Tag appears only on multi-user accounts.)

3

Set the switches to Yes or No

Choose Yes or No for each on that device:

  • Incoming = Yes — messages reach GHL (default). No — send-only, nothing comes in.
  • Contact = Yes — new senders become GHL contacts (default). No — messages still arrive on WhatsApp, but no contact is created in the CRM.
  • Calls = Yes — WhatsApp call events are posted into the GHL conversation (and can trigger workflows). No — call events are ignored.
  • Tag = No — this number never adds or changes a contact's wa# tag (default). Yes — an incoming message auto-tags the contact with this number. (Multi-user accounts only.)

The change saves as soon as you pick it — no separate save button — and takes effect immediately for that device.

4

Manage the Blocked list

In the same column, the Blocked control is a red block icon — a circle with a diagonal line through it, like WhatsApp's own Block symbol — with a count beside it showing how many numbers are blocked for that device (for example, the icon followed by 3). Click it to open a popup where you can add a number, search the list, or unblock a number. Changes take effect right away — a blocked sender's messages and calls stop reaching GHL, while group messages keep coming through.

Set different rules per number Because it's per device, you can (for example) keep a sales number fully open while making a broadcast number send-only, or let one number create contacts while another doesn't — all under the same account.
⚠️
Outbound messages always work

These settings only affect incoming messages, contact creation, and call events. Your team can still send WhatsApp messages out from GHL conversations, workflows, and AI replies regardless of how they're set.

What's next?

Need help with this? WhatsApp us at +1 347 308 7143 — quick replies guaranteed.
💬 Message us