Skip to main content

LeadConnector

This integration connects Knock Knock App to the HighLevel platform, which now appears as LeadConnector throughout the app (it was previously shown as GoHighLevel — it's the same platform and the same connection). Connecting lets you sync contacts, calendars, and pipelines across both platforms. This is ideal if you use LeadConnector as your main business management tool.

Connecting LeadConnector​

To connect your LeadConnector account:

  1. Go to Integrations in the sidebar.
  2. Find LeadConnector and click Connect.
  3. You will be redirected to LeadConnector to authorize the connection.
  4. Sign in and grant Knock Knock App access.
  5. You will be redirected back with the connection confirmed.
note

You need an active LeadConnector account. The integration works with both agency and sub-account level access.

Installing from the LeadConnector Marketplace​

You can also start from the other side: install the Knock Knock app directly from the LeadConnector marketplace directory, at either the agency level or for a single sub-account.

  1. Find Knock Knock App in the LeadConnector marketplace and click Install.
  2. Choose whether to install for your agency or a specific sub-account.
  3. After the install, you land in Knock Knock App to finish connecting. If you're already logged in, a Connect LeadConnector? confirmation appears so the connection is bound to the right Knock Knock account.
  4. For agency-level installs, you may be asked to map which sub-account to sync — same as the sub-account mapping step described below.

Both routes end up with the same connection; use whichever is more convenient.

Sub-Accounts​

If you manage multiple businesses or clients through LeadConnector, you can connect specific sub-accounts to Knock Knock App:

  • Select which sub-account to sync during setup.
  • Each sub-account's contacts and data are kept separate.
  • You can switch between sub-accounts in the integration settings.
tip

If you are an agency managing multiple client accounts, connect each sub-account individually to keep data organized and separated.

LeadConnector Settings​

Once connected, the card shows the connection state ("LeadConnector is connected and mapped to your account") with two chips — Booking on/off and Visit logging on/off — and a Configure button. Configure opens LeadConnector settings, "everything this app does inside your LeadConnector account", in up to six tabs with one Save changes for all of them:

  • Booking — whether and where bookings land.
  • Contact data — website-visit logging and the custom fields enrichment writes to.
  • Recognition tokens — the tracking token that lets Knock Knock App recognize your contacts when they click through.
  • Team access — which Knock Knock account each LeadConnector user is signed into inside LeadConnector, or no access (account owner only).
  • App page — the name of the app's item in your LeadConnector sidebar, or hiding it.
  • Menu link — an optional plain link in your LeadConnector sidebar that opens the owner account.

Calendar Sync​

The LeadConnector calendar integration works similarly to other calendar connections:

  • Your LeadConnector calendar events are used to determine availability.
  • Appointments booked through Knock Knock App can be synced to your LeadConnector calendar.
  • Availability is reflected in real time.

Use for Booking Toggle​

The Booking tab of LeadConnector settings has a Use for booking switch and a Calendar picker.

  • On (default) — Your LeadConnector calendar is used for all appointment bookings made through Knock Knock App. AI agents and the widget's booking flow pull availability from LeadConnector and write new bookings back to your LeadConnector calendar.
  • Off — Booking attempts skip the LeadConnector calendar entirely. Use this if you've connected LeadConnector only for contacts and pipelines and want bookings to flow to a different calendar (Google Calendar or Calendly).

The toggle is per-company. Changes take effect immediately on new booking attempts. A calendar you've since deleted in LeadConnector is dropped quietly rather than blocking the save.

Booking on Multiple Calendars​

If you have several bookable LeadConnector calendars — say a sales demo and a support consultation — you can let visitors choose. Turn on Let visitors pick a calendar on the Booking tab and tick the Calendars visitors can choose from (leave all unchecked to show every active calendar). With it on, the widget and the AI agents ask "What would you like to book?" first, then show availability from — and book on — the chosen calendar. This is opt-in; with it off, everything books on your single selected calendar as before. A calendar you haven't ticked is never offered or booked, even by the AI.

Each calendar on offer gets a Purpose of meeting box (up to 300 characters, e.g. "pricing questions, plans and upgrades"). The AI in chat and on calls asks what the meeting is about and books the calendar whose purpose matches. Just describe the topics — each purpose is already linked to its calendar, so there's no need to name the calendar — and keep topics distinct between calendars. A calendar with no purpose is matched on its name and LeadConnector description. See Meeting Booking for the visitor's side of the flow.

Meeting Length and Taken Slots​

Bookings use each calendar's own slot duration, so 45- and 60-minute calendars book (and reschedule) at their real length, and the AI tells the visitor the length that was booked. If a slot is taken while the visitor is booking, the widget asks them to pick another time and — when the calendar has its own booking page — adds a Book Meeting button as a fallback. See When a Slot Is No Longer Free.

Contact Data​

The Contact data tab controls what Knock Knock App writes onto your contacts beyond the basics:

  • Log website visits (off by default) — every completed visit by a recognized contact is posted as an internal comment on the contact's LeadConnector conversation, about every 15 minutes: Website visit — date, time, the source (and, on the first visit, the campaign and referrer), the page count and duration, the pages viewed, and a link to the session recording. Comments post only once a visit has ended, and LeadConnector doesn't allow them to be deleted afterwards.
  • Custom fields — the fields enrichment fills: LinkedIn URL, Company LinkedIn, and Job title. Pick an existing field from the suggestions or type a new name to have it created; leave one blank to skip it. A visitor's LinkedIn profile and their employer's LinkedIn page are written onto matched and newly created contacts, never overwriting a value that's already there. (The post-call fields belong to each outbound agent — see below.)

Recognition Tokens​

Every link in your LeadConnector emails can carry a token that recognizes the contact the moment they land on your site — the same mechanism Agent K relies on. The Recognition tokens tab decides which contacts get one:

  • App-created contacts — contacts this app creates get a token at creation.
  • Auto-sync other contacts — a daily sweep adds tokens to contacts created outside the app.
  • Add tokens to existing contacts — opens Contacts without a token, a paged list where you Select all listed or pick individually, then click Add token to N contacts and watch the progress. When every scanned contact already has one, it says so.

Append ?kk={{contact.kk_token}} to the links in your templates to put the token to work.

Bookings Arrive Complete​

Bookings synced to LeadConnector fill in contact details rather than leaving gaps:

  • If the LeadConnector contact has no phone number, the visitor's phone from the booking is back-filled onto the contact. An existing phone number is never overwritten.
  • If an AI-chat booking only carried an email, the phone number and name the visitor gave in chat are used to complete the booking.
  • The appointment's description lists the visitor's Email, Name, and Phone. When the visitor didn't give a name or phone — common on voice calls — the matched contact's own name and phone are used instead of "Unknown".
  • An email that doesn't look like a real address is refused before anything is written to the contact; the AI asks the visitor to spell it again.

Lead Source Note​

When Knock Knock App captures a new lead, the LeadConnector contact gets a Lead source note a minute or so later: whether it came from a chat, a call, or a website form, the page and product it came from, where the chat or call started, the landing page, the traffic source, UTMs, and the Google Ads click ID. It's written for every account with LeadConnector connected — there's no setting — and at most once per visit.

The Google Ads click ID is also written to a gclid contact custom field (created the first time it's needed), always holding the visitor's latest ad click, so you can use it for Google Ads offline-conversion imports.

Company-Level Matches​

When a visitor hasn't told you who they are, enrichment may link their visit to an existing contact at their company as a best guess. That guess never applies to a visitor Knock Knock App can already identify, and it's released the moment the visitor gives their name, email, or phone — from then on their visits, chats, and notes go to their own contact, not the guessed one. The guessed contact itself is never changed.

AI Call Recordings in Conversations​

Recordings of AI calls are attached to the contact's LeadConnector Conversations thread as a playable message, so your team can listen without leaving LeadConnector. The recording is attached once the audio is ready — typically a few minutes after the call ends. A plain link to the recording is also appended to the call transcript note. Recording links use a neutral /recordings/… path (and your own domain on white-labeled setups), so they never name the voice provider behind them.

Post-call notes on inbound calls wait for the call summary before posting, so they never arrive incomplete.

note

Playable recordings require the conversations message-write permission. If the card shows Permissions needed, reconnect to grant it — the transcript note with the recording link works either way.

Send SMS Workflow Action​

The Knock Knock marketplace app adds a Send SMS action you can drop into any LeadConnector workflow. Pick one of your SMS agents and the message is sent from that agent's phone number as a workflow step — appointment reminders, follow-ups, review requests, anything your workflows already trigger.

Note on Chat Start​

When a visitor starts a chat, a note titled "Web Chat — <date and time>" is posted on their LeadConnector contact recording which page of your site the chat began on ("Chat started from"). It's written for every account with LeadConnector connected, once per conversation.

Post-Call Summary Field​

Outbound call agents have a post-call summary field setting: pick a LeadConnector contact custom field, and after each call the AI writes its post-call summary into that field on the contact. Leave the setting blank to disable it.

Pipeline Management​

Connect your LeadConnector pipelines to keep your sales process in sync:

  • New leads captured in Knock Knock App can be added to a LeadConnector pipeline stage.
  • Lead status updates flow between platforms.
  • Your sales team can track progress from either platform.
info

Pipeline sync helps you maintain a single source of truth for your sales process. Changes made in either platform are reflected in the other.

Opening Knock Knock App Inside LeadConnector​

Your team can use Knock Knock App without leaving LeadConnector. There are two ways in from the LeadConnector sidebar: the app page (recommended) and an optional menu link.

The App Page​

Installing the LeadConnector app adds its own page to your sub-account's left menu, named Next Level AI by default. Everyone who opens it is signed into their own Knock Knock account — see Team Access.

The App page tab of LeadConnector settings changes how it shows:

  • Name — the item's name in the sidebar. Leave it blank to use your agency's name, or the default name if you have no agency. Name changes can take a few minutes to show.
  • Hide from the sidebar — your team then can't open the app from inside LeadConnector.

LeadConnector doesn't let apps rename their own page, so these two settings are applied by a short script in LeadConnector. A LeadConnector agency admin adds it once, for every sub-account in the agency — the tab (and your agency's settings) show the script under Apply it in LeadConnector:

  1. In LeadConnector, switch to the agency view and open Settings → Company.
  2. Open the White Label tab.
  3. Copy the script into the Custom JS field and click Save changes.
  4. Reload LeadConnector.

Only agency admins see that setting. If that isn't you, send the script to whoever manages your LeadConnector agency.

Updating the App​

When a new version of the LeadConnector app is available and you haven't opened the app page yet, a blue bar at the top of the portal reads "A new version of the LeadConnector app is available. Update it from your App Marketplace, then open Next Level AI in your sub-account sidebar." Update the app in LeadConnector and open the page once; you can also dismiss the bar.

The Menu link tab manages a plain link in your LeadConnector sidebar that opens Knock Knock App. Unlike the app page, it always signs in as the account owner, and it stops working once you set up Team access. Because the app page covers it, new connections don't get one — if you still have one, the tab says "Not needed: the app page covers it. Remove it so the app doesn't show twice."

  • Add link / Remove link — account owner only. Removing asks first ("Remove the menu link?"); the app page stays, and you can add the link back at any time. Adding a link needs your own LeadConnector agency account connected, because menu links live in it.
  • If your agency connected LeadConnector for you, the link lives in your agency's LeadConnector account, so your agency adds or removes it from its portal.
  • To add a link yourself in LeadConnector instead, copy the URL shown with Copy. On a white-labeled agency setup it uses your agency's custom domain.

Team Access​

By default, everyone who opens the app page is signed in as the account owner. The Team access tab (account owner only) lists each LeadConnector user by name and email, with a Signs in as picker:

  • One of your Knock Knock users — yourself or one of your team members; they're signed into that account.
  • No access — turns that user off. They see "Your account owner has turned off access for your LeadConnector user."
  • Not linked — the picker says what this means. With nobody linked it's Not linked (owner account). Once anyone is linked it becomes Not linked (no access): unlinked users are blocked with "Your LeadConnector user is not linked to an account here. Ask your account owner to link it." — so link yourself too.

Turning users off without linking anyone only blocks those users; everyone else keeps the owner account.

Bookings and the Identity Graph​

Appointments booked through LeadConnector — whether booked by an AI agent, through the widget, or directly in LeadConnector — are mirrored into the visitor's Identity Graph profile. The next time that person returns and talks to your chat or voice agent, the agent already knows about the meeting and can speak to it. This is also what powers Nox's answers to questions like "what meetings are scheduled this week?".

The Old LeadConnector App Has Been Retired​

Knock Knock App now connects only through the current LeadConnector marketplace app. Connections made with the old app no longer work, and nothing syncs until you reconnect:

  • A red bar across the top of the portal reads "LeadConnector has stopped syncing: your account is connected through the old app, which no longer works. Reconnect to install the new app." Its Reconnect button opens the Integrations page. The bar can't be dismissed.
  • The LeadConnector card shows Install the new app. Click Reconnect, sign in to LeadConnector, and approve the permissions.

Your sub-account mapping, calendar selection, and other settings are kept.

Missing Permissions​

When the app asks for permissions your current connection hasn't granted yet, the LeadConnector card shows Permissions needed, lists them under "Not yet granted", and offers Reconnect to upgrade. Your connection keeps working in the meantime; reconnecting grants the new permissions and turns on the features that need them.

Disconnecting LeadConnector​

To disconnect:

  1. Go to Integrations in the sidebar.
  2. Find LeadConnector and click Disconnect.
  3. Confirm the disconnection.
warning

Disconnecting will stop all syncing between Knock Knock App and LeadConnector and uninstall the Knock Knock App from your LeadConnector account. Data that has already been synced will remain in both platforms.

Next Steps​