Overview

The Appointment Slot node in a Guided Workflow offers users predefined time blocks for scheduling meetings, consultations, or services. This node dynamically fetches available slots based on configured calendars and displays them during the workflow, enabling seamless appointment booking. It helps guide users through selecting a suitable time, ensuring bookings are made within available and permitted timeframes. Appointment slots help streamline scheduling, avoid conflicts, and provide efficient time management.

​

Various Fields in the Appointment Slot Screen Component

​​

• API Name:

  The API Name is a unique identifier for a specific object, field, or component. It is typically used programmatically or in backend integrations. It often follows a convention with underscores separating words (for example, Customer_Status__c)

• Label: This allows you to name the appointment slot. If you wish to customize the name, you can use this component to define it. 

• Mark Field as Mandatory: Enable this checkbox to make the field required, preventing users from proceeding without providing a value.

• View Type: Determines how the appointment options are displayed. Two viewing types are available: 

​

Card View

• Card View: Displays dates and times as cards, as shown in the screenshot.  

  ​

  ​

  ​

  ​

  ​

• If you choose the Card View, you will have to plot the following:

  • Show Only Available Slots: When this toggle is enabled, only available appointment slots will be displayed to the user. Unavailable slots will be completely removed from view, rather than appearing as greyed-out options. This helps streamline the booking experience by showing only actionable time slots and reducing visual clutter.

​

Date Picker View

• Date Picker View: Provides a dropdown for date and time selection, allowing end-users to choose a date as per their requirements.

  ​

  ​

  ​

• If you choose the Date Picker View, you will have to plot the following:

  • Placeholder: You can define what you want to be displayed on the node for the end user.

    ​

    Note: The Appointment Slot input component supports localization for the calendar in the Date Picker View. Month names and dates are automatically translated based on the user's locale settings.

    

    ​

​

Other Common Fields For Both Card View and Date Picker View

• Assignment Type: Enables the company to define how cases are assigned. Two options are available:

  • Queue: Selecting this option displays an additional dropdown to choose a specific work queue. If you select Queue, the following fields will open up:

    • Work Queue: You can select a work queue from the dropdown to assign tasks or cases to a specific queue for processing.

  • User: Selecting this option provides another dropdown to select either a static or dynamic user group, depending on your needs. If you select User, the following fields will open up:

    • User Source: You can choose from two options:

      • Static: You can select the user from the User field dropdown.

      • Dynamic: You can either give the user ID or select from a variable in the User ID Variable field.

• Types of Slots: You can choose from the available two options in the dropdown:

  • Define Inline: Allows you to manually select the start and end date/time for the slot, with the option to specify buffer durations. If you choose these options, you will have to plot the following:

    • Time Slot Duration: You can define the duration of the slot in seconds, minutes, hours, and days.

    • Buffer Time Duration: You can define the gap between consecutive appointment slots to prevent back-to-back scheduling.

    • Start Time: You can select the start date and time for your appointment slot.

    • End Time: You can select the end date and time for your appointment slot.

    • Timezone: Choose the timezone from the dropdown to show slots in the correct time.

    • Recurrence Type: Choose whether slots repeat daily (all 7 days) or only from Monday to Friday (excluding Saturday and Sunday).

    • Capacity: Set how many appointments can be booked in a single time slot.

    • Slot Variable: Select the variable where the user’s chosen appointment slot will be saved for use later in the workflow.

  • Choose Existing Slot Definition: Enables you to select pre-existing slots already defined in the system. If you choose these options, you will have to plot the following:

    • Slot Definition: You can choose the defined slot as created in the Slot Availability Manager

    • Start Time & End Time: Define the range within which slots can be shown. Slots matching this range, based on availability settings, will be shown, regardless of what’s set in the Slot Availability Manager.

      ​

      Note: Upon date selection, the time picker in the Appointment Screen automatically selects the first available time slot based on the defined slot configuration respecting working hours, excluded dates, and holidays. The auto-selection logic work consistently for both single-day and multi-day or recurring slot definitions.

• Slot Variable: Allows you to define a variable for the slot, enabling it to be reused in subsequent nodes if needed. 

• Take Confirmation: You can enable this toggle to ensure confirmation from users via their chosen communication channel, supported by Sprinklr. A link is shared with the customer to confirm their confirmation about the appointment. The available options of various channels on which the link can be shared are:

  • Email

  • Whatsapp

  • SMS
    Regardless of the channel you choose, you have to plot the following fields:

    • Account: You can select the account from the dropdown.

    • Confirmation Asset: Select the asset if any image is to be sent to the user.

    • URL Shortener: Use this to shorten a link using the system’s preconfigured URL shortener.

    • Confirmation Link Expiry Time: You can define the duration for which that particular confirmation link will be valid.

    • Guided Workflow for Appointment Confirmation: Select the workflow that should run when the user clicks the appointment link, ensuring the confirmation process is completed.

      ​

      

• Visibility Conditions: It is a rule or set of rules that determines whether a specific element, field, or component is visible to users in an application or interface. These conditions are typically based on factors such as field values or contextual data. Visibility conditions ensure that users only see relevant information, improving usability and security. 

  • Example  

    • Condition: Display a "Priority Escalation" section if the "Ticket Priority" is set to "High."

    • Implementation: Visibility Condition: Ticket_Priority = 'High' 

    • Result: The "Priority Escalation" section appears only for high-priority tickets. 

• Configure Error Message: This field allows you to create a warning message for users if the value is required and not entered.