Account

The Account tab answers three questions: who am I signed in as, which GoHighLevel sub-account does this dialer belong to, and are my contacts actually coming across. Its own subtitle says as much — Your account, sign-in, and connected GoHighLevel sub-account.

Account

Four read-only rows describing the session you’re in.

Row	What it shows
Account	The name of your dialer account — the company, not the sub-account
Name	Your own name
Email	The address you sign in with
Role	Whether you’re an admin or an agent

Nothing here is editable on this screen. People and their roles are managed under Users.

GHL location

The GoHighLevel sub-account campaigns dial contacts from. The card says it plainly: Open this page from inside the sub-account you want to use, then connect — we detect which one you’re in automatically.

Current: shows the connected sub-account’s ID, or Not connected.

The button reads Connect this sub-account the first time and Reconnect this sub-account afterwards. You’re never asked to type or paste anything — because the admin app is running inside GoHighLevel, pressing it works out which sub-account you’re viewing and asks you to confirm it. The confirmation names the sub-account and warns: This can’t be undone without contacting support.

If the connection worked but we can’t yet read that sub-account’s data, you’ll see: Connected, but we couldn’t reach this location’s GoHighLevel data yet. Ask your agency to install the app on this sub-account, then reload.

If the wrong sub-account is connected, you can’t fix it here

There is no disconnect button, and pressing Reconnect this sub-account from a different sub-account doesn’t move the connection — it’s refused, and tells you to open the dialer from the one you’re already connected to.

That’s deliberate. Your lists, vendor leads, Do Not Call entries and campaign contacts all belong to the connected sub-account, so re-pointing the account would strand every one of them. If it’s genuinely wrong, contact support — it isn’t a self-serve change.

Contacts sync

A live local copy of your GoHighLevel contacts. The dialer reads it to know a caller’s name, timezone and tags — that’s what drives inbound routing and the screen-pop an agent sees when a call connects.

The readout is one line:

• {n} contacts mirrored — how many contacts we currently hold
• a status badge: Syncing… while it’s filling, Live when it’s current, Not synced when nothing has come across
• · 1 location can’t sync in red if a connected sub-account is unreachable — hover it for the reason

Before you’ve connected a sub-account it reads No contacts mirrored yet — link a GHL location above to start syncing.

It keeps itself current on its own, both from changes GoHighLevel sends us as they happen and from a full re-check each day. You don’t normally have to touch it.

Re-sync from GHL

Forces a full re-scan of the connected sub-account now, instead of waiting for the daily one. It walks every contact again and then removes anything from the local copy that no longer exists in GoHighLevel — so it’s the button for contacts I deleted or merged over there are still showing up over here, and the button for a sync that’s stuck showing an error.

The badge flips to Syncing… and the count climbs while it runs; the card refreshes itself, so you can watch it without reloading. How long it takes depends on how many contacts you have — it runs in the background, and you can leave the screen.

What it does not do:

• It never writes anything back to GoHighLevel. It only reads.
• It doesn’t touch your lists, campaigns or leads. A list is a separate thing with its own sync.
• It won’t help if no sub-account is connected — connect one first.

Note

A re-sync is also the way out of a stuck sync. If a sub-account’s app was reinstalled, or the badge has been showing · 1 location can’t sync for a while, pressing Re-sync from GHL puts that location back into the queue rather than leaving it parked.