> ## Documentation Index
> Fetch the complete documentation index at: https://docs.famulor.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Built-in tools

> Give assistants safe actions for calls, messages, scheduling, and data capture

Built-in tools let an assistant take approved actions during a conversation. Configure them under **Assistant → Tools** and write a clear description of when each tool may be used.

If a tool is unavailable or misconfigured, the assistant receives a safe failure result and can continue the conversation.

## Available tools

| Tool                      | What it does                                                                 |
| ------------------------- | ---------------------------------------------------------------------------- |
| **End call**              | Ends the call after the assistant has completed the request and said goodbye |
| **Call transfer**         | Transfers the caller to a configured phone number                            |
| **Warm call transfer**    | Briefs a colleague before bringing the caller into the conversation          |
| **Transfer to assistant** | Hands the live call to another assistant in the same workspace               |
| **Send SMS**              | Sends a text message to the caller or a configured number                    |
| **Send email**            | Sends a fixed, templated, or assistant-written email                         |
| **Business hours**        | Checks a weekly opening-hours schedule in the assistant's timezone           |
| **Schedule callback**     | Confirms a future callback and adds it to **Audience → Scheduled Callbacks** |
| **Collect payment card**  | Securely captures a payment method into your connected payment account       |
| **Set call variable**     | Saves a value for later flow conditions, tools, emails, and webhooks         |

Calendar availability and booking are configured through [Calendar booking](/assistants/calendar-booking). Keypad input is configured with a **Collect** node in the [Flow Builder](/flow-builder/overview).

## Transfers

### Phone transfer

Choose a destination, transfer type (cold or warm), and the condition under which the assistant should transfer — describe it in as much detail as you can, since precise wording makes the trigger more reliable. You can also let the assistant determine the destination number dynamically instead of fixing it.

**Cold transfer** connects the caller straight through to the destination. Set a ringing timeout (15–80 seconds, 30 by default) before the attempt is considered unanswered.

**Warm transfer** briefs a colleague before connecting the caller — use it whenever the recipient needs context first. It needs a few extra settings:

| Setting                  | What it's for                                                          |
| ------------------------ | ---------------------------------------------------------------------- |
| Outbound number          | A workspace number with an outbound trunk, used to call the supervisor |
| Hold music               | Plays to the caller while the supervisor is briefed                    |
| Hold message             | Spoken to the caller right before they're placed on hold               |
| Briefing initial message | The first thing the assistant says once the supervisor picks up        |
| Summary instructions     | What the assistant should tell the supervisor about the call           |
| Connected message        | Spoken to the caller once the supervisor is connected                  |
| Ringing timeout          | 5–120 seconds (30 by default) before the attempt times out             |

**Fallback on failure** decides what happens if the colleague doesn't pick up: the assistant continues the conversation itself and offers alternatives, says goodbye and ends the call, or connects the caller straight through to a fallback number without a briefing.

### Transfer to another assistant

Hand off a live call to a different assistant in the same workspace — useful for language routing (detect the caller's language, transfer to a language-specialist assistant), a different compliance or consent path (move to an assistant configured for a different recording setup), or chaining specialized assistants (sales → onboarding, triage → expert) without provisioning a separate number for each step.

Choose the target assistant and a **Context Engineering Plan** — how much of the conversation it receives. Options run from the full message history down to a summary plus the last few messages (recommended), only the last few messages, a summary alone, or no prior context at all for a clean handoff. Optionally set a **message before transfer**, and choose whether the target assistant speaks its own initial message once it takes over.

The **Squad** view shows the resulting assistant-routing graph. Transfers to the same assistant are rejected, and a transfer limit prevents loops.

## Ending the call

Write the **End call** description as clearly as you'd explain it to a new hire — the tool only fires when its condition actually matches:

* **Simple** — end the call once all questions are answered and the caller no longer needs help.
* **More detailed** — also end after a successful booking, once the caller says goodbye, or once the conversation is clearly finished.

Cover the realistic paths you expect (success, goodbye, "nothing else needed") so the assistant doesn't hang up too early or drag a finished call out.

## SMS and email

For SMS, choose whether the recipient is the caller or a fixed E.164 number. The assistant must use a workspace number with outbound messaging enabled.

For email, choose a verified sender and one of three content modes:

* **Assistant-written** — creates the subject and body from the conversation.
* **Fixed** — always sends the exact configured content.
* **Template** — inserts call variables and stops if a required value is missing.

A successful send means the message was accepted for delivery; it does not guarantee delivery to the final inbox or handset.

## Business hours and callbacks

Business hours can contain one or more time windows for each weekday. The check always uses the assistant's configured timezone.

For callbacks, choose the destination and the maximum number of days customers may book ahead. The assistant must repeat the agreed time and obtain confirmation. Past dates and dates outside the allowed window are rejected.

## Payment-card collection

Connect your payment account under **Tools → [Agent Connectors](/assistants/agent-tools#agent-connectors)**, then add **Collect payment card** to the assistant or a Flow Collect node. The caller enters card details securely. Famulor never exposes the full card number or security code in conversation history.

Only use this feature where your legal basis, consent flow, and account permissions allow it.

<Note>
  Collecting a payment card costs extra credits at the workspace's **Card collection** rate; current rates are on the [Usage page](https://app.famulor.io/usage).
</Note>

## Call variables and current time

**[Set call variable](/assistants/variables)** lets the assistant store approved values such as a company name or appointment preference. Limit the allowed keys when the assistant should only update specific fields.

Every assistant also has a current-time tool. It uses the assistant's timezone to resolve requests such as “tomorrow at 3” or “next Tuesday”.

## API and MCP

Built-in tools can be managed through `PATCH /api/v1/assistants/{id}` and the assistant tools in [MCP](/api/mcp). Use `GET /api/v1/email-senders` or its MCP equivalent to list verified senders without exposing credentials.