Skip to content

Campaign Request Scheduling Menu

Element Name: Campaign Request Scheduling Menu

Category: Outbound

Description: Extension module that offers a scheduling menu based on configured slots and exceptions, or returns the scheduling validation result in a JSON format entity.

Functionality: This module allows managing campaign scheduling by validating time slots and presenting scheduling options to users.

Campaign Request Scheduling Menu Configuration Fields

The following parameters should be considered for its configuration

[Allows defining a specific channel to create a deflected campaign record. It must match the contact channel.] Dropdown list with scheduling records for channels different from the client's session (deflection).

[Scheduling] Dropdown list containing scheduling profiles to be used for creating the menu.

[Entity Containing the Contact Identifier] Dropdown list with entities where the contact ID is obtained.

[Action Behavior] Allows defining the behavior of the action:

  • Scheduling Validator: Returns the validation result of the scheduling slots in a string entity (JSON format). It does not create a scheduling record.

  • Scheduling Menu: Offers a scheduling menu according to the validation of the slots with attempt control. Creates the scheduling campaign record.

[Entity for Storing Scheduling Options] Dropdown list with string entities to store the result of slot validation.

[Menu Language:] Dropdown list with languages available in the Lynn application. The selected language will be used to present the menu messages.

[Menu Scope]:

  • Day: Show scheduling options for a single day.
  • Day Range: Show scheduling options for a range of days.

[Number of Days to Consider in the Menu Scope (Current day is considered). Only applies to 'Day Range'] Allows defining if the menu/validation will show scheduling options for one or several days, with a maximum of 5 consecutive days.

[Entity for Storing the Scheduling Menu (List Type)] List-type entity to be used for building and displaying the scheduling menu.

[Error Handling Intention: If the maximum number of failed attempts is reached, the action flow will be interrupted, and the error description will be passed to the selected intention named: 'Scheduling_Entity_Error'] Checkbox where the intention to be activated in case of error is identified.

Scheduling Information (Required)

[Count All Campaign Records (True) or Only Scheduling Records (False)] Allows defining if all campaign records (True) or only the scheduling profile records (False) are counted to determine the available scheduling capacity. It is recommended to use a dedicated scheduling campaign and count the profile records.

[Scheduling Confirmation Message] Message to confirm the scheduling. The scheduled date will be concatenated. Example: "Your scheduling has been confirmed for [date]."

[No Available Slots Message] Message to show when there are no available slots for scheduling. Example: "Sorry, no slots are available at the moment."

[Selected Scheduling Unavailable Message] Message to show when the selected scheduling slot is no longer available. Example: "The selected slot is no longer available. Please choose another."

Implementation Example

-- Input:

[Specific Channel] GupShup WhatsApp (Testing 56940XXXXXX Service 80)

[Scheduling] Test SH

[Entity Containing the Contact Identifier] CONTACT_ID

[Action Behavior] Scheduling menu

[Entity for Storing Scheduling Options] Scheduling menu

[Menu Language] es

[Menu Scope] Day range

[Number of Days to Consider in the Menu Scope (Current day is considered). Only applies to 'Day Range'] 5

[Entity for Storing the Scheduling Menu (List Type)] menuScheduling

[Menu Message to Request Scheduling Date] 'Seleccione fecha de agendamiento'

[Menu Message to Request Scheduling Time] 'Seleccione la hora de agendamiento'

[Maximum Failed Attempts from an Expression] 3

[Error Handling Intention] Error_Handler

[Scheduling Confirmation Message] 'Hemos agendado su mensaje correctamente'

[No Available Slots Message] 'Lo sentimos, no hay horarios disponibles para agendar'

[Selected Scheduling Unavailable Message] 'El horario seleccionado ya no se encuentra disponible'

[Entity for Storing the Scheduling Date] SchedulingDate

-- Output: