AI Agents

How does Scheduling work?

Updated October 7, 2026

Scheduling lets an AI Answer node check live calendar availability and help a customer book an appointment directly inside the conversation.

It can be used for:

  • Consultations
  • Sales demos
  • Service appointments
  • Property viewings
  • Tours
  • Test drives
  • Assessments
  • Meetings
  • Other bookable appointments

The customer does not need to leave the conversation and open a separate booking page.

How Scheduling works

Scheduling is a skill inside the AI Answer node.

When Scheduling is enabled and configured, AI Answer can:

  1. Understand that the customer wants to book
  2. Check your configured availability
  3. Offer available times
  4. Collect the required contact details
  5. Confirm the selected appointment

The calendar determines which times are actually available.

AI Answer handles the conversation around the booking.

Example booking conversation

A customer asks:

“Do you have anything available Thursday afternoon?”

AI Answer can check the configured calendar and offer available times.

For example:

“I have 1:30 PM, 3:00 PM, or 3:30 PM available. Which works best?”

The customer can choose a time conversationally.

Once the required details are collected, the booking can be confirmed inside the same conversation.

Configure Scheduling before using it

Before AI Answer can book appointments, configure the scheduling rules for the booking experience you want to offer.

Settings can include:

  • Available days and hours
  • Appointment duration
  • Available time slots
  • Time zone
  • Buffer time between appointments
  • Minimum advance notice
  • How far ahead customers can book
  • Required contact information
  • Calendar settings

The AI agent uses these rules when offering and confirming appointments.

Availability comes from your calendar

Scheduling should only offer times that are actually available.

The calendar is the source of truth for appointment availability.

AI Answer can phrase the response naturally, but it should not invent appointment times.

For example, if 2:00 PM is already booked, the AI agent should not offer that time.

This keeps the conversational experience flexible while keeping the booking itself controlled by real availability.

Customers can ask naturally

Customers do not need to use a specific date format.

They can ask things like:

“Do you have anything tomorrow afternoon?”

“Can I come in next Tuesday?”

“Anything after work this week?”

“Is Saturday available?”

“Can I book a demo sometime next week?”

AI Answer can interpret the request and check availability that matches it.

The AI agent can offer available times

When the requested time is not specific enough for a single booking, AI Answer can offer a short list of available options.

For example:

Customer:

“I need a consultation Thursday afternoon.”

AI Agent:

“I have 1:30 PM, 3:00 PM, and 4:30 PM available on Thursday. Which works best?”

This keeps the customer inside the conversation instead of sending them to browse a calendar manually.

Required customer details

You can define which customer details must be collected before the booking is confirmed.

Common examples include:

  • Name
  • Email address
  • Phone number

Only collect the information your booking process actually needs.

If the customer already provided a required detail earlier in the conversation, the AI agent can use that information instead of asking for it again.

Example: booking a consultation

A prospect asks:

“Can I book a product consultation?”

The AI agent can:

  1. Confirm what they want to book
  2. Ask when they are available
  3. Check the calendar
  4. Offer open times
  5. Collect required contact information
  6. Confirm the appointment

The entire process can happen in the same conversation where the prospect was already asking questions about your product or service.

Scheduling can happen after other questions

A customer does not need to start the conversation by asking for an appointment.

Scheduling can become the next step naturally.

For example:

Customer:

“Which service would be best for a first visit?”

AI Agent:

Explains the relevant options.

Customer:

“Okay, can I come in Friday?”

The same AI Answer node can move from answering the question into the scheduling flow when Scheduling is enabled.

Customers can ask questions during scheduling

Customers may ask another question while they are in the middle of booking.

For example:

“Before I book, how long does the appointment take?”

The conversation can answer the question and then continue with the booking process.

This is one advantage of conversational scheduling: the appointment flow does not have to behave like a rigid form.

What happens when a customer selects a time?

Once the customer chooses an available time, Scheduling can hold that slot while any remaining required information is collected.

If the booking is completed, the appointment is confirmed.

If the scheduling process is abandoned or the customer moves away from the booking, the held time can be released.

This helps prevent the same time from being offered while the customer is completing the booking.

After the booking is confirmed

After a successful booking, the customer receives the appointment details in the conversation.

Depending on the channel and configuration, this can include information such as:

  • Appointment date
  • Appointment time
  • Confirmation details
  • Add-to-calendar information

The conversation can continue after the booking is complete.

For example, the customer might ask:

“Where should I park?”

or:

“What should I bring?”

AI Answer can continue handling those questions normally.

Scheduling on web and WhatsApp

Scheduling can be part of the same AI agent experience across supported customer channels.

For example, customers can book from:

  • Your website
  • WhatsApp
  • A dedicated Chat Page

The booking logic remains part of the AI agent while the customer continues using the channel they already chose.

Example: service business

A service business could use:

