What this does
WhatsApp supports voice and video calls. With the Calls setting on (it's on by default), each call to a number is recorded as an event in the GHL conversation — so your team can see that the contact tried to reach you, and when, without leaving the inbox. You can turn it off per number if you'd rather not log calls.
- Visibility — the call shows up in the conversation timeline alongside the contact's messages.
- Automation — because the event posts as an inbound conversation entry, GHL workflows can act on it (more below).
What gets posted, and when
WAGHL posts one short inbound line into the conversation per call, once the call is over. There's exactly one message per call, with the wording set by the outcome:
| Outcome | Message posted | When |
|---|---|---|
| Missed | ⏰ Missed WhatsApp voice call | Rang unanswered until WhatsApp gave up. |
| Answered | ✅ WhatsApp voice call answered | The call was picked up. |
| Declined | ❌ WhatsApp voice call declined | The call was rejected on your side. |
| Cancelled | ↩️ WhatsApp voice call cancelled by caller | The caller hung up before it was answered. |
For a video call, "voice" is replaced by "video" — for example ⏰ Missed WhatsApp video call. Every message contains the words WhatsApp and call, which makes them easy to match in a workflow. If a number is shown on multiple connected devices, a second line notes which one took the call — for example 💬 Received on +1 555 010 1234.
Missed WhatsApp to react only to missed calls, or WhatsApp + call to catch every outcome. See the example below.
Turn it off per number
Calls is on by default, so WhatsApp call events are already posted to the conversation — there's nothing to switch on. You only need to come here if you want to turn it off for a particular number. It lives in the same per-number panel as Incoming and Contact, so each number can be set on its own.
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).
Find the Calls dropdown
Each device row has an Incoming / Contact / Calls column with three dropdowns. The third one is Calls.
Set Calls to Yes or No
It's already Yes (call events posted) by default. Set it to No to stop posting that number's WhatsApp call events, or back to Yes to resume. The change saves as soon as you pick it — no separate save button — and takes effect immediately for that device.
Use a call to trigger a workflow
Since the call posts as an inbound conversation entry, you build the automation on GHL's standard inbound-message trigger and filter for the call text. Here's a common example — text a contact back after they miss you / you miss them:
Create a workflow with an inbound trigger
In GHL, go to Automation → Workflows, create a new workflow, and add the Customer Replied trigger (GHL's inbound-message trigger).
Filter it to call events
On the trigger, set Reply Channel to SMS. Then add a filter so it only fires for a call — for a missed call, Message contains Missed WhatsApp. To catch any call outcome (voice or video), filter on Message contains WhatsApp and contains call. This keeps ordinary replies from triggering it.
Add your follow-up action
Add a Send SMS action (this sends over WhatsApp) with your message — for example: "Sorry we missed your call! How can we help?" You can also add a task, a pipeline move, or notify the owner.
Publish and test
Turn the workflow Published on, then place a WhatsApp call to the number. The event lands in the conversation and your follow-up fires.
Because calls and messages share the same inbound trigger, always add the message filter in step 2 — otherwise the workflow would also run on ordinary WhatsApp replies, not just calls.
FAQ
Does turning Calls on change my messages?
No. Calls is independent of the Incoming and Contact settings. It only controls whether WhatsApp call events are posted to the conversation — your messages and contact creation behave exactly as their own settings say.
Can I set it differently per number?
Yes — Calls is per device. You might post call events on your main sales number but leave them off on a broadcast-only number.
My workflow runs on every reply, not just calls — why?
The inbound trigger fires on all inbound entries, calls and messages alike. Add the message filter (step 2) so it only fires on a call — match Missed WhatsApp for missed calls, or WhatsApp + call for any outcome — and keep the Reply Channel set to SMS, which is WhatsApp once the WAGHL app is installed.
What's next?
- Stop incoming messages — the Incoming and Contact settings on the same panel
- Missed call text back — auto-reply when a call is missed
- Premium actions & webhook — trigger sends from GHL workflows