Settings
- Quiet hours on or off — off by default; switch on in Settings.
- Start and end — the window in which messages are allowed; defaults 07:00 and 22:00, in your organisation's timezone.
- Urgent jobs go through — on by default: an urgent job (checkout today, or a job created inside the assignment window) is offered regardless.
- Apply to the team — off by default: whether the host's own team notifications also wait.
What happens at 23:30 when a booking arrives
A booking made at 23:30 for a checkout in ten days creates the job as usual. The offer to the first cleaner is held until 07:00. At 07:00 held messages go out gradually rather than all at once, so a cleaner with five held offers does not receive five messages in the same second. The host is told once that messages are being held, so nobody wonders why the cleaner has not responded.
What quiet hours do not do
They do not delay the calendar checks. Bookings, cancellations and date changes are processed every five minutes around the clock; only the outbound messages wait.
Technical details
- The settings are
quietHoursEnabled,quietHoursStart/quietHoursEnd,quietHoursUrgentBypassandquietHoursApplyToTeam. - A held offer is queued in the database-backed message queue with a release time of 07:00, and the host receives a
quiet_hours_heldnotification. - Why the queue is in the database: Lemon runs on several machines. A message held in one machine's memory would be lost on restart or invisible to the others. The queue is a table, with retry counts, delivery status and fallback channels recorded per message; the same table powers retries after a channel failure.