# How to set up a Cal.com AI phone agent that books appointments

By Samuel Oram-Jones

You let a Bland AI phone agent book appointments in Cal.com by connecting your Cal.com account once, creating an Integration tool on that connection, setting the tool's fields, and tagging it into your agent's prompt. Each step is a click or a form field in Bland's dashboard, set out in order in Bland's [Cal.com walkthrough](https://docs.bland.ai/tutorials/tools/integration-tools).

A Bland agent can schedule a meeting on Cal.com when a caller wants to book time, and then read the booking's start time back to them. Bland's [no-code AI call center](/no-code-ai-call-center) guide and [no-code AI phone agents](/no-code) hub cover the wider setup.

## What do you need before you start?

You need a Bland agent to tag the tool into, and a Cal.com account with its API key. [Building your first AI phone agent](/no-code/how-to/build-your-first-ai-phone-agent) covers the agent.

Salesforce, HubSpot, Cal.com, Calendly, Notion, and Slack connect from Bland's dashboard. Anything else connects through Bland's REST API and webhooks, which Bland's forward-deployed engineers can help with on Enterprise.

The same pattern applies to every built-in integration: connect an account once, build a tool on it, and tag the tool into a prompt.

## How do you connect Cal.com and build a booking tool in Bland?

You connect Cal.com to Bland and build a booking tool in four steps, all in Bland's dashboard.

### Step 1: Connect Cal.com

1. Set the sidebar selector to **All agents** and open **Tools** under Resources.
2. Open the **Connections** tab.
3. Click **Add connection** and choose **Cal.com**.
4. Give the connection a name, like "Sales Team Calendar", and enter your Cal.com API key.

You only do this once. One connection can power as many tools as you need. You can also start from the tool builder: **New connection** at the top of its connection list opens the same flow.

### Step 2: Create the tool

1. From inside your agent, open **Tools** and click **Create tool**.
2. Choose **Integration**.
3. Pick your Cal.com connection, then the booking action.

The fields the tool needs come from Cal.com, so you do not define them yourself.

### Step 3: Configure the tool

1. **Describe when to use it.** The agent reads the description to decide when to call the tool. Write the trigger: "Book a meeting once the caller has agreed to a specific time."
2. **Fill in each field.** Give each field a fixed value, have the agent fill it from the conversation, or use a variable already on the call. A calendar or event type is usually fixed. The attendee's name and email usually come from the caller.
3. **Choose the output fields.** Check the fields the agent should be able to use, and keep `ok` checked so the agent can tell when a booking failed.
4. Save the tool.

### Step 4: Tag it into a prompt

1. In the agent's **Prompt**, type `@` and pick the tool. It then appears under **Tool references**.

A tool that is not tagged is never called.

## Can Norm build a Cal.com scheduling agent for you?

Yes, [Norm](/norm/no-code-agent-builder), Bland's AI assistant, can build a Cal.com scheduling agent from a plain-English description, and [how Norm works](/norm/how-it-works) explains how its changes reach live calls.

Norm works in your agent's development environment, so saving a version does not change live traffic until that version is published to staging and then promoted to production.

## How do you know a Cal.com booking worked?

A Bland agent knows a booking worked from the fields the Cal.com booking action returns. In addition to the default `ok`, `message`, and `data` fields, the action returns these.

| Field | What it holds |
| - | - |
| `meeting_url` | The booking URL |
| `booking_id` | Unique identifier for the booking |
| `booking_uid` | UID for the booking |
| `status` | Booking status |
| `start_time` | Scheduled start time |
| `end_time` | Scheduled end time |
| `attendee_email` | The attendee's email |
| `attendee_name` | The attendee's name |
| `attendee_timezone` | The attendee's timezone |

To use a field in a prompt, check it under **Output fields** and write its bare name, for example:

```text
Confirm the booking and read the start time back to the caller: {{start_time}}.
```

Under **Tools** at All agents, Bland's **Analytics** tab shows how often each tool is called and how often it fails. You can also [talk to your agent in your browser](/no-code/how-to/test-an-ai-phone-agent-in-your-browser), which needs no phone number, and [testing an AI phone agent before launch](/no-code/how-to/test-an-ai-phone-agent-before-launch) covers evaluations, Bland's test cases that run before you promote, once the Evals feature is enabled for your organization.

## What can go wrong when a Bland agent books in Cal.com?

A Cal.com booking tool can hit five of the common failures Bland names for its tools, and each one has a fix in Bland's dashboard.

- **The agent never calls the tool.** Look at **Tool references** under the prompt. A tool missing from that list is untagged and will never be called, so tag it in the prompt where it should run.
- **The tool fires at the wrong moment.** The agent chooses from the description. Rewrite it to say when to use the tool and when not to.
- **The agent calls it but ignores the answer.** Check **Output fields**. Only the fields you checked are available to the agent.
- **You edited a tool and the agent still uses the old version.** Tagging attached a copy, so open the tool from **Tool references** and make the same change there.
- **It works on the agent but not inside a pathway.** A pathway is a branch of the agent's behavior with instructions of its own, and tools do not follow the agent into one. Tag the tool again inside that pathway.

Idaho Housing and Finance Association saves $750,000 a year by replacing its IVR with Bland, which handles 4,000 inbound calls a day and cut average call time by 20%.

> "We save thousands of dollars a day."

Greg Blake, Chief Information Officer, Idaho Housing and Finance Association

## Frequently asked questions

### Does Bland have a no-code option?

Yes. Norm, Bland's AI assistant, builds voice agents using natural language descriptions, and Bland's dashboard includes a visual builder for non-technical users.

### Do I need a developer to let my AI phone agent book in Cal.com?

No. Bland builds AI phone agents that answer inbound calls and place outbound calls. Your team builds and edits them in plain English with Norm or in Bland's visual builder, with no engineers needed on your side. Enterprise customers also get Bland's forward-deployed engineers.

### What do I need from Cal.com to connect it to Bland?

A Cal.com account and its API key. You enter the key once, when you name the Bland connection, with a name like "Sales Team Calendar".

### Can one Cal.com connection power more than one Bland tool?

Yes. You only connect Cal.com once in Bland, and one connection can power as many tools as you need.

### Why does my Bland agent never book a meeting?

A Bland agent that never books a meeting may not have the Cal.com tool tagged into its prompt. Check Tool references under the prompt, because a tool that is not listed there is never called.

### Does Norm change a Bland agent that is already taking calls?

No. [Norm](/norm) edits your agent in development, so a change reaches live calls only after a saved version is published and promoted to production.
