Settings you can control

WAGHL gives you 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 — push WhatsApp call events to GHL

Turn Calls on to post WhatsApp call events to the contact's GHL conversation. When someone calls this number on WhatsApp, the outcome is written into their conversation as a message:

  • ⏰ Missed WhatsApp voice call
  • ✅ WhatsApp voice call answered
  • ❌ WhatsApp voice call declined
  • ↩️ WhatsApp voice call cancelled by caller

Video calls read the same way with "video" in place of "voice". Every event contains "WhatsApp" and "call", so you can catch them all with a single GHL workflow filter — for example, to auto-reply to missed calls or log call activity. Turn Calls off and call events aren't reported to GHL.

Call events post to existing contacts only A call event is written to the caller's conversation only if they're already a contact in GHL. A call never creates a new contact.
The settings are independent Incoming = No stops messages reaching GHL at all. Contact = No still lets messages arrive on WhatsApp — it only stops a new CRM contact being created. Calls controls call events separately. You can set all three 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

Open the device's settings

Each device has a settings panel with three labeled rows — Incoming, Contact, and Calls — each with its own Yes / No dropdown. Hover the info icon on any row for a reminder of what it does.

3

Set each 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 to existing contacts' conversations (default). No — call events aren't reported to GHL.

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

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 reporting. 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