Start → AI Answer with Scheduling enabled

The customer can:

  1. Ask about services
  2. Find the right option
  3. Ask for an appointment
  4. Choose an available time
  5. Provide the required contact information
  6. Confirm the booking

You do not need to create a separate customer journey just because the conversation moves from questions to scheduling.

Example: sales demo

A prospect asks several product questions and then says:

“Can someone show me this next week?”

AI Answer can use Scheduling to offer available demo times.

This makes scheduling the next step in the same sales conversation instead of sending the prospect to another page.

Example: property viewing

A customer asks about a property and then says:

“Can I see it Saturday morning?”

If property viewings are configured as a schedulable appointment, AI Answer can check the available times and continue the booking process.

Use Router when different requests need different paths

If your AI agent handles many types of customer requests, you can use Router to direct booking-related requests to the appropriate path.

For example:

Book a consultation
→ AI Answer with Scheduling enabled

Ask about a policy
→ Document Search

Check product availability
→ Data Search

Speak to someone now
→ Human Handoff

Scheduling does not need to handle every type of conversation.

Scheduling vs. Human Handoff

Scheduling is useful when the customer wants a planned appointment or meeting.

Use Human Handoff when a person needs to take over the current conversation.

For example:

“Can I book a consultation for next week?”

→ Scheduling

“I need to speak with someone about this problem now.”

→ Human Handoff

Some workflows may use both.

Scheduling vs. AI Form

Scheduling collects the information required to complete a booking.

Use AI Form when you need broader structured intake that is not just part of the appointment process.

For example, you might use:

AI Form → AI Answer with Scheduling enabled

The form could collect qualification information first, and the customer could then book an appointment if the workflow should continue to scheduling.

Working hours

Define the days and times when appointments can be booked.

For example:

  • Monday to Friday
  • 9:00 AM to 5:00 PM

The AI agent should only offer times that fall within your configured availability.

Appointment duration

Set the duration that matches the meeting or service.

Examples:

  • 15-minute introduction
  • 30-minute demo
  • 45-minute consultation
  • 60-minute service appointment

Appointment duration affects which openings can be offered.

Buffer time

Buffers create space before or after appointments.

This can be useful when your team needs time for:

  • Preparation
  • Travel
  • Cleanup
  • Notes
  • Transition between meetings

Make sure the buffer reflects how your team actually operates.

Advance notice

Advance notice controls how soon a customer is allowed to book.

For example, you may not want customers booking an appointment only five minutes before it begins.

A minimum notice period gives your team enough time to prepare.

Booking window

The booking window controls how far into the future customers can schedule.

For example, you might allow bookings:

  • Up to 14 days ahead
  • Up to 30 days ahead
  • Up to 90 days ahead

Choose a range that fits your business.

Time zones

Make sure the scheduling time zone is configured correctly.

This is especially important for:

  • Remote meetings
  • International customers
  • Travel businesses
  • Multi-location teams
  • Businesses serving customers across regions

Customers may describe times naturally, but the booking still needs a consistent calendar time zone behind it.

Multilingual scheduling

Customers can make scheduling requests in the language they are already using in the conversation.

The booking logic stays the same while AI Answer handles the conversational wording.

This is useful for businesses serving customers across different languages and locations.

Test Scheduling before publishing

Test the full booking experience before making the AI agent live.

Check:

  • A customer asking for a specific date and time
  • A customer asking for a broad period such as “Thursday afternoon”
  • A requested time that is already booked
  • A request outside working hours
  • A request too close to the appointment time
  • A request beyond the booking window
  • Missing required contact information
  • A customer changing their preferred time
  • A customer asking another question during booking
  • A successful confirmation

Make sure the times offered by the AI agent match the actual calendar availability.

Test natural customer wording

Customers will not always ask:

“Book an appointment on October 15 at 2:00 PM.”

Test more natural requests such as:

  • “Anything Thursday?”
  • “How about next week?”
  • “Do you have something in the morning?”
  • “What about after 4?”
  • “Can we do Saturday instead?”
  • “Is there anything earlier?”

The scheduling experience should work naturally around the customer's intent.

Tips for using Scheduling

  • Configure your calendar rules before enabling Scheduling.
  • Use realistic working hours and appointment durations.
  • Add buffers when your team needs preparation or transition time.
  • Set appropriate advance notice and booking windows.
  • Collect only the contact information required for the appointment.
  • Let the calendar determine real availability.
  • Do not rely on the AI agent to invent or assume available times.
  • Test both successful bookings and unavailable requests.
  • Test the experience in the channels where customers will actually use it.
  • Use Router, AI Form, or Human Handoff when the broader workflow requires them.

For more information, see:

  • What are AI Answer skills?
  • How to use the AI Answer node
  • Which AskHandle node should I use?
  • What is a Router node?
  • What is an AI Form node?
  • How does Human Handoff work?