Manage your clients

A client in GodSetter is one of your CRM sub-accounts: the business the AI agent books appointments for. The Clients page is where you see them all, tell which ones are ready to receive calls, and open the one you need to adjust.

You rarely create clients by hand — they arrive from GoHighLevel with "Sync sub-accounts", active from the start.

What a client is

A client links three things: a GoHighLevel location (the sub-account whose contacts and calendars the agent works with), an optional calendar to book into, and the flags that decide whether it takes calls at all.

Every call GodSetter places belongs to a client: the calendar the agent offers, the CRM the tags and notes are written into, and the {{client_name}} the agent says out loud all come from that row.

The numbers at the top

Four cards summarize the whole agency — they never follow the search or the filters below them:

• Total clients and Active clients — how many exist, how many are switched on.
• Calls · 7d — calls placed for all your clients in the last 7 days.
• Average conversion — booked calls over total calls in the same 7 days, with the count of appointments underneath.

Search and filters

"Search by name, niche or agent…" matches the client name, its niche and the name of the agent template assigned to it. It ignores accents and case, so Nunez finds Núñez.

Four pills filter by status, each with the count of matches inside the current search — so Active 3 means three among the rows you are looking at:

• All
• Active — switched on and ready.
• To configure — the client has nowhere to book: no calendar of its own and no active outbound agent carrying a default calendar. This is the only state that needs your attention; the row also shows a Configure link straight to the client.
• Inactive — switched off. Its leads are refused at the door with client_inactive_or_not_found.

Search, filter and page are kept in the URL, so a filtered view can be bookmarked or shared. The table shows 25 clients per page.

The table, column by column

Sync sub-accounts

"Sync sub-accounts" imports (or refreshes) your GoHighLevel sub-accounts as clients. It also runs on its own once a day, so the button is only for when you don't want to wait.

New sub-accounts arrive active and without a calendar of their own — they book into the default calendar of the agent that calls them, matched by name in each sub-account. Existing clients only get their name refreshed: your calendar, niche and flags are never overwritten by a sync.

If the button answers "GoHighLevel not connected or unreachable. Check it in Connections.", fix the connection first — Connect your CRM.

While you have no clients at all, the page leads with "Import your sub-accounts from GoHighLevel" and that same button instead of an empty table, plus a discreet "or create a client manually" link.

Inside a client

Open a client (or use New client) and you get one form:

• Name — what you call it in GodSetter; pre-filled from the sub-account when you pick one.
• GoHighLevel location / GHL Location ID — the sub-account. In the New client form it's a picker; ids are only typed by hand when GoHighLevel is not connected or cannot be read, and the form says which of the two it is.
• GHL Calendar — a dropdown of that location's calendars (a plain GHL Calendar ID field if they can't be loaded). It is optional: "Empty = the client books into the default calendar of the agent that calls it; set one here to override it for this client only." One default on the agent therefore covers every client of the same snapshot, and a calendar picked here always wins for this client.
• Niche — a free-text label (up to 60 characters) with suggestions from the niches you already use. It is descriptive only: it never decides which agent calls or answers.
• Agent Template — the client's default agent. It is used only by the legacy agency-level webhook …/api/webhooks/ghl-trigger/{publicId}, which calls with whatever agent is set here. With the recommended per-agent webhook URL the agent is decided by the URL the workflow posts to, so this field can stay empty — see Wire your CRM workflow to an agent.
• Recording on — archives this client's call recordings (the global setting can turn archiving on for everyone) and resolves the {{recording_disclaimer}} placeholder in the prompt, so the agent announces the recording.
• Client active — the master switch. Turn it off and every new lead for this client is refused at the door.

Then Save.

Good to know

• Deactivating is not deleting. An inactive client keeps its leads, calls and history; it simply stops accepting new triggers.
• A client with nowhere to book never gets called. The trigger answers skipped with reason not_configured. Give the calling agent a default calendar (agent editor → Identity & routing) or pick one on the client.
• The calendar is resolved at dial time, in the sub-account of the call. If GoHighLevel can't be read at that moment the lead is parked and retried, not lost — details in How the AI books appointments.