General
The General tab is on every vendor. It holds the vendor’s identity, whether it’s accepting anything right now, and how the leads it posts are screened. An inbound vendor gets two more cards here: the campaigns its live calls feed, and the agents allowed to take them.
Vendor
Section titled “Vendor”Name — internal. Admins only: this settings area, logs, and the vendor’s posting instructions.
Codename — what agents see: the lead Source, the contact tag, and the live-call banner. Blank uses the name. Use it when the partner’s real name isn’t what you want on an agent’s screen.
Status — Activated or Deactivated. Deactivated vendors reject posted leads, and an inbound vendor also stops routing inbound calls.
There is no third option here. An archived vendor shows a static Archived instead, and the only way back is Restore vendor in the header — see Vendors.
The note under the picker tells you where the rest of the work is: hand out the posting address on Post API, watch what arrives on Activity, and buy an inbound vendor its number on Numbers. What its calls cost you is set on Billing.
The note also says where posted leads go, and it’s worth reading closely: they land in this vendor’s own list, which is a roster rather than a dial queue — it never appears in a campaign’s list picker. To dial them, link a GoHighLevel smart list filtered on this vendor’s Codename and attach that to a campaign. Vendor Lists has the steps.
Lead handling
Section titled “Lead handling”How posted leads are screened before they land in the vendor’s list. Duplicates are matched account-wide by phone; numbers on the do-not-call list are always rejected, and that isn’t configurable.
On duplicate — what to do with the contact when a lead is already in the account.
| Option | What happens |
|---|---|
| Reject (tell the vendor it’s a duplicate) | The post is turned away and the partner is told it’s a duplicate |
| Update the contact | The existing contact is updated with the posted data |
| Don’t update the contact | The post is accepted, and the existing contact is left as it was |
This decides what happens to the contact. Whether that person gets dialed is decided by the lists they belong to, not by this setting.
Campaigns this vendor feeds
Section titled “Campaigns this vendor feeds”Inbound vendors only.
Tick the campaigns this vendor’s inbound calls should fan out to. Its calls go to ready agents across every ticked campaign.
Outbound-only campaigns aren’t offered here — they don’t take inbound calls. If the campaign you want is missing, its type is the reason; see Campaigns.
With two or more ticked, star one as the queue source: the campaign whose hold music, wait time and GHL location the call uses — that last one being the GoHighLevel sub-account the caller’s contact lands in. With one ticked there’s nothing to choose and the star doesn’t appear.
The same assignment is editable from each campaign’s Inbound tab. It’s one setting seen from two ends, not two settings.
Agents
Section titled “Agents”Inbound vendors only.
Tick who can be handed this vendor’s live transfers. It’s the same setting as Users → Attributes → Vendors, edited from this end.
A ticked agent still has to be ready in one of the campaigns above to actually get the call — the two lists narrow each other.
If the card says this vendor has no attribute yet, save its name once and the agent list appears.
Saving
Section titled “Saving”Everything on this tab — the name, the codename, the status, the duplicate rule, the campaign ticks and the agent ticks — is staged until you press Save changes in the header. The badge beside it counts what’s waiting.