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, 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.
Communication integrations are configured per source. Open a source → Messaging Settings → Integrations tab, then pick the sub-tab (Messengers or Other). Each integration has its own card with an Enable toggle, its settings, and a Validate Connection button.
Supported integrations
Slack
Post lead alerts into a Slack channel in your workspace via OAuth. Lives on the Messengers sub-tab.
SMS
Text one or more phone numbers whenever a new lead comes in (US-focused delivery). Lives on the Messengers sub-tab.
Telegram
Send lead alerts into a Telegram chat or group that's been linked to your account. Lives on the Messengers sub-tab.
LeadConnector Messaging Sync (GoHighLevel)
Push the conversation into GoHighLevel's Conversations inbox so your team replies from inside GHL. Card is labeled LeadConnector Messaging Sync. Lives on the Messengers sub-tab.
Call Bridge
When a lead shares a phone number, NZ Leads calls you first and then dials the lead and joins both calls. Lives on the Other sub-tab.
REST Webhook
POST a JSON payload to any endpoint you control on every lead event. Lives on the Other sub-tab.
Lead Reply API
A lightweight API for sending replies back into NZ Leads from an external system. Lives on the Other sub-tab.
Which should I pick?
- Solo operator or on-call rotation → SMS. Nothing beats a text for reliability and speed.
- 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.
Notify on new lead
Label: Notify on new lead. On messenger cards such as SMS, Slack and Telegram.
- When on - An alert is sent as soon as a new lead comes in.
- When off - There is no new-lead alert. You still get an alert when a customer sends a message the AI doesn’t handle or when the AI hands the lead to a person, and when contact info arrives if Messengers is checked under Trigger integrations: in the source’s Contact Info tab.
Messenger cards have no “only when contact info is received” or “only new leads” options; those exist only on CRM cards.
Notify only for MESSAGE type leads
Label: Notify only for MESSAGE type leads. Shown only on Google Local Services sources. When on, phone-call and booking leads are not sent to this integration, only message leads.
Include source name in messages
Label: Include source name in messages. On messenger cards such as SMS, Slack and Telegram. Default: off.
- When on - The source name (e.g., “Yelp - Downtown”) is added 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.