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

# Appointment scheduling with AI

> Let a Fliqr AI Agent check availability and book appointments using AI Functions connected to your appointment calendar.

Combine an AI Agent with appointment tools so contacts can ask for a time in natural language while your calendar rules stay authoritative.

## Building blocks

1. **Appointment calendar** configured in Fliqr AI (availability, duration, buffers)
2. **AI Function(s)** that check availability and/or book
3. **AI Agent** prompt that knows when to call those functions
4. Optional **Flow** confirmation and reminders

## Create AI Functions for scheduling

<Steps>
  <Step title="Configure appointments">
    Set up your calendar under the Appointments / scheduling tools in your workspace (availability windows, services, timezone).
  </Step>

  <Step title="Add an AI Function">
    Go to **AI Center → AI Tools → AI Functions → Add**.
  </Step>

  <Step title="Check availability function">
    Name it clearly (`check_appointment_availability`). Description: “Allows the user to check open appointment slots.” Collect fields like `preferred_date` / `service_type`. Point the function at the flow/action that runs **Check Availability**.
  </Step>

  <Step title="Book function">
    Create `book_appointment` that collects name, slot, and contact details, then triggers your booking flow/action.
  </Step>

  <Step title="Output message via custom field">
    Have the Flow write the result into a text custom field and use that field as the function **output message** so the Agent rewrites a natural reply (do not send a second raw Flow message if it would duplicate).
  </Step>

  <Step title="Enable on the Agent">
    Attach the functions on the Agent and test phrases like “Do you have anything Tuesday afternoon?”
  </Step>
</Steps>

## Prompt guidance

```text theme={null}
You help users schedule appointments.
When they ask about times, call check_appointment_availability.
When they confirm a slot, call book_appointment.
Never invent open slots — only offer times returned by tools.
Always confirm timezone and service type.
```

<Tip>
  Function names should be multi-word and descriptive (`book_appointment`, not `book`). Parameter names should be meaningful (`email`, not `AAAAAA`).
</Tip>

## Next

<CardGroup cols={2}>
  <Card title="Functions & actions" icon="bolt" href="/docs/core-concepts/ai-agents/functions-actions">
    Deeper function design and HTTP tools.
  </Card>

  <Card title="Human handover" icon="headset" href="/docs/core-concepts/ai-agents/human-handover">
    Escalate complex booking edge cases.
  </Card>
</CardGroup>