# Tools

> What the AI can do mid-conversation: capture leads into the CRM, book with the scheduler, open tickets, and call any of 235 integrations — scoped to the step that needs them.

Tools are what turn an answering machine into a front office: the AI doesn't just *say* it can book you in — it books you in. Tools are attached to agents, and inside a [workflow](/docs/workflows/steps) they can be scoped to a single step, so only the booking step can touch the calendar.

## Built-in tools

| Tool | What it does |
| --- | --- |
| Lead capture | Collects the fields of the CRM card you bound (name, phone, job details…) and creates the deal — one binding shared by chat and voice. See [CRM overview](/docs/crm/overview). |
| Scheduler booking | Offers real slots from a [booking page](/docs/scheduler/overview) and books one, confirming by text. |
| Send to help desk | Opens a [ticket](/docs/helpdesk/overview) with the transcript when a human should take over. |
| CRM writes | Creates or moves cards as a conversation progresses — "mark them contacted". |

## Connector tools

Any of the [235 integrations](/docs/integrations/overview) can back a tool: look up an order in Shopify, check a customer in Stripe, write a row to Google Sheets, post to Slack. Connect the account once (business-level or per-agent), then attach the tool where it's needed. Requests are fenced to the product's own API host, and credentials are encrypted and never shown to the model.

## Step-scoped tools

In a flow, tick a tool on a specific step and it exists *only there*. The order-taking step can push to the POS; the small-talk step can't. This is the main defense against tools firing at the wrong moment — scope tightly.

> **THE LEAD TOOL IS THE WORKHORSE:** Bind the lead-capture tool to the right board and column and every door — chat, phone, DMs — files its own leads with [attribution](/docs/crm/attribution). Most businesses need that before any exotic connector.