Skip to main content
Autocalls.ai offers built-in “tools” that your AI assistant can use during a call. These help you shape the conversation flow and automate actions like transferring calls or scheduling appointments.

​
1. End Call Tool

  • Purpose: Tells the AI to politely wrap up the conversation.
  • How It Works: You can specify in the system prompt or logic, for instance: “If the user says goodbye, end the call.”
  • Configuration: Enable in Tools & actions → Default tools and define conditions in your system prompt that should trigger the end call.

​
2. Cold Call Transfer

  • Purpose: Moves the caller from the AI assistant to a human agent or external phone number.
  • Use Cases: Warm leads on a sales call, escalations on a support call, etc.
  • Configuration: Set up in Tools & actions → Default tools by adding the phone number or department the call should go to, and optionally a short hold message.

​
3. Warm Call Transfer

  • Purpose: Transfers the call with hold music, and briefs the person picking up before the caller is connected.
  • Use Cases: Handovers where context matters, so the colleague does not start from nothing.
  • Configuration: Set up in Tools & actions → Default tools with the destination number and what the briefing should cover.

​
4. Transfer to Assistant

  • Purpose: Hands the conversation to a different AI assistant instead of a person.
  • Use Cases: A receptionist assistant routing to a sales or support assistant.
  • Configuration: Set up in Tools & actions → Default tools by choosing the assistant to hand off to.

​
5. Appointment Scheduler

  • Purpose: Lets the AI check your calendar availability and book appointments automatically.
  • Available Integrations: Cal.com, GoHighLevel, and Calendly calendar systems
  • Typical Flow:
    1. AI offers scheduling.
    2. Caller selects date/time.
    3. AI confirms and sends a confirmation (using email or SMS if configured).
  • Configuration: Set up in Tools & actions → Default tools with your calendar integration.

​
6. DTMF Input

  • Purpose: Allows the AI to send keypad inputs during calls to navigate phone menus, IVR systems, and automated workflows.
  • How It Works: The AI can press phone keypad buttons (0-9, *, #) when encountering automated systems or menu prompts.
  • Use Cases:
    • Navigate through company phone menus
    • Enter extension numbers to reach specific departments
    • Input security codes or account numbers
    • Bypass IVR systems to reach human agents
  • Configuration: Enable in Tools & actions → Default tools and include instructions in your system prompt about when to use DTMF.

​
7. Collect Keypad Input

  • Purpose: Collects digits the customer types on their phone keypad, such as an order number or a PIN.
  • Difference from DTMF Input: DTMF Input presses digits to navigate someone else’s menu. Collect Keypad Input reads digits the customer presses for you.
  • Use Cases: Reference numbers, dates of birth, anything the assistant keeps mishearing when spoken.
  • Configuration: Set up in Tools & actions → Default tools, then tell the assistant in the prompt when to ask for the digits.

​
8. No-Code Automation Platform

  • Purpose: After calls, the AI can trigger actions in the automation platform (like updating a CRM, sending an email, or logging results in Google Sheets).
  • Configuration: Set up triggers and actions in the Automation Platform, then link to your assistant via webhook configuration in Post-call Actions.

​
9. Custom Mid-Call Tools

  • Purpose: Create your own custom API integrations that the AI can use during calls.
  • Use Cases: Check inventory, verify customer data, fetch real-time information, or integrate with your own systems.
  • Types: A HTTP request tool calls your own endpoint directly, or an Automation Platform tool auto-creates a linked no-code flow for multi-step logic.
  • Configuration: Set up in Tools & actions → Custom mid call tools by defining API endpoints, parameters, static fields, and when the AI should use them. Values support dynamic system variables like {{customer_phone}}.
  • For detailed setup instructions and examples, see our Custom Mid-Call Tools Guide.

​
10. MCP Servers

  • Purpose: Connect a remote Model Context Protocol server so the AI can use many external tools at once, discovered automatically.
  • Use Cases: Connect a platform like HubSpot, your internal APIs, or knowledge tools to pull live data and trigger actions mid-conversation.
  • Configuration: Add a server under the Mid call tools / MCP page, then assign it to an assistant. See the MCP Servers Guide.
Note: Tools can be combined. For instance, the AI can use a custom tool to check availability, then schedule an appointment, and finally transfer to a human agent if needed.