When a tagged meeting gets its call
Set the days and hours the assistant may dial and how far apart its attempts are, so a meeting tagged in Raynet gets its confirming call at a sensible moment.
How meetings are found
Chetty looks for meetings at startup and every 15 minutes, within the next 30 days. The list picks the meetings that carry the Trigger tag; each one is then read in full, because the list alone does not carry the owner.
Meetings already pending outside those 30 days are reread one by one. A meeting that disappears from the list is not proof that it was deleted, so nothing is dropped silently.
The first call
The first call is planned at First call time on the last allowed calling day before the meeting, so a Monday meeting is normally called on the Friday before.
A meeting tagged late uses the next allowed slot. Public holidays are not skipped, so a holiday inside the window does not move the call.
Calling days and hours
- Calling days default to Monday to Friday and at least one must stay selected.
- Calls from and Calls until default to 09:00 until 17:00 in the configured time zone, Europe/Prague unless changed.
- The closing time is exclusive: a call may start at 16:59, not at 17:00.
- Every attempt must start before the meeting start minus Minimum time before the meeting, normally two hours.
- A retry is moved inside the calling hours rather than running outside them.
Attempts and retries
Maximum attempts defaults to two calls, Delay between attempts to three hours, counted from the result of the previous call.
A customer who names a future time is called back at that exact time when it is allowed and an attempt remains. Only one call runs at a time, so a busy queue or a slow network can delay the start; just before dialling, Chetty checks the meeting, its note in Raynet, the current time, the deadline and the attempt count once more.
What changes a plan
- A moved meeting starts a new count for its new start.
- Cancelling the meeting, completing it or removing the Trigger tag drops the pending call.
- A completed call is not repeated for the same meeting time.
- The Trigger tag stays on the meeting when a result is written, so it remains recognizable in Raynet.