Daily digest and quiet hours

Daily digest time, quiet hours, batch messages

Daily digest and quiet hours

Telegram notification system offers two special features: daily aggregated digest and quiet hours for noise reduction.

Daily Digest

What it sends

One-per-day aggregated message:

📊 Salon X daily digest — 2026-05-02

🗓️ Bookings: 12 (10 completed, 1 cancelled, 1 no-show)
👥 New customers: 3
💰 Revenue: 95,000 HUF
⭐ Reviews: 2 new (avg 4.8)
🎁 Package sales: 2 (45,000 HUF)
📈 Occupancy: 78%

Timing

Configurable time it arrives:

  • Default: 21:00 (evening, summarizing day end)
  • Configurable: 06:00-23:00

When good

  • Morning (08:00): yesterday summary at morning coffee
  • Evening (21:00): today aggregated before bed

On/off

Connection row → Settings → Daily digest toggle. Default: OFF.

Quiet Hours

What it does

Messages in given time window NOT sent immediately. If event happens during quiet hours:

  • Message goes "queued"
  • Sent batch-style at quiet hours end
  • Or simply skipped (depending on config)

Config

  • Start hour: e.g., 22:00
  • End hour: e.g., 08:00 (next morning)
  • Toggle: on/off

Default

Quiet hours off by default. You enable.

What it DOESN'T block

  • Urgent notifications (e.g., payment-failed) may bypass quiet hours (depending on config)
  • Daily digest time is separate (e.g., 21:00 still before quiet hours)

Per-user config

Each connection has separate quiet hours + daily digest:

  • Owner: 22:00-08:00 quiet hours, daily digest 08:00
  • Manager: no quiet hours (always reachable), daily digest off
  • Reception: 18:00-09:00 quiet hours (gets only working hours), daily digest off

Batch message (queued events)

During quiet hours: messages are in queue. End of quiet hours:

  • Queue messages go in batch-style message
  • E.g., 5 new bookings overnight → 1 summary message in morning
  • Or: 5 separate messages (depending on config)

Current default: separate messages (not batch).

When to use it

Scenario 1, salon owner daily routine Owner: daily digest 08:00. Reads at morning coffee. Quiet hours 22:00-07:00 (night silence).

Scenario 2, vacationing manager Manager vacation: quiet hours 24/7 (always silent). Only daily digest 18:00 evening on new state.

Scenario 3, reception staff Reception only during work hours (09:00-18:00). Quiet hours 18:00-09:00.

Scenario 4, hot-on-call owner Owner for urgent: no quiet hours, always reachable. (But critical events filtered: only no-show, payment-failed.)

Scenario 5, group channel Telegram group. Team-level quiet hours 22:00-09:00. Daily digest 08:30 (reception team reacts in morning).

Tips

  • Daily digest is salon health quick gauge, worth enabling.
  • Quiet hours nicely marked time range, don't leave 0-24 hours.
  • 22:00-08:00 standard quiet window by Hungarian population rules.
  • Queued events batch send currently separate messages, no duplication worry.
  • Daily digest time is context-dependent: 08:00 morning coffee, 21:00 evening aggregate.
  • Multi-user quiet hours strict, don't set same for everyone (vacationing owner differs from receptionist).

Related articles

#daily-digest#quiet-hours#batch#queue
💬

Have a question? Ask the AI assistant

The Bookinda AI knows the entire help center and can answer in seconds.

B

Bookinda AI Assistant

Ask anything about features, settings, or integrations.

Hi! I'm the Bookinda assistant. I can answer questions about features, billing, integrations, and more. What would you like to know?

Still need help?

Get in touch with our support team.

Contact us