# AI Conversational Appointment Booking Workflow and Setup > The following is a step-by-step guide on how to set up your own AI Conversational Appointment booking bot within a workflow. - Source: https://docs.ghlcustomercare.com/docs/marketing/ai-appointment-booking-bot/ai-conversational-appointment-booking-workflow-and-setup - Section: Marketing / AI Appointment Booking Bot - Reading time: 1 min - Images: 6, each explained below - Modified on Tue, 21 Jun, 2022 at 3:38 PM --- ### The following is a step-by-step guide on how to set up your own AI Conversational Appointment booking bot within a workflow. --- ## 1\. Create Workflow Add a trigger with customer Replied (or any other trigger) ![Create Workflow](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48232359047/original/9_O9O-lOgVZzMFPEhKvgEiajAtnaS18yhw.png) **1. Create Workflow (image 1 of 6)** This screenshot appears in the "1. Create Workflow" section of "AI Conversational Appointment Booking Workflow and Setup". The text alongside this image reads: Add a trigger with customer Replied (or any other trigger). Immediately after, the guide continues: Create action for the appointment bot with the desired calendar Set the "Total bot processing duration" -This is how long before the bot will time out if there are no replies from the contact. - What this covers: Add a trigger with customer Replied (or any other trigger) - Next: Create action for the appointment bot with the desired calendar Set the "Total bot processing duration" -This is how long before the bot will time out if there are no replies from the contact. ## 2\. Select the AI appointment bot in the workflow options Create action for the appointment bot with the desired calendar Set the "Total bot processing duration" -This is how long before the bot will time out if there are no replies from the contact. ![AI appointment bot](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48232359049/original/pr8zGFvRVV-AiELuKGmg8rgJOyAzi19VpQ.png) **2. Select the AI appointment bot in the workflow options (image 2 of 6)** This screenshot appears in the "2. Select the AI appointment bot in the workflow options" section of "AI Conversational Appointment Booking Workflow and Setup". The text alongside this image reads: Create action for the appointment bot with the desired calendar Set the "Total bot processing duration" -This is how long before the bot will time out if there are no replies from the contact. Immediately after, the guide continues: 1. The bot successfully books the appointment. - What this covers: Create action for the appointment bot with the desired calendar Set the "Total bot processing duration" -This is how long before the bot will time out if there are no replies from the contact. - Next: 1. The bot successfully books the appointment ## 3\. The AI conversation will end in one of the three ways. **1\. The bot successfully books the appointment** **2\. Bot timed out:** The appointment was not booked as the lead didn't respond to the prompts by the bot. **3.** **Appointment could not be booked for other reasons,** - no suitable slot, the bot could not understand the query or other technical issues. ## 4\. Create a condition if the bot booked an appointment.  ![Create condition if the bot booked an appointment.](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48232359046/original/hJxKhMj9Kpsm64xjTF7gE24n8eRgzgs72g.png) **4. Create a condition if the bot booked an appointment. (image 3 of 6)** This screenshot appears in the "4. Create a condition if the bot booked an appointment." section of "AI Conversational Appointment Booking Workflow and Setup". The text alongside this image reads: 3. Appointment could not be booked for other reasons, - no suitable slot, the bot could not understand the query or other technical issues. Immediately after, the guide continues: Here we want to know if the appointment was not booked because the bot timed out or for some other reason. - What this covers: 3. Appointment could not be booked for other reasons, - no suitable slot, the bot could not understand the query or other technical issues. - Next: Here we want to know if the appointment was not booked because the bot timed out or for some other reason. ## 5\. Create a message or any action for the appointment booked condition ![Create message for appointment booked](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48232359048/original/KKvlxmWPb4Du_Qzq0o7_HgVBmsxWMJ2a3A.png) **5. Create a message or any action for the appointment booked condition (image 4 of 6)** This screenshot appears in the "5. Create a message or any action for the appointment booked condition" section of "AI Conversational Appointment Booking Workflow and Setup". The text alongside this image reads: 3. Appointment could not be booked for other reasons, - no suitable slot, the bot could not understand the query or other technical issues. Immediately after, the guide continues: Here we want to know if the appointment was not booked because the bot timed out or for some other reason. - What this covers: 3. Appointment could not be booked for other reasons, - no suitable slot, the bot could not understand the query or other technical issues. - Next: Here we want to know if the appointment was not booked because the bot timed out or for some other reason. ## 6\. Secondary condition if the appointment is not booked due to bot timeout  Here we want to know if the appointment was not booked because the bot timed out or for some other reason.  Common reasons could be that no slots were available or the bot failed to understand the conversation.  ![Secondary condition if the appoitment is not booked](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48232359051/original/WYUwNv5-5grq9Jlo-YUcHXatsZbInn14ig.png) **6. Secondary condition if the appointment is not booked due to bot timeout (image 5 of 6)** This screenshot appears in the "6. Secondary condition if the appointment is not booked due to bot timeout" section of "AI Conversational Appointment Booking Workflow and Setup". The text alongside this image reads: Common reasons could be that no slots were available or the bot failed to understand the conversation. Immediately after, the guide continues: Configure appropriate actions for bot failures for any other reason. If you have Eliza Agent Platform Subscription, you can send the lead over there to continue the lead nurture. - What this covers: Common reasons could be that no slots were available or the bot failed to understand the conversation. - Next: Configure appropriate actions for bot failures for any other reason. If you have Eliza Agent Platform Subscription, you can send the lead over there to continue the lead nurture. ## 7\. Third Condition - Appointment not booked for any other reason. Configure appropriate actions for bot failures for any other reason. If you have Eliza Agent Platform Subscription, you can send the lead over there to continue the lead nurture.  ![Human Rollover to Eliza agent platform ( if subscribed)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48232359050/original/lbIxgrDyMUfoe8A8bvOrTM4D7YWvX1h5Mw.png) **7. Third Condition - Appointment not booked for any other reason. (image 6 of 6)** This screenshot appears in the "7. Third Condition - Appointment not booked for any other reason." section of "AI Conversational Appointment Booking Workflow and Setup". The text alongside this image reads: Configure appropriate actions for bot failures for any other reason. If you have Eliza Agent Platform Subscription, you can send the lead over there to continue the lead nurture. - What this covers: Configure appropriate actions for bot failures for any other reason. If you have Eliza Agent Platform Subscription, you can send the lead over there to continue the lead nurture. [](https://app.tango.us/app/workflow/b9d308b3-1e9a-44f8-a259-7f23906a05aa?utm_source=magicCopy&utm_medium=magicCopy&utm_campaign=workflow%20export%20links) --- Documentation for GHL Customer Care. Support: support@ghlcustomercare.com