Visitor event and bot schedules
Restrict visitor events and eligible bots to selected dates, weekdays and website-local times.
What it is
Dates limits an event to particular dates, weekdays or times of day. Bot editors can also use date and time filters to restrict eligibility. These checks use the website's local time rather than the visitor's location.
Who uses it and why
- Administrators and supervisors with the Settings or Manager role schedule campaigns and restrict automatic engagement to suitable hours.
- Bot Trainer users set eligible hours for bots.
- Developers work with Powerfront on custom business-hour exceptions where required.
Where to find it
In Settings › Events › Visitor Events, open an event and find Additional filters › Dates. Bot schedules require the Bot Trainer role and are available through the relevant bot editor under Settings › Bots › FAQ Bots or Settings › Bots › Custom Bots.
The Settings role grants access to Settings › General Settings › Regional Settings, where the website's Time Zone is shown. Ask Powerfront to change it for you.
How it works
Each row defines an allowed window. You can supply dates, weekdays, times or a combination. Restrictions within a row work together. Several rows are alternatives: the schedule passes if any row matches.
For example, use one row for Monday to Friday, 09:00 to 17:00, and another for Saturday, 10:00 to 13:00. No date rows means there is no schedule restriction, although visitor filters and other eligibility checks still apply.
Date-specific rows are checked before recurring rows. They do not override recurring rows that also allow the current time. Adding a holiday row does not, by itself, close an otherwise allowed weekly window.
The time editor works in minutes. An ending time includes the remainder of that minute. Delayed Time On Page actions check the schedule again before running.
Configure it
- Open the event and select Add beside Dates.
- Check the displayed Timezone.
- Enter optional date From and To values.
- Select Day of the week and enter time From and To values as needed.
- Add further allowed windows, then save.
A row must contain at least one value. When both times are set, To must be later than From. Split overnight opening hours across separate days and rows.
For a custom business-hour calendar with closure exceptions, ask Powerfront to review the integration. Exception precedence depends on that custom configuration.
Settings
| Setting | Where | Applies to | Default | Who can change it | What it does |
|---|---|---|---|---|---|
| Time Zone | Settings › General Settings › Regional Settings | website | Not set: uses the hosting system's local time zone | Settings role | Supplies the website-local time used to evaluate visitor-event and bot schedules. |
| From | Settings › Events › Visitor Events | website | Not set: no starting date or time restriction | Settings role, Manager role | Sets an optional starting date or starting time in a Dates row. |
| To | Settings › Events › Visitor Events | website | Not set: no ending date or time restriction | Settings role, Manager role | Sets an optional ending date or ending time in a Dates row. |
| Day of the week | Settings › Events › Visitor Events | website | Not set: every weekday is allowed | Settings role, Manager role | Limits a Dates row to selected weekdays. |
Permissions
| Permission | Lets you |
|---|---|
| Settings | Manage visitor events and access Regional Settings, subject to delegated permissions. |
| Manager | Manage visitor-event date restrictions, subject to delegated permissions. |
| Bot Trainer | Manage schedules offered in bot editors. |
Limits and good to know
- A schedule is an eligibility check. It does not create a new trigger when opening time arrives.
- Closing an eligibility window is not a promise that an existing conversation will end.
- Subsites and visitors in other countries do not automatically give each event a separate time zone.
- Appointment schedules and voice opening hours are separate configurations.
- Check dates around daylight-saving changes with Powerfront when precise transition behaviour matters.
Depends on and works with
+2 more · used by
- Visitor event alerts for operatorsConfigured by
Dates can restrict alert times.
- Custom bots and FAQ botsConfigured by
Time filters can restrict bot participation.
View all connections as a list
This feature uses
- Website and regional settingsConfigured by
The website time zone determines the local time used by these schedules.
- Visitor event rules and actionsRelated
Event schedules permit or prevent a matching trigger without creating a trigger themselves.
- Custom bots and FAQ botsRelated
Bot registrations can use date and time restrictions to limit participation.
Used by
- Time-based visitor event triggersConfigured by
Event schedules are checked again before a deferred action runs.
- DepartmentsConfigured by
Channel schedules restrict when visitors satisfy the channel's routing conditions.
- Skillsets and skills-based routingConfigured by
Skill time filters can add or remove eligibility as schedules change.
- Visitor popups and embedded contentConfigured by
Event schedules can limit when popups appear.
- Visitor event rules and actionsConfigured by
Date and time filters restrict when an event can run.
- Proactive chat invitationsConfigured by
Event schedules restrict invitation times.
- Visitor popup event setupConfigured by
Dates can limit offer times.
- Visitor event updates to customer contextConfigured by
Dates restrict when actions can run.
- Visitor event alerts for operatorsConfigured by
Dates can restrict alert times.
- Custom bots and FAQ botsConfigured by
Time filters can restrict bot participation.
FAQ and troubleshooting
Why did my event run on a holiday?
Another allowed row may still match. Date-specific rows do not automatically cancel weekly rows.
Why does the editor reject 22:00 to 02:00?
The ending time must be later than the starting time within one row. Split the window into an evening row and a following-day row.
Why does the event run at the wrong local hour?
Check the Timezone shown in the row. The website's time zone applies, rather than the visitor's time zone. Powerfront can correct the website setting.
Why did nothing happen when business hours began?
The event still needs its selected trigger and matching visitor filters. The schedule only permits or prevents that evaluation.