Communication Tools

Communication integrations do one of two things: they alert your team the moment a new lead comes in, or they hand the lead off to another system so your own software can take over. These integrations are split across two sub-tabs of the source’s Messaging Settings → Integrations tab:

• Messengers sub-tab — Slack, SMS, WhatsApp, Telegram, and LeadConnector Messaging Sync (GoHighLevel Messenger).
• Other sub-tab — Call Bridge, REST Webhook, and Lead Reply API. These sit under Other because they do more than push a single alert.

Supported integrations

Which should I pick?

• Solo operator or on-call rotation → SMS. Nothing beats a text for reliability and speed.
• Small field team already on WhatsApp → WhatsApp. Drop the alert into the crew’s group chat.
• Office or hybrid team with multiple departments → Slack. A dedicated channel keeps threads organized and searchable.
• Team that coordinates on Telegram → Telegram.
• You already handle replies inside GoHighLevel → LeadConnector Messaging Sync (card is labeled LeadConnector Messaging Sync in the UI).
• You want to be patched straight onto the phone with the lead when they share a number → Call Bridge.
• You run your own software and want the raw event → REST Webhook.
• You have an external system that needs to post replies back into NZ Leads → Lead Reply API.

You can enable more than one at the same time. It’s common to run Slack for the office plus SMS for whoever is on-call after hours.

Shared options on every card

These options appear on every communication integration. The per-integration pages only mention them when they behave differently for that integration.

Enable

A simple on/off toggle for this integration on this source. When off, nothing is sent. Default: off — the integration only runs once you turn it on.

Inherit from parent

Only shown on a location that has a parent business. When on, the location uses the parent business’s configuration for this integration — same credentials, same options. When off, the location has its own settings that override the parent. Turn it off only on a specific location that needs to behave differently.

Create customer only when contact info is captured

Label: Create customer only when contact info is captured. Default: off.

• When on — NZ Leads waits to fire the alert until it has collected either a phone number or an email from the conversation. Leads that never share contact info never trigger an alert.
• When off — The alert fires the moment the lead first reaches out, even before their phone or email is known.

Use this when you only want to be alerted about real, reachable leads.

Create only for new leads

Label: Create only for new leads. Default: off.

• When on — NZ Leads skips leads it recognizes as returning or already in the system. Only brand-new leads trigger an alert.
• When off — Every lead triggers an alert, including returning ones.

Include source name

Label: Include source name. Default: off.

• When on — The source name (e.g., “Yelp – Downtown”) is appended to the alert so you can see at a glance where the lead came from.
• When off — The source name is not included.

Use this when you run multiple sources and want to tell them apart from the alert itself.

Validate Connection

A button on every card that tests the integration right now. On success, you see a green confirmation. On failure, the error is shown inline so you can fix it.

Disconnect

Removes the connection for this integration on this source. You’ll be asked to confirm. After disconnecting, no more alerts are sent until you reconnect.

Error log

If the integration hits a problem while processing a real lead, the most recent error and its timestamp are shown right on the card.

Questions about communication integrations? Email support@nzleads.com.