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 behavior 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.
Point it at a calendar on your campaign. 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. The agent confirms first and never narrates the handoff.
Add a Tag
Tags the lead in your CRM 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.
Check a Tag
Looks up whether the lead already has a 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.
A tool marked smart, like Service Area Check, runs deterministic code rather
than the agent’s judgment. When the answer has to be exactly right, that’s the
kind you want.