Why you configure tools, not build them
A tool runs live, mid call, while a real person is on the phone. If a coverage check returns the wrong answer or a transfer dials the wrong place, the call is already going sideways before anyone notices. So tools are code, and we own it, built deterministically where it matters so it runs on hard logic, not the agent’s best guess. When you need behaviour that isn’t a tool, you write a skill in plain English instead.What’s in the library today
Appointment Booking
Offers real open times from your calendar and books the one the lead accepts.
Choose its calendar in the booking settings. It is a
capability, so adding it also brings the outcome and
the campaign route that go with a booking.
Service Area Check
The caller says their ZIP, and the agent checks it against your coverage list
with real code, not judgment. It never guesses “yes, we cover you.” You set the
ZIPs and what to do when someone’s out of area.
Live Transfer
Warm transfers the caller to a real person, with a spoken introduction. You set
the destination number and what the agent says as it transfers. The agent
confirms first and uses that message during the handoff.
Add a Tag
Tags the lead in GoHighLevel mid call, so your own workflows fire while the
agent is still on the phone: send a link, start an automation. The agent
never says the tag out loud. Needs the sub-account to use GoHighLevel.
Check a Tag
Looks up whether the lead already has one specific tag, so the agent can
adapt on the spot: existing customer, VIP, already booked. It says a natural
“give me a moment” while it checks. One tag per skill, not a list. Needs the
sub-account to use GoHighLevel.
A tool marked smart, like Service Area Check, runs a configured action rather
than the agent’s judgment. When the answer has to be exactly right, that’s the
kind you want.
Tools you already have
Three of these, Appointment Booking, Live Transfer, and Add a Tag, are also capabilities. The library shows an ability as added when it is installed. Check the actual inventory rather than assuming anything from the agent’s name, script or campaign type. An agent may have none. A capability is more than a tool. Adding one from the library also brings the fields it fills in after the call, the route your campaign takes when it happens, and the setting it needs before it can run. Remove it and all of that goes with it. That is why the library says capability on those three. Some other tools arrive with the agent and are marked built in, like ending the call. You can see what each does and adjust when the agent reaches for it, but you don’t add or remove those here.Changing the transfer message
See Live Transfer settings for destination and routing choices. In Skills & Tools → Live Transfer, What the agent says as it transfers controls the handoff wording. It is separate from When should the agent use this?, which decides when the transfer tool runs, and from the destination number. Edit the handoff message in the Live Transfer panel, or ask the chatbot to change it. You can write the exact sentence or describe the tone you want. Leaving the message blank restores “Just a second while I connect you.” Your transfer destination and other capabilities stay as they are.Adding and removing
Add a tool from the library, fill in what it needs, and save. It’s live on that agent. There’s no on and off switch: a tool being on the agent is the on state, so to turn one off you remove it. Everything you add is scoped to this one agent.In the API
Each tool is a skill record with atype, created with
Create an agent skill:
The catalog
endpoint lists every tool the platform offers, with
fields for what you
would need to fill in. It is the shared catalog, not this agent’s state: what
is already on the agent comes back on
Get campaign as capabilities and
tools.
Every tool is defined in the Glossary.