Date/Time based trigger
This is a checklist that serves as a guide when using date and date/time triggers, to avoid confusion.
General Guidelines
- In both date and date/time triggers, make sure the assigned date or time is always in the future. Past dates and times prevent the trigger from starting. This is the platform's default behavior.
- In channels where the time zone is provided by default (Web Chat, Facebook, Instagram, etc.), the contact's time zone is used in date/time triggers.
- In channels where the time zone is NOT provided by default, the workspace's time zone is used in date/time triggers.
- NicoChat treats all date and date/time contact fields as UTC by default. Therefore, if the time zone is not provided, the system assumes the value is in UTC and applies the offset according to the time zone of the contact or of the workspace.
Date trigger
- Make sure the date, when saved in the date field, is in the standardized UTC format. An example of UTC format for date is “YYYY-MM-DD”. Other formats include:
DD-MM-YYYY
MM-DD-YYYY
DD/MM/YYYY
- Localized date formats always cause problems, since they are not recognized by the system and create offsets out of sync with the actual time.
Date and time trigger
- Make sure the date and time, when saved in the date and time field, is in UTC format. The de facto standard format for date and time is “YYYY-MM-DDThh:mm:ss+Z”
where:
YYYY represents the year
MM represents the month
DD represents the day
T represents the separation between date and time
hh represents the hour
mm represents the minutes
ss represents the seconds
Z represents the time zone (such as +05:00 or -02:00